Re: BAR 14: can't assign mem (size 0x200000)
From: Parag Warudkar
Date: Sat Mar 29 2014 - 20:15:30 EST
On Sat, Mar 29, 2014 at 1:19 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> wrote:
> [+cc Rafael, linux-pci, linux-acpi]
> On Sat, Mar 29, 2014 at 09:41:20AM -0700, Linus Torvalds wrote:
>> Parag, can you add a WARN_ON_ONCE() to that message, so that we see
>> what the call chain is for it.
> I think we likely get a Bus Check notification when resuming, so we're
> probably in this path:
> acpi_hotplug_execute(acpi_device_hotplug, ...)
> acpi_pci_root_scan_dependent # .hotplug.scan_dependent
> dev_printk("Allocating resources")
> It seems like we ought to do the equivalent of a Bus Check from the
> root at boot-time, even if we don't receive an explicit Bus Check
> notification then (ACPI 5.0, sec 5.6.6, says "OSPM will typically
> perform a full enumeration automatically at boot time, but after
> system initialization it is the responsibility of the ACPI AML code to
> notify OSPM whenever a re-enumeration operation is required"), but I
> don't think we do, which makes the resume path different from the boot
> Parag, would you mind collecting an acpidump and attaching it to the
> bugzilla below?
I have attached a single acpidump to the bugzilla.
I realized that I misspoke when I said VTd makes a difference.
Actually on 3.14 exact same message appears on resume irrespective of
whether or not VTd is enabled.
However on 3.11 (3.11.0-18-generic Ubuntu LTS latest kernel) - I don't
see those messages irrespective of VTd status.
I must have accidentally booted into 3.11 kernel after disabling VTd
and thought the messages went away because of disabling VTd.
So we can ignore the VTd part.
> Is this a regression? I guess you said that the message (and the sec-
> latency change, which I don't think is applicable to PCIe anyway) are
> the only ill effects you see, so it might not be too serious even if
> it is.
Not sure if Ubuntu includes any patches on top of 3.11 mainline that
make a difference to this issue - but in case they don't this might be
About the seriousness part - I am not seeing any issues in my regular
use. Not sure what that bridge does and if there are any specific
devices involved - so it might just be that I am not using anything
that could be problematic due to this issue.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/