linux-kernel - Re: Config NO_BOOTMEM breaks my amd64 box

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4BB3DC4E.7030504@zytor.com>
Date:	Wed, 31 Mar 2010 16:35:42 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	James Morris <jmorris@...ei.org>
CC:	Ingo Molnar <mingo@...e.hu>, Yinghai Lu <yinghai@...nel.org>,
	linux-kernel@...r.kernel.org, airlied@...ux.ie,
	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: Config NO_BOOTMEM breaks my amd64 box

On 03/31/2010 03:58 PM, James Morris wrote:
> On Wed, 31 Mar 2010, Ingo Molnar wrote:
> 
>>>
>>> Yes, it was happening with -rc3.
>>
>> Could you please send the bootlog that Yinghai asked for, plus also one that 
>> you get with NO_BOOTMEM turned off (for comparison)?
> 
> I don't have the old boot logs, and have since upgraded the system 
> further.  
> 

Upgraded how?  The problem no longer happens?

> IIRC, the boot was failing after not being able to find the root fs 
> (ext3/lvm/raid0).  I thought it was a dracut issue, but it seemed to be 
> fixed by enabling bootmem.

This would rather match the problem that was addressed by the patch in
-rc3.  Any help in reproducing it would be great.

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