mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Ingo Molnar <mingo@kernel.org>,
	Michael Wang <wangyun@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: TIP tree's master branch failed to boot up
Date: Mon, 10 Dec 2012 07:28:12 -0800	[thread overview]
Message-ID: <227554ec-58bc-4c8d-aaf7-b0c9073b6e18@email.android.com> (raw)
In-Reply-To: <20121210105449.GC7264@gmail.com>

Yes, the current x86/microcode is broken, I have been trying to work with Fenghua on a fix but didn't get one before the weekend.

Ingo Molnar <mingo@kernel.org> wrote:

>
>I've Cc:-ed hpa, he merged the x86/microcode bits.
>
>Michael Wang, I've excluded x86/microcode from the latest 
>version of the -tip tree which I just pushed out:
>
>  4e00fd4c93e0 Merge branch 'x86/cleanups'
>
>Can you confirm that your server boots now?
>
>Thanks,
>
>	Ingo
>
>* Michael Wang <wangyun@linux.vnet.ibm.com> wrote:
>
>> On 12/10/2012 12:50 PM, Michael Wang wrote:
>> > Hi, Folks
>> > 
>> > I'm testing with the latest tip tree's master branch 3.7.0-rc8 and
>> > failed to boot up my server, it's hung at very beginning and I
>could not
>> > catch any useful log, is there any one else got this problem or I'm
>the
>> > only one?.
>> 
>> And bisect catch below commit:
>> 
>> commit 56e7dba100a50f674627a3764fd4da4a6ec93295
>> Merge: ea8432f 16544f8
>> Author: Ingo Molnar <mingo@kernel.org>
>> Date:   Fri Dec 7 12:13:11 2012 +0100
>> 
>>     Merge branch 'x86/microcode'
>> 
>> Regards,
>> Michael Wang
>> 
>> 
>> > 
>> > Regards,
>> > Michael Wang
>> > 
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/

-- 
Sent from my mobile phone. Please excuse brevity and lack of formatting.

  reply	other threads:[~2012-12-10 15:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10  4:50 Michael Wang
2012-12-10  7:39 ` Michael Wang
2012-12-10 10:54   ` Ingo Molnar
2012-12-10 15:28     ` H. Peter Anvin [this message]
2012-12-11  2:35     ` Michael Wang
2012-12-10 17:02 ` H. Peter Anvin
2012-12-11  2:22   ` Michael Wang
2012-12-11  2:34     ` H. Peter Anvin
2012-12-11  2:39       ` Michael Wang

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=227554ec-58bc-4c8d-aaf7-b0c9073b6e18@email.android.com \
    --to=hpa@zytor.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=wangyun@linux.vnet.ibm.com \
    /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®