[+cc Yinghai] Hi Guenter, On Fri, May 15, 2015 at 12:28 PM, Guenter Roeck <groeck@xxxxxxxxxxx> wrote: > Hi all, > > ever since 3.18(ish), we see lots of pcie io range allocation error messages > when booting our systems. > > pcieport 0000:02:00.0: res[7]=[io 0x1000-0x0fff] get_res_add_size add_size 1000 > pcieport 0000:02:00.0: BAR 7: no space for [io size 0x1000] > pcieport 0000:02:00.0: BAR 7: failed to assign [io size 0x1000] > > This is repeated for each port. > > What we atually _want_ is no IO address range, but so far I have not been able to > tell this to the code (or to the bridge). What information does the core have that we could use to figure out that you want no I/O space? For example, does the host bridge have no I/O apertures? Or are there no devices below 02:00.0 that require I/O space? If you can post a complete dmesg log, that should contain this information. I think we currently will try to assign enough I/O space for any I/O BARs below the bridge. Or, if the bridge supports hotplug, we will try to assign at least pci_hotplug_io_size, which defaults to 256. > The IO space "0x1000-0xfff" gives an indication of what is going on, at least > to some degree. The io range is calculated in pbus_size_io() as > b_res->start = min_align; > b_res->end = b_res->start + size0 - 1; > with size0 == 0, so end < start. > > Searching for the get_res_add_size and the BAR7 message suggests that many > others see the problem as well, so it appears that we are not alone. > I have not been able to find a solution, though. > > Any idea what we may have to do to fix the problem, or in other words > what may be wrong ? Is the problem that some device doesn't work, or is it just extra annoying messages. We should fix something in either case, of course, but it's more urgent if a device used to work but no longer does. 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
