On Tue, Aug 23, 2011 at 4:55 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> Rogério, thanks for doing all the work of bisecting. I know that's
> slow and painful. Can you please attach the complete dmesg log from a
> current upstream kernel with 12c22d6ef2 reverted? While you're at it,
> you might also try a boot of plain vanilla upstream with the
> "pci=use_crs" kernel option.
Sadly, there's no way we'll revert that revert right now, but we could
certainly try it in the next merge window.
We've made enough changes to the resource allocations since, that
maybe we can try that "remove transparent bridge sizing" thing again.
That said, it would be really interesting to also see the output from
the *broken* kernel, if there is some way to get it out of it sanely.
Like a serial console or so, with PCI debugging enabled
(CONFIG_PCI_DEBUG), and perhaps "pci=earlydump".
There's probably some hidden system IO port or something that we just
happen to stomp on given some random resource allocation. And it would
be nice to try to figure it out, and fix it for real, rather than just
have a "ok, we can make things work by randomly changing PCI
allocations"..
Linus
--
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
