linux-kernel - Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 16 Feb 2009 13:29:12 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	"Adam J. Richter" <adam@...drasil.com>,
	"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>
Cc:	peterz@...radead.org, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.29-rc5 hanging at boot when CONFIG_LOCK_STAT=y


* 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.

	Ingo
--
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/