Messages in this thread | | | Date | Tue, 15 Dec 2009 13:14:37 +0100 | From | Jens Axboe <> | Subject | Re: kexec boot regression |
| |
On Tue, Dec 15 2009, Yinghai Lu wrote: > Jens Axboe wrote: > > Hi, > > > > I have this big box that takes forever to boot, so I use kexec to boot > > into new kernels. Works fine, but some time past 2.6.32 it stopped > > working. Instead of wasting brain cycles on finding out why, I handed > > the problem to my trusty regression friend - git bisect. > > > > This is what it found (sorry Yinghai it's you again, you owe me a beer > > for hours of 2.6.32-git bisecting ;-) > > sure. > > > > > > > 99935a7a59eaca0292c1a5880e10bae03f4a5e3d is the first bad commit > > commit 99935a7a59eaca0292c1a5880e10bae03f4a5e3d > > Author: Yinghai Lu <yinghai@kernel.org> > > Date: Sun Oct 4 21:54:24 2009 -0700 > > > > x86/PCI: read root resources from IOH on Intel > > > > For intel systems with multi IOH, we should read peer root resources > > directly from PCI config space, and don't trust _CRS. > > > > > > I could not revert this single commit, as a further commit made other > > changes. So I reverted 67f241f4 first and then 99935a7a. I confirmed > > that this kernel then works fine. > > > > let see how BIOS mess it up again!
Heh, I had a feeling this was coming :-)
> please.
Please find two logs attached - one from a boot with -git and the two patches reverted, and one from a boot with -git.
-- Jens Axboe
[unhandled content-type:application/octet-stream][unhandled content-type:application/octet-stream] | |