Messages in this thread | | | Date | Thu, 18 Nov 2010 14:06:39 -0800 | From | Greg KH <> | Subject | Re: [stable] Boot failure with 2.6.27.46 on Xeon E5620 (Westmere EP) |
| |
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 -- 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/
| |