From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
	by nuthatch.gentoo.org with esmtp (Exim 4.62)
	(envelope-from <gentoo-user+bounces-59869-garchives=archives.gentoo.org@gentoo.org>)
	id 1HHLG4-0003bG-5E
	for garchives@archives.gentoo.org; Wed, 14 Feb 2007 14:37:20 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
	by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l1EEa6sw016208;
	Wed, 14 Feb 2007 14:36:06 GMT
Received: from nz-out-0506.google.com (nz-out-0506.google.com [64.233.162.226])
	by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l1EEVuDO011603
	for <gentoo-user@lists.gentoo.org>; Wed, 14 Feb 2007 14:31:57 GMT
Received: by nz-out-0506.google.com with SMTP id s1so179766nze
        for <gentoo-user@lists.gentoo.org>; Wed, 14 Feb 2007 06:31:56 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=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;
        b=Kx3fX+U3MfudreyG0glZGqRW4sSYGpEYtTLse4t3RmEWiC/TN2ysKgIjV3aoWj1MhudplyCvF5o8pFuJsZz3oHxlMx/C/YQSPYrGDJltFuQcFhH7ClnbQQAG3kXJbxOLupWMnGYyThSNE9kwG/IxW1cD8spotrPhTEqMCmKOEuo=
Received: by 10.115.60.1 with SMTP id n1mr167025wak.1171463516135;
        Wed, 14 Feb 2007 06:31:56 -0800 (PST)
Received: by 10.114.124.8 with HTTP; Wed, 14 Feb 2007 06:31:56 -0800 (PST)
Message-ID: <e9e943910702140631v33e9f45cxe1e6e39bbb00dd69@mail.gmail.com>
Date: Wed, 14 Feb 2007 14:31:56 +0000
From: "Duane Griffin" <duaneg@dghda.com>
Sender: duaneg@gmail.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel randomly locking up, no error messeges, no panics nothing.
In-Reply-To: <d9e14b810702140530h38d874d2n40756ffe3f4c3a7e@mail.gmail.com>
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <d9e14b810702140344g4149853agb423e4bf6e1275cd@mail.gmail.com>
	 <e9e943910702140427j3aea4dep567e6ff3efd53b69@mail.gmail.com>
	 <d9e14b810702140457o64c4ae58g4296b2a52a8d6a2d@mail.gmail.com>
	 <200702141407.10239.volker.armin.hemmann@tu-clausthal.de>
	 <d9e14b810702140530h38d874d2n40756ffe3f4c3a7e@mail.gmail.com>
X-Google-Sender-Auth: 2eeb1f93ab1cc119
X-Archives-Salt: 382bec9e-f196-45d8-9884-dac37f8dff79
X-Archives-Hash: 1237132b80563e9a5f9e0c4bafb6b55c

On 14/02/07, Ivan Lucian Aron <nophinity@gmail.com> wrote:
> I haven't tried vanilla sources

Fair enough, let's see where the problem seems to be, anyway.

> So wait for it to lock again, and check the kernel tasks with
> sysrq-t / echo t >/proc/sysrq-trigger.
> Will get back as soon as I get more info.

Yep. If things are going *very* badly then writing to the system log
may be failing. In that case you can switch to a console and use
SysRq-9 then SysRq-t to send the output to console. Check your system
log first though. Much easier to get it from there than copying things
down by hand or photgraphing your screen!

Cheers,
Duane.

-- 
"I never could learn to drink that blood and call it wine" - Bob Dylan
-- 
gentoo-user@gentoo.org mailing list