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 1KpP33-0006Q4-0h for garchives@archives.gentoo.org; Mon, 13 Oct 2008 15:09:29 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9018CE0206; Mon, 13 Oct 2008 15:09:26 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.145]) by pigeon.gentoo.org (Postfix) with ESMTP id 51799E0206 for ; Mon, 13 Oct 2008 15:09:26 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 4so560048eyk.10 for ; Mon, 13 Oct 2008 08:09:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender :to:subject:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references :x-google-sender-auth; bh=9QqfAPe8kd9a1ND7rFPI/GTXvyxc9S8nU60iSpNQUTg=; b=xHyKyJb0Q6jsGkd491COEWMgwStXETo9ZnnrhhAIqiBZGooYLMcdT6sBFxJHYoU11P U3jGF9Ms3TUllC8tMpbEkVdNmj9vZd32N9AdQqAwd13RmqRL/D9nynZX/KjwJdO/pUJb CwDAq/RUfXpFFf081oWTk+tZLWnAiRq85x5Qg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=j76KNFBrN95WextfL3kJAvjuY+ig7YxuO+v9+xXmGMUALyOF3DeYlSfDzP0Ax6NOZB L0VWkuAcLjNkGG12igb7ztPgdicVeO3cLNo2qSbealXtSKY22hRzDxt49BuwR+npjLf3 IEKuqOS7kHryb+QumVJrFV/d1cAiW9/+o2qFc= Received: by 10.103.20.7 with SMTP id x7mr3633287mui.96.1223910564766; Mon, 13 Oct 2008 08:09:24 -0700 (PDT) Received: by 10.103.141.2 with HTTP; Mon, 13 Oct 2008 08:09:24 -0700 (PDT) Message-ID: Date: Mon, 13 Oct 2008 16:09:24 +0100 From: "Duane Griffin" Sender: duaneg@gmail.com To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel crash - howto find out what happened? In-Reply-To: <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=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200810121108.57840.alexander.puchmayr@linznet.at> X-Google-Sender-Auth: 9808f3c7fae5f9d8 X-Archives-Salt: c4539f2e-17bc-42f2-9c23-d91c22a44ca1 X-Archives-Hash: 269aada99f7b57a55aaca5acfac51fe3 2008/10/12 Alexander Puchmayr : > 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). If you have another machine lying around, try setting up netconsole and/or serial console logging. They should catch any dying messages from your kernel. Blinking LEDs indicates a panic, which means you should get a message in those cases, at least. Using serial console is the easiest and most reliable way, but requires a serial cable. Netconsole just uses ethernet but isn't as reliable. Take a look at Documentation/serial-console.txt and Documentation/networking/netconsole.txt under your kernel source directory for more info. Cheers, Duane. -- "I never could learn to drink that blood and call it wine" - Bob Dylan