From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KpnP9-00020g-KZ for garchives@archives.gentoo.org; Tue, 14 Oct 2008 17:09:55 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2472FE0229; Tue, 14 Oct 2008 17:09:55 +0000 (UTC) Received: from mail.askja.de (mail.askja.de [83.137.103.136]) by pigeon.gentoo.org (Postfix) with ESMTP id ED4F1E0229 for ; Tue, 14 Oct 2008 17:09:54 +0000 (UTC) Received: from static-87-79-89-40.netcologne.de ([87.79.89.40] helo=zone.wonkology.org) by mail.askja.de with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1KpnP6-0002cJ-K6 for gentoo-user@lists.gentoo.org; Tue, 14 Oct 2008 19:09:52 +0200 Received: from localhost (localhost [127.0.0.1]) (uid 1000) by zone.wonkology.org with local; Tue, 14 Oct 2008 19:09:45 +0200 id 0001032F.48F4D259.000014B2 From: Alex Schuster Organization: Wonkology To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel crash - howto find out what happened? Date: Tue, 14 Oct 2008 19:09:39 +0200 User-Agent: KMail/1.9.9 References: <200810121108.57840.alexander.puchmayr@linznet.at> <342e1090810131630v306f6c37v5b2de6e3e0cd5cdc@mail.gmail.com> <200810141831.07316.alexander.puchmayr@linznet.at> In-Reply-To: <200810141831.07316.alexander.puchmayr@linznet.at> 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-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200810141909.43431.wonko@wonkology.org> X-Archives-Salt: d3c8ae86-9d37-4b34-aa2e-cd286b7a968a X-Archives-Hash: 97a72201091f6f7b9394aba074790028 Alexander Puchmayr writes: > On Dienstag, 14. Oktober 2008, Daniel da Veiga wrote: > > > > I had one of this freezes today. > > Simply killed X using CTRL+SYSREQ+K and got back a console with error > > messages. > > > > Have you tried the SYSREQ keys? > > How does this work? I've tried it but I didn't get this working at all. > AFAIK, first step is to compile the CONFIG_MAGIC_SYSRQ into the kernel. > Then, make sure there's a "1" in /proc/sys/kernel/sysrq; well it is. > /usr/src/linux/Documentation/sysrq.txt says press "ALT-SysRq- key>", I've tried it out with SysRq=printScreen and cmd='h' for help, > but nothing happens, even under normal conditions. What did I make > wrong? Try another key than 'h'. The space key will show a little help, probably that what you expected to see with 'h'. Oh, you need to be on a text console (ctrl-at-f1) to get visible output. http://en.wikipedia.org/wiki/Magic_SysRq_key Wonko