linux-kernel - Re: [Bug #15518] CONFIG_NO_BOOTMEM=y breaks boot on 32bit

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]

Message-ID: <20100324170016.GB3552@viiv.ffwll.ch>
Date:	Wed, 24 Mar 2010 18:00:16 +0100
From:	Daniel Vetter <daniel@...ll.ch>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Daniel Vetter <daniel@...ll.ch>
Subject: Re: [Bug #15518] CONFIG_NO_BOOTMEM=y breaks boot on 32bit

On Sun, Mar 21, 2010 at 09:13:28PM +0100, Rafael J. Wysocki wrote:
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=15518
> Subject		: CONFIG_NO_BOOTMEM=y breaks boot on 32bit
> Submitter	: Daniel Vetter <daniel@...ll.ch>
> Date		: 2010-03-11 15:37 (11 days old)

I've just retested on 3.6.34-rc2. NO_BOOTMEM=y still crashes with a
plethora of backtraces somewhere in early boot. Disabling this option
still works around the problem
-- 
Daniel Vetter
Mail: daniel@...ll.ch
Mobile: +41 (0)79 365 57 48
--
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/