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 1KpmoA-0006mO-3H for garchives@archives.gentoo.org; Tue, 14 Oct 2008 16:31:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 48B36E013E; Tue, 14 Oct 2008 16:31:18 +0000 (UTC) Received: from puchmayr.linznet.at (puchmayr.linznet.at [80.66.46.165]) by pigeon.gentoo.org (Postfix) with ESMTP id 51339E013E for ; Tue, 14 Oct 2008 16:31:17 +0000 (UTC) Received: (qmail 6689 invoked by uid 210); 14 Oct 2008 16:31:14 -0000 Received: from prometheus.puchmayr.linznet.at by hephaestos (envelope-from , uid 201) with qmail-scanner-2.02st (clamdscan: 0.94/8417. f-prot: 4.6.7/3.16.15. spamassassin: 3.2.1. perlscan: 2.02st. Clear:RC:1(192.168.1.4):. Processed in 0.088312 secs); 14 Oct 2008 16:31:14 -0000 Received: from prometheus.puchmayr.linznet.at (HELO ?192.168.1.4?) (192.168.1.4) by hephaestos.puchmayr.linznet.at with SMTP; 14 Oct 2008 16:31:14 -0000 From: Alexander Puchmayr Organization: Fa Linznet To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel crash - howto find out what happened? Date: Tue, 14 Oct 2008 18:31:06 +0200 User-Agent: KMail/1.9.9 References: <200810121108.57840.alexander.puchmayr@linznet.at> <342e1090810131630v306f6c37v5b2de6e3e0cd5cdc@mail.gmail.com> In-Reply-To: <342e1090810131630v306f6c37v5b2de6e3e0cd5cdc@mail.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="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810141831.07316.alexander.puchmayr@linznet.at> X-Archives-Salt: 9620c50d-6890-481c-9075-2a0694a5c70b X-Archives-Hash: 15a015eacee94863ffd4d39d49e36320 On Dienstag, 14. Oktober 2008, Daniel da Veiga wrote: > On Sun, Oct 12, 2008 at 07:08, Alexander Puchmayr > > wrote: > > Hi there! > > > > MY gentoo system (an amd64@4400+, 2GB ram, nforce4-chipset) worked fine > > for nearly two years, but now it frequently freezes, sometimes (not > > always) scrollock and capslock LED blinking). > > > > Since I'm using the box as desktop, I have only a frozen X-server and > > no possibility to switch to console (maybe there's some hint whats > > happened?). > > > > How do I find out what happened, why it crashed? Modern systems have > > MCE-logs, but how do I read it in this case? After reboot, all > > information seems to be gone since mcelog is always empty. > > > > I assume there's some problem with some hardware, I already tested RAM > > with memtest86, but no errors. > > 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-", 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? Alex