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 1KozEV-0005hN-Ob for garchives@archives.gentoo.org; Sun, 12 Oct 2008 11:35:35 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B5A4AE049F; Sun, 12 Oct 2008 11:35:33 +0000 (UTC) Received: from wr-out-0506.google.com (wr-out-0506.google.com [64.233.184.229]) by pigeon.gentoo.org (Postfix) with ESMTP id 8CD08E049F for ; Sun, 12 Oct 2008 11:35:33 +0000 (UTC) Received: by wr-out-0506.google.com with SMTP id c37so788068wra.26 for ; Sun, 12 Oct 2008 04:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:message-id; bh=JdXXbWTFsTGtuNEawMBuyEKjypLft/fGbW1xZ40tRSY=; b=rLq5AK4t1W63J9d2a9d0NLWEI+sOME/+iX15dzYWzpluzadKCpR/CvuOs4U6WdQefX ZLGSjf1H1ikPukDZ81EHtnrOp8b1qZQ988HHyeI4+DSw/yJn+p8zXaeufp/n/Lb0YsEP Zpe32ZcScZzEuS1Mc31qFVngXwXL6Ei5GSMyI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :message-id; b=u1eLeokc3xU2admJZynl5wjCvMwlMyq2vFo0+nGg7Pomn7MVz4hd1Te0l3s07LZvs9 iSPz8MWC5BYewzeXQRiO7cyMaoK+FGcV8gDL0zElkX92oSMEmRRErXz1601mM5u2E29m dtiLRUMP4OPhUD/QtZPcY0u81sRP1pifeaqTw= Received: by 10.64.47.16 with SMTP id u16mr7783923qbu.73.1223811332052; Sun, 12 Oct 2008 04:35:32 -0700 (PDT) Received: from ?10.0.0.6? (dsl-243-231-180.telkomadsl.co.za [41.243.231.180]) by mx.google.com with ESMTPS id k30sm7488124qba.4.2008.10.12.04.35.29 (version=SSLv3 cipher=RC4-MD5); Sun, 12 Oct 2008 04:35:31 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel crash - howto find out what happened? Date: Sun, 12 Oct 2008 13:35:20 +0200 User-Agent: KMail/1.9.10 References: <200810121108.57840.alexander.puchmayr@linznet.at> <20081012091635.GA16359@eriks> <200810121312.21029.alexander.puchmayr@linznet.at> In-Reply-To: <200810121312.21029.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="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200810121335.21083.alan.mckinnon@gmail.com> X-Archives-Salt: b34d3336-840a-44d8-819e-d4978dc85d6a X-Archives-Hash: de2ea68d7aab0e3c5ddc93da5a32e330 On Sunday 12 October 2008 13:12:20 Alexander Puchmayr wrote: > > 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) > > I've tried, but unfortunately, the X-Driver on my laptop (i965) does also > seem to have stability problems, after ca an hour it froze using 100% > cpu-time, unable to kill (nither kill or kill -9 did work). I guess it > didn't wakeup from DPMS :-( Here's a thought: if you have a spare machine, you could ssh in to your desktop and continue to work normally. The ssh session would be tailing an appropriate log, so even if the desktop goes south there's a good chance the error log is visible For something more persistent, you could try temporarily sending all logs to a remote log server. Remote logging is quite efficient, I usually find the only thing that gets in it's way is a complete instant kernel halt that brings the whole machine down without warning - this is extremely rare on production kernels -- alan dot mckinnon at gmail dot com