[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1234787530.30178.6.camel@laptop>
Date: Mon, 16 Feb 2009 13:32:10 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Ingo Molnar <mingo@...e.hu>
Cc: "Adam J. Richter" <adam@...drasil.com>,
"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK_STAT=y
On Mon, 2009-02-16 at 13:29 +0100, Ingo Molnar wrote:
> * Adam J. Richter <adam@...drasil.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists