From: Yinghai <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Bisected regression (Was Re: current -git fails to boot on nehalem-ex)
Date: Thu, 10 Dec 2009 09:26:45 -0800 [thread overview]
Message-ID: <67EA4830-231F-45C9-A1A6-CE1C6CD9493D@kernel.org> (raw)
In-Reply-To: <20091210160640.GB27794@elte.hu>
On Dec 10, 2009, at 8:06 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jens Axboe <jens.axboe@oracle.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@kernel.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?
>
Let find the root cause
Jen
Can you boot with earlyconsole or earlyprintk and debug?
YH
next prev parent reply other threads:[~2009-12-10 17:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 9:10 current -git fails to boot on nehalem-ex Jens Axboe
2009-12-10 10:39 ` Bisected regression (Was Re: current -git fails to boot on nehalem-ex) Jens Axboe
2009-12-10 16:06 ` Ingo Molnar
2009-12-10 17:26 ` Yinghai [this message]
2009-12-10 18:07 ` Jens Axboe
2009-12-10 18:34 ` Yinghai Lu
2009-12-10 18:41 ` Bisected regression Roland Dreier
2009-12-10 18:44 ` Jens Axboe
2009-12-10 19:13 ` Yinghai Lu
2009-12-10 18:44 ` Yinghai Lu
2009-12-10 18:42 ` Bisected regression (Was Re: current -git fails to boot on nehalem-ex) Yinghai Lu
2009-12-10 18:45 ` Jens Axboe
2009-12-10 19:07 ` Jens Axboe
2009-12-10 19:19 ` Yinghai Lu
2009-12-10 19:26 ` Jens Axboe
2009-12-10 19:34 ` Bisected regression Roland Dreier
2009-12-10 21:07 ` Bisected regression (Was Re: current -git fails to boot on nehalem-ex) Yinghai Lu
2009-12-10 21:15 ` Jens Axboe
2009-12-10 22:39 ` H. Peter Anvin
2009-12-10 22:45 ` Yinghai Lu
2009-12-10 22:54 ` H. Peter Anvin
2009-12-10 22:47 ` Bisected regression Roland Dreier
2009-12-10 22:50 ` H. Peter Anvin
2009-12-11 8:19 ` Bisected regression (Was Re: current -git fails to boot on nehalem-ex) Jens Axboe
2009-12-11 8:32 ` Ingo Molnar
2009-12-11 8:55 ` [tip:x86/urgent] x86: Use find_e820() instead of hard coded trampoline address tip-bot for Yinghai Lu
2009-12-10 19:28 ` Bisected regression Roland Dreier
2009-12-10 19:33 ` Yinghai Lu
2009-12-10 19:36 ` Roland Dreier
2009-12-10 19:50 ` Yinghai Lu
2009-12-10 22:44 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=67EA4830-231F-45C9-A1A6-CE1C6CD9493D@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®