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 1Kox46-0007m0-7M for garchives@archives.gentoo.org; Sun, 12 Oct 2008 09:16:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F1099E03CC; Sun, 12 Oct 2008 09:16:39 +0000 (UTC) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by pigeon.gentoo.org (Postfix) with SMTP id 87948E03DE for ; Sun, 12 Oct 2008 09:16:39 +0000 (UTC) Received: (qmail invoked by alias); 12 Oct 2008 09:16:51 -0000 Received: from p549EC445.dip.t-dialin.net (EHLO localhost) [84.158.196.69] by mail.gmx.net (mp032) with SMTP; 12 Oct 2008 11:16:51 +0200 X-Authenticated: #43117208 X-Provags-ID: V01U2FsdGVkX19I45Z+fnhIQ2MqClZ0SOKVzV5p4zaBCLyorW9DcF aGs0DERf5je9Pa Date: Sun, 12 Oct 2008 11:16:36 +0200 From: Erik Hahn To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel crash - howto find out what happened? Message-ID: <20081012091635.GA16359@eriks> Mail-Followup-To: gentoo-user@lists.gentoo.org References: <200810121108.57840.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-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200810121108.57840.alexander.puchmayr@linznet.at> User-Agent: Mutt/1.5.18 (2008-05-17) X-Y-GMX-Trusted: 0 X-FuHaFi: 0.63 X-Archives-Salt: 86795e39-c1ad-4a51-89db-d2bd7b6815b7 X-Archives-Hash: 95ec3714645d2ab98ae25ed2b1cdc2db On Sun, Oct 12, 2008 at 11:08:57AM +0200, Alexander Puchmayr wrote: > 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. > Alex If it's a kernel panic you actually get debugging information on the console. It's just hidden "behind" the X server. Maybe you can reproduce the problem working without X (If you can do your work purely from the VTs) Do you use any proprietary drivers? -Erik -- hackerkey://v4sw5hw2ln3pr5ck0ma2u7LwXm4l7Gi2e2t4b7Ken4/7a16s0r1p-5.62/-6.56g5OR