public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Youquan Song <youquan.song@linux.intel.com>
To: "S.Çağlar Onur" <caglar@CS.Princeton.EDU>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	Greg KH <greg@kroah.com>, "stable@kernel.org" <stable@kernel.org>,
	"hpa@zytor.com" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Song, Youquan" <youquan.song@intel.com>
Subject: Re: [stable] Boot failure with 2.6.27.46 on Xeon E5620 (Westmere EP)
Date: Wed, 26 May 2010 09:23:57 -0400	[thread overview]
Message-ID: <20100526132357.GA26728@youquan-linux.bj.intel.com> (raw)
In-Reply-To: <DD6ACA75-527D-406D-971B-64F042E0ED26@CS.Princeton.EDU>

> > I can't think of any known issues in 2.6.27 that can lead to this kind
> > of boot failure on WSM-EP. Caglar, It will be nice if you can do git
> > bisect between working and non-working kernels.
> 
> Sure, I'll try to boot those with plain 2.6.27 to see but please note that it's going to be little time consuming. For each one I have to create a custom boot image for them to download and test (a.k.a. don't expect to hear from me soon :))

Hi Caglar,

What's the microcode version? Get by "dmesg | grep microcode" if you
success boot other version of kernel.
Can you try to disable C-state(C6) in BIOS before your boot 2.6.27?

Thanks
-Youquan

  reply	other threads:[~2010-05-26  5:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25 15:10 Boot failure with 2.6.27.46 on Xeon E5620 (Westmere EP) "S.Çağlar Onur"
2010-05-25 15:53 ` [stable] " Greg KH
2010-05-25 20:32   ` "S.Çağlar Onur"
2010-05-25 20:51     ` Greg KH
2010-05-26  0:24       ` Suresh Siddha
2010-05-26  3:29         ` "S.Çağlar Onur"
2010-05-26 13:23           ` Youquan Song [this message]
2010-11-18 21:24             ` "S.Çağlar Onur"
2010-11-18 21:54               ` Greg KH
2010-11-18 21:59                 ` "S.Çağlar Onur"
2010-11-18 22:06                   ` Greg KH
2010-06-02 23:54         ` "S.Çağlar Onur"
2010-06-03 16:40           ` Greg KH
2010-06-03 17:50             ` "S.Çağlar Onur"

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=20100526132357.GA26728@youquan-linux.bj.intel.com \
    --to=youquan.song@linux.intel.com \
    --cc=caglar@CS.Princeton.EDU \
    --cc=greg@kroah.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=youquan.song@intel.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