From: john stultz <johnstul@us.ibm.com>
To: Uwe Bugla <uwe.bugla@gmx.de>
Cc: Roman Zippel <zippel@linux-m68k.org>,
Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
akpm@osdl.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: i686 hang on boot in userspace
Date: Fri, 14 Jul 2006 12:43:22 -0700 [thread overview]
Message-ID: <1152906202.5365.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20060714150418.120680@gmx.net>
On Fri, 2006-07-14 at 17:04 +0200, 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?
> Hope I could help - still need a booting kernel, and I think I ain´t the only one.
Hmmm... I don't see anything that sticks out in the sysrq info (well,
not sure if the do_wp_page() is just trace junk or not - CC'ed Peter
just in case). Maybe this is related to the expand files OOM thing that
Martin saw?
If you boot w/ init=/bin/bash do you also see the hang? If you execute
"date" a few times, does it seem to keep proper track of time?
Also could you enable softlockup detection? (CONFIG_DETECT_SOFTLOCKUP)
Which you can find under Kernel debugging in the make menuconfig.
thanks
-john
next parent reply other threads:[~2006-07-14 19:43 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060714150418.120680@gmx.net>
2006-07-14 19:43 ` john stultz [this message]
2006-07-17 10:52 ` i686 hang on boot in userspace Roman Zippel
2006-07-17 11:09 ` Roman Zippel
2006-07-17 13:38 ` Uwe Bugla
2006-07-17 14:17 ` Roman Zippel
2006-07-17 14:59 ` gmu 2k6
2006-07-17 15:21 ` Roman Zippel
2006-07-17 15:58 ` gmu 2k6
2006-07-17 16:02 ` gmu 2k6
2006-07-17 17:03 ` Roman Zippel
2006-07-17 18:15 ` gmu 2k6
2006-07-17 18:17 ` gmu 2k6
2006-07-18 9:38 ` gmu 2k6
2006-07-19 10:26 ` gmu 2k6
2006-07-24 15:34 ` gmu 2k6
2006-07-25 7:32 ` Jens Axboe
2006-07-25 8:00 ` gmu 2k6
2006-07-25 7:41 ` Jens Axboe
[not found] ` <f96157c40607250120s2554cbc6qbd7c42972b70f6de@mail.gmail.com>
[not found] ` <20060725080002.GD4044@suse.de>
2006-07-25 8:28 ` gmu 2k6
2006-07-25 8:08 ` Jens Axboe
2006-07-25 9:17 ` gmu 2k6
2006-07-25 8:57 ` Jens Axboe
2006-07-25 10:09 ` gmu 2k6
2006-07-25 9:46 ` Jens Axboe
2006-07-25 10:19 ` gmu 2k6
2006-07-25 10:41 ` Jens Axboe
2006-07-25 9:20 ` gmu 2k6
2006-07-25 8:57 ` Jens Axboe
2006-07-25 9:35 ` gmu 2k6
2006-07-25 9:24 ` Jens Axboe
2006-07-25 11:29 ` Jens Axboe
2006-07-25 12:47 ` gmu 2k6
2006-07-25 12:52 ` Jens Axboe
2006-07-25 12:58 ` Jens Axboe
2006-07-25 14:27 ` gmu 2k6
2006-07-25 14:29 ` gmu 2k6
2006-07-25 15:18 ` Jens Axboe
2006-07-25 13:13 ` gmu 2k6
2006-07-25 14:50 ` gmu 2k6
2006-07-25 15:19 ` Jens Axboe
2006-07-25 18:58 ` gmu 2k6
2006-07-25 19:21 ` Jens Axboe
2006-07-25 19:28 ` gmu 2k6
2006-07-25 9:51 ` gmu 2k6
2006-07-25 9:42 ` Jens Axboe
2006-07-17 16:11 ` gmu 2k6
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1152906202.5365.12.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uwe.bugla@gmx.de \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.