linux-kernel - Re: Boot hangs after "Freeing initrd memory" with 2.6.31.11

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: <4B53B218.6000607@zytor.com>
Date:	Sun, 17 Jan 2010 16:58:00 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ozan Çağlayan <ozan@...dus.org.tr>
CC:	Yinghai Lu <yinghai@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	mingo@...e.hu, a.p.zijlstra@...llo.nl, jaswinder@...nel.org,
	stable@...nel.org, "Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Boot hangs after "Freeing initrd memory" with 2.6.31.11

On 01/16/2010 04:28 AM, Ozan Çağlayan wrote:
> 
> Linux 2.6.31 is released on Sep 9th. So people having an Athlon XP processor + a kernel newer than 4 months
> which enables CONFIG_X86_CPU_DEBUG can't even boot into a linux kernel. I was *at least* expecting a comment from the relevant
> people but nope for 2 days.
> 
> It seems to be a serious regression which doesn't get caught. I'm also CC'ing Rafael, maybe he can inject this
> in one of his regression threads.
> 

Anything which involves enabling CONFIG_X86_CPU_DEBUG can hardly be
considered serious.  It's a broken piece of work that should never have
gotten into the kernel in the first place.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

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