ahci 0000:00:1f.2: controller reset failed (0xffffffff)
in [Kernel]
|
Prev: linux-next: manual merge of the v4l-dvb tree with Linus' tree
Next: kernel: local_irq_{save,restore}_nmi()
From: Yinghai on 6 Apr 2010 21:20 On 04/06/2010 03:54 PM, Andy Isaacson wrote: > This Dell Precision WorkStation T3400 doesn't boot 2.6.34-rc1 (tried > 522dba71). 2.6.33 was fine, and it's been running various stable > kernels for the last 18 months. Unfortunately I can't reasonably bisect > as I need this machine to be usable, but I can test specific patches or > options. (three or four reboots is fine, 15 is not.) > > full dmesg from failing boot and a successful boot at > http://web.hexapodia.org/~adi/tmp/20100406-pci-ahci-reset-fail/ > > I suspect it's due to: > > [ 3.094038] pci 0000:00:1f.2: no compatible bridge window for [mem 0xff970000-0xff9707ff] > [ 3.103001] pci 0000:00:1f.2: can't reserve [mem 0xff970000-0xff9707ff] > > so I've CCed a few recent committers to setup-res.c. > can you try to boot with pci=nocrs ? also please check with -rc4. YH -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: H. Peter Anvin on 12 Apr 2010 22:00
On 04/12/2010 10:56 AM, Bjorn Helgaas wrote: > > Linux thinks the windows are: > 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] > > The 0xa0000-0xbffff one makes good sense. That's normally MMIO that's > routed via PCI to the VGA device frame buffer, and we should be able > to figure out how to avoid that area, e.g., by using BIOS info, PCI > class codes, etc. > > Now we need to figure how to avoid the 0xc0000-0xeffff and 0xf0000-0xfffff > windows. Maybe there's something special about how ACPI describes them. > > Or maybe we're just unlucky because these are the first windows in the > _CRS list, and Linux tries them in order, while Windows uses a different > strategy. > I strongly suspects that Windows knows that < 1 MB is special, and only ever assigns it upon explicit allocation. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |