From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1S8GK4-0000Pr-EZ for garchives@archives.gentoo.org; Thu, 15 Mar 2012 19:26:52 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6C065E0973; Thu, 15 Mar 2012 19:26:38 +0000 (UTC) Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com [209.85.214.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 6B61BE0952 for ; Thu, 15 Mar 2012 19:25:44 +0000 (UTC) Received: by bkwj4 with SMTP id j4so2880879bkw.40 for ; Thu, 15 Mar 2012 12:25:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=Nc/oF+O2kgn7uEUr6xT8bxa63emYYUcIWG0fjod322o=; b=j6fOF1LtfnHlHJamuSiW/QLmdU7d0tqcIlSBVCXy+pAGmtWEO2rBaCI3SWkBn+MBWs TT56PAi21a3HzSze2PAqt2e4Zegv5jspbA4YOlLFTSZk5yHJQTSj5eM1ww23lahABLwK NCBKdCzmvI5eqK/laLUUOzNUYeFH8UW2cq4TcoNHHU3ayhX0NG66w+QI4jVOzNWY61QU nPryHoyaiw+UN23aH/vejmlpq+5Ld2PQf+K55OeUv1nquHKKgIgA8EFEGFQCFyDSE/pS gnk3G/vZNgnZpM7dVobsjPj2UtWjjyZOv7Z3kZUPYpEgD9i60O2QVZWljrZ+PlVGmvpG PzYg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.204.157.135 with SMTP id b7mr44965bkx.138.1331839543439; Thu, 15 Mar 2012 12:25:43 -0700 (PDT) Received: by 10.204.168.17 with HTTP; Thu, 15 Mar 2012 12:25:43 -0700 (PDT) In-Reply-To: <201203151917.53229.michaelkintzios@gmail.com> References: <4F60E22D.3060409@gmail.com> <4F621EE6.6040209@gmail.com> <201203151917.53229.michaelkintzios@gmail.com> Date: Thu, 15 Mar 2012 15:25:43 -0400 Message-ID: Subject: Re: [gentoo-user] How can I trigger kernel panic? From: Michael Mol To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c00f07e2-4420-40f2-a6d2-433674dc69df X-Archives-Hash: 41dad8d6c6d6f0e82820c02788de178a On Thu, Mar 15, 2012 at 3:17 PM, Mick wrote: > On Thursday 15 Mar 2012 17:02:15 Michael Mol wrote: >> On Thu, Mar 15, 2012 at 12:55 PM, Jarry wrote: >> > On 14-Mar-12 19:41, ZHANG, Le wrote: >> >> > =C2=A0 =C2=A0So my question is: Can I somehow deliberately trigger >> >> > =C2=A0 =C2=A0"kernel panic" (or "kernel oops")? >> >> >> >> For panic, echo c > /proc/sysrq-trigger >> > >> > After I issued the above mentioned command, my system >> > instantly "froze to death". Nothing changed on screen, >> > no "kernel panic" or "Ooops" screen. Just frozen... >> > >> > No reaction to keyboard or mouse. No auto-reboot either. >> > The only thing I could do is to press "Reset". Not exactly >> > what I have been expecting... >> >> Were you running under X? The panic would have killed X, which >> wouldn't have released control over the video hardware. >> >> There's a SysRq sequence to get around this, but I don't remember it. > > Ctrl+Alt+ > > R E I S U B > > (busier in reverse) > > After a E or I you should be back into a console, unless things are badly > screwed. Is that Ctrl+Alt+SysRq+(R E I S U B), or is the SysRq key not actually used= ? --=20 :wq