On Monday 26 April 2010 06:50:32 am R. Andrew Bailey wrote: > On 23/04/10 17:05 -0600, Bjorn Helgaas wrote: > >On Wednesday 21 April 2010 01:31:20 pm Andy Isaacson wrote: > >Would you guys (Andy & Andy, what a coincidence :-)) mind giving > >it a try? This is intended to work on top of current upstream, > >with no other patches required. > > > Good news- that solved it. I tried Yinghai's patches saturday to no > avail (sorry it took me so long to get back to you, I was about 5 bios > revisions behind on this machine and wanted to update it before I > tried any more tests). Great, thanks for testing this! The only problem here is that we changed two things at once -- the BIOS and the patch, and we need to figure out which change fixed the problem. I want Linux to work correctly even on the old BIOS, on the theory that "if Windows works, Linux should work, too." Changing a BIOS is relatively risky, and it's not something I want users to have to diagnose and deal with. If we're lucky, the kernel without the patch will still fail on the updated BIOS. If the pre-patch kernel fails and the post-patch kernel works, and you can attach the entire dmesg log of the post-patch kernel to the bugzilla, we should be able to see Linux making more sensible BAR assignments when working around the BIOS bug. Then we can be pretty confident that my patch fixed the problem. If the pre-patch kernel works on the updated BIOS, that means one of the BIOS updates fixed the BIOS bug, and we didn't actually exercise my patch at all. If that's the case, we'll have to wait for a report from the other Andy. (Or you could temporarily down-grade your BIOS to the original version you had. But I don't know whether that's even possible... it probably depends on the BIOS update tools.) Thanks again for all your help. All progress in Linux depends on early adopters like you who are willing to test kernels and help work through issues :-) Bjorn -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
