From: Greg KH <greg@kroah.com>
To: "S.Çağlar Onur" <caglar@CS.Princeton.EDU>
Cc: Youquan Song <youquan.song@linux.intel.com>,
Suresh Siddha <suresh.b.siddha@intel.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: Thu, 18 Nov 2010 14:06:39 -0800 [thread overview]
Message-ID: <20101118220639.GA956@kroah.com> (raw)
In-Reply-To: <42E89D5B-D2D6-42E5-A218-B538968FF6E5@CS.Princeton.EDU>
On Thu, Nov 18, 2010 at 04:59:12PM -0500, "S.Çağlar Onur" wrote:
> Hi Greg,
>
> On Nov 18, 2010, at 4:54 PM, Greg KH wrote:
>
> > On Thu, Nov 18, 2010 at 04:24:40PM -0500, "S.Çağlar Onur" wrote:
> >> Hi Youquan & Greg,
> >>
> >>
> >> On May 26, 2010, at 9:23 AM, Youquan Song wrote:
> >>
> >>>>> 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?
> >>
> >> First of all I'm really sorry that it took really long time to reply this mail as I was waiting Dell to send a loaner machine to us. This morning I've got the hardware and following patch solved the boot problem that I was observing, Greg could you consider adding that to 2.6.27-stable tree?
> >>
> >> commit a0bf284bfedd6dc95bbee7ebf5ccf3b5f753a008
> >
> > No problem, now queued up.
>
> Umh please drop that patch for now, seems like I mixed my kernel
> configs and compiled/tested a 64 bit one (by the way 64bit kernel
> boots fine) but 32bit one still fails with the same error. I'll try to
> bisect...
Heh, ok, I'll go drop it now :)
that's what I get for trying to be quick...
thanks,
greg k-h
next prev parent reply other threads:[~2010-11-18 22:07 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
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 [this message]
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=20101118220639.GA956@kroah.com \
--to=greg@kroah.com \
--cc=caglar@CS.Princeton.EDU \
--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 \
--cc=youquan.song@linux.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