[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0607171242440.6761@scrub.home>
Date: Mon, 17 Jul 2006 12:52:28 +0200 (CEST)
From: Roman Zippel <zippel@...ux-m68k.org>
To: Uwe Bugla <uwe.bugla@....de>
cc: Valdis.Kletnieks@...edu, linux-kernel@...r.kernel.org,
akpm@...l.org, johnstul@...ibm.com
Subject: Re: i686 hang on boot in userspace
Hi,
On Fri, 14 Jul 2006, Uwe Bugla wrote:
> Hi everybody,
> first of all thanks to the explanatory hints how a magic Sysrq key works – I've learned a lot.
>
> I first pressed ALT + PrintScreen + P, then ALT + PrintScreen + T.
> To avoid wordwrapping or other unwanted effects please see the resulting kern.log as outline attachment.
>
> Could someone please explain to me what's behind that cryptic code?
It shows what the kernel is currently is doing and where it's spending the
time.
First, your kernel buffer log buffer seems a little small, so not
everything is captured. Could you increase the number in the "Kernel log
buffer size" option (it's in the "Kernel debugging" part of the "Kernel
hacking" menu).
Second, could you press ALT+PrintScreen+P a few more times (maybe around
10 at least) while the kernel hangs? This would should where the cpu is
spending its time and whether it's at a single place or at different
places.
Thanks.
bye, Roman
Powered by blists - more mailing lists