Hah Bjorn, you are awesome. It's fascinating to have someone able tell a
story based on those debug messages, which were previously unreadable
to me!
I'm going to fetch Yinghai's patches now, and will keep you
posted. Thanks so much for the help!
Andy B.
On 23/04/10 10:19 -0600, Bjorn Helgaas wrote:
On Friday 23 April 2010 07:34:27 am R. Andrew Bailey wrote:
CR is 15841. I finally managed to find my null modem adapter, which
has been missing for months, and managed to get you a serial boot
dump. The fact that its so much longer than the other two makes me a
little suspicious that I screwed up the other two, let me know if
anything appears to be missing.
Here's the bugzilla as a link for easy clicking:
https://bugzilla.kernel.org/show_bug.cgi?id=15841
Thanks a lot for the quick response -- and I know from personal
experience what a hassle it can be to set up a serial console :-)
I think this is the same as this problem:
https://bugzilla.kernel.org/show_bug.cgi?id=15744
This is from your "ahci enabled, crs enabled" log:
pci_root PNP0A03:00: host bridge window [mem 0x000a0000-0x000bffff]
pci_root PNP0A03:00: host bridge window [mem 0x000c0000-0x000effff]
pci_root PNP0A03:00: host bridge window [mem 0x000f0000-0x000fffff]
pci_root PNP0A03:00: host bridge window [mem 0xf0000000-0xfebfffff]
pci_root PNP0A03:00: host bridge window [mem 0xcff00000-0xdfffffff]
pci_root PNP0A03:00: host bridge window [mem 0xff980800-0xff980bff]
pci_root PNP0A03:00: host bridge window [mem 0xff97c000-0xff97ffff]
pci_root PNP0A03:00: host bridge window [mem 0xfed20000-0xfed9ffff]
pci_root PNP0A03:00: host bridge window [mem 0xfedad800-0xfedadfff]
pci 0000:00:1f.2: no compatible bridge window for [mem 0xff970000-0xff9707ff]
pci 0000:00:1f.2: BAR 5: assigned [mem 0x000a0000-0x000a07ff]
pci 0000:00:1f.2: BAR 5: set to [mem 0x000a0000-0x000a07ff] (PCI address [0xa0000-0xa07ff]
ahci 0000:00:1f.2: controller reset failed (0xffffffff)
It looks like the BIOS put the AHCI controller (1f.2) at 0xff970000,
which doesn't fit in any of the host bridge windows. Therefore, Linux
moved the device, and we put it at 0xa0000. Unfortunately, there is
already a legacy VGA device there, so that was a bad choice.
Yinghai has some patches to address this. The most recent ones are
here: http://lkml.org/lkml/2010/4/21/22
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
