linux-kernel - Re: Bisected regression (Was Re: current -git fails to boot on nehalem-ex)

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]

Date:	Thu, 10 Dec 2009 17:06:40 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jens Axboe <jens.axboe@...cle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	linux-kernel@...r.kernel.org, yinghai@...nel.org
Subject: Re: Bisected regression (Was Re: current -git fails to boot on
 nehalem-ex)


* Jens Axboe <jens.axboe@...cle.com> wrote:

> On Thu, Dec 10 2009, Jens Axboe wrote:
> > Hi,
> > 
> > As written in the subject, it just hard hangs before writing anything on
> > the console. With earlyprintk, I captured the failure, see below.
> > 
> > I'll try and bisect this, but it takes some time (since the bios and
> > post process takes forever). I just updated the firmware on the box as
> > well, but it did boot 2.6.32 (and RHEL5 boots fine too). Of course that
> > doesn't rule out a BIOS bug.
> 
> Results are persistent, git bisect points to:
> 
> commit b24c2a925a9837cccf54d50aeac22ba0cbc15455
> Author: Yinghai Lu <yinghai@...nel.org>
> Date:   Tue Nov 24 02:48:18 2009 -0800
> 
>     x86: Move find_smp_config() earlier and avoid bootmem usage
> 
> which appears consistent with the panic(). Reverting that does indeed
> make current -git boot properly.

Thanks. Yinghai, do you have any ideas, or should we revert it?

	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/