From: Peter Zijlstra <peterz@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK_STAT=y
Date: Mon, 16 Feb 2009 13:32:10 +0100 [thread overview]
Message-ID: <1234787530.30178.6.camel@laptop> (raw)
In-Reply-To: <20090216122912.GA6302@elte.hu>
On Mon, 2009-02-16 at 13:29 +0100, Ingo Molnar wrote:
> * Adam J. Richter <adam@yggdrasil.com> wrote:
>
> > Hello Peter and Ingo,
> >
> > Under linux-2.6.29-rc5, and I believe all earlier 2.6.29-rc
> > releases, CONFIG_LOCK_STAT=y causes my system to hang at boot when
> > booting from lilo-22.8. Linux-2.6.28 does not have this hang.
> > Disabling LOCK_STAT or booting from grub avoids the hang. These are
> > sufficient workarounds for me, but I document it here in case anyone
> > else is seeing something similar or wants to take a deeper look at it.
>
> hm, so if booting from LILO you see a hang, while when booting with GRUB
> it works fine?
>
> Could it be LILO messing up the kernel image loading somehow? LOCK_STAT
> might just be the thing that brings the kernel over a specific size.
There used to be an issue long ago on s390 where the per-cpu section was
stomping on the initrd or something similar. Lockstat generates a huge
per-cpu BSS section.
next prev parent reply other threads:[~2009-02-16 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-16 6:50 2.6.29-rc5 hanging at boot when CONFIG_LOCK_STAT=y Adam J. Richter
2009-02-16 12:29 ` Ingo Molnar
2009-02-16 12:32 ` Peter Zijlstra [this message]
2009-02-16 19:51 ` Adam J. Richter
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=1234787530.30178.6.camel@laptop \
--to=peterz@infradead.org \
--cc=adam@yggdrasil.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=yinghai@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox