On Fri, Aug 16, 2013 at 4:05 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote: > On Tue, Aug 6, 2013 at 11:41 PM, Leon Ravich <lravich@xxxxxxxxx> wrote: >> From comparison of pci printout from the two kernel , >> beside the EDAC errors I noticed other strange differences: >> >> In 3.8.13 I got BAR 7 and BAR 8: >> [ 39.017749] pci 0000:00:00.0: BAR 8: assigned [mem 0xc0000000-0xdfffffff] >> [ 39.024530] pci 0000:00:00.0: BAR 7: can't assign io (size 0x10000) >> >> In 3.8.13 I am getting: >> [ 38.931873] pci_bus 0000:01: busn_res: can not insert [bus 01-ff] >> under [bus 00-01] (conflicts with (null) [bus 00-01]) >> >> >> On 6 August 2013 09:32, Leon Ravich <lravich@xxxxxxxxx> wrote: >>> Thanks Bjorn. > > Is this still a problem, or have you found a solution in the meantime? > >>> 1) If I understand it right this patch only removes the "pci >>> 0000:00:00.0: ignoring class 0x0b2000 (doesn't >>> match header type 01)" message , don't care about it , had it before . > > It also affects how the PCI core handles the device. But as you said, > if you had the message before, it's probably not the cause of the > current problem. > >>> 2) regarding the comparing of printouts: > > Can you post the complete logs somewhere, maybe in a bugzilla or similar? > > Where are the "PCIE ERR_CAP_STAT" and similar messages from? My quick > grep didn't find them. Did this problem ever get resolved? Is there anything we need to look at? 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
