On 4/8/2018 5:21 PM, David Miller wrote: > From: Meelis Roos <mroos@xxxxxxxx> > Date: Sun, 8 Apr 2018 21:44:57 +0300 (EEST) > >> This is a followup on the thread https://lkml.org/lkml/2015/10/7/135 and >> corresponding https://bugzilla.kernel.org/show_bug.cgi?id=117191 entry. >> >> I saw some sparc64 PCI allocation changes in yesterdays git and compiled >> 4.16.0-10242-gf605ba9 on most of my sparc64 machines to test if the PCI >> BAR allocation problems introduced in 4.3 were fixed on some of them. >> Alas, no change at all - of the test machines, none showed any changes >> in the error messages in "dmesg | grep BAR". >> >> There was one test machine, T1000 with no addon cards, that did not >> encounter any problem, before or after the recent patch. All the other >> test machines tried still have the BAR allocation problems. >> >> The errors seem to cluster into 3 categories: >> >> 1. many devices fail BAR allocations >> 2. one of the Davicom Ethernet devices fails BAR allocation >> 3. Uli ISA bridge fails BAR allocation. >> >> Full current dmesg and lspci info is also available if there is any >> interest. I did not include it all here, which machines are interesting? > > PCI folks, please look into this. > > A regression like this should not linger since 4.3, thank you. > It sounds like a FW issue. Does the problem go away when you boot with pci=realloc kernel command line? -- Sinan Kaya Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc. Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
