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 1QW3oh-0002qi-TM for garchives@archives.gentoo.org; Mon, 13 Jun 2011 09:52:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 820C81C055; Mon, 13 Jun 2011 09:50:50 +0000 (UTC) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by pigeon.gentoo.org (Postfix) with SMTP id 0B3A51C055 for ; Mon, 13 Jun 2011 09:50:49 +0000 (UTC) Received: (qmail invoked by alias); 13 Jun 2011 09:50:48 -0000 Received: from p54850C9B.dip0.t-ipconnect.de (EHLO gmx.net) [84.133.12.155] by mail.gmx.net (mp006) with SMTP; 13 Jun 2011 11:50:48 +0200 X-Authenticated: #20088476 X-Provags-ID: V01U2FsdGVkX18VeKtft90VeBtBcpV3ROjqL22SFTADf9n3wWWntZ /VYb7BYaAYmgHW Received: by gmx.net (nbSMTP-1.00) for uid 1001 Meino.Cramer@gmx.de; Mon, 13 Jun 2011 11:50:50 +0200 (CEST) Date: Mon, 13 Jun 2011 11:50:49 +0200 From: meino.cramer@gmx.de To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Questions about the magic Sys Req keys Message-ID: <20110613095049.GK3061@solfire> References: <4DF5D5DF.7080205@gmail.com> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4DF5D5DF.7080205@gmail.com> User-Agent: mutt-ng/devel-r804 (Linux) X-Y-GMX-Trusted: 0 X-Archives-Salt: X-Archives-Hash: 44ca1a76d0ab75de50d76a07a90cd3ef Dale [11-06-13 11:24]: > Howdy, > > I just had a hard lock up. I had a random reboot the other day while I > was sleeping as well. This was with gentoo-sources 2.6.39. I'm not > sure what caused the one the other day but I had several days of > uptime. The one I just had was also after a few days of uptime. I > was logged into KDE when EVERYTHING froze. The mouse pointer wouldn't > move. The clock stopped. The numlock light wouldn't even change when > I hit the key for it. So, X was locked up pretty good. I also > couldn't switch to a console either. This is the odd part. I tried to > use the magic Alt SysReq keys to at least try to get a reasonable > shutdown. They didn't work either. > > So, my question is this. What kind of lock up could keep the magic > keys from working? This is on my new amd64 machine. It was totally > stable until the kernel upgrade. I think this could be a kernel issue. > I booted a older kernel and will test it for a few days but wanted to > know what kind of lockups could keep the magic keys from working. > After the hal/xorg deal, we all know how I hate hard resets. ;-) > > Thanks much. > > Dale > > :-) :-) > Hi Dale, this kind of locks happening - as far as I know - when the kernel itsself hangs or crash (null pointer dereferences and such). As long as the kernel does "something" (eats CPU cycles in a more or less senseful way) the sysreq magic does work since it is due to its nature located somewhere deep in the kernel just a little bit above the surface of the hardware...:) If the kernel crashes the lights may shine but there is no one at home anymore. Try to modularize as much as possible to seperate the good from the bad and the ugly. May be upgradeing the kernel to 2.6.39.1 may help also. Good luck! Best regards, mcc