"ignoring host bridge windows from ACPI" in a recent laptop

"ignoring host bridge windows from ACPI" in a recent laptop

[Bernd Petrovitsch]

[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]

Hi!

I have a Sony Vaio VPCF11M1E since early this year. Looking through the
output of `dmesg`, I noticed
----  snip  ----
pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
----  snip  ----
So I tried that.
The laptop boots and works without problems so far. I attached a diff of
the first approx. 630 lines of the `dmesg` outputs without and with the
above parameter. It gets pretty messy afterwards because (at least) the
USB and/or SATA initialization runs apparently in parallel.

After finding http://lkml.org/lkml/2010/2/12/174, it seems that we might
need another quirk to activate that automatically.

At the end, I lost also dozens of
----  snip  ----
name_count maxed, losing inode data: dev=00:07, inode=
----  snip  ----
lines (which are also not in the attached diff). I don't know if that
has something to do with the above.

I can provide the full diff and/or the two dmesg outputs (and pretty
much anything else - just tell me what you need).

	Bernd
-- 
mobile: +43 664 4416156              http://www.sysprog.at/
    Linux Software Development, Consulting and Services

[-- Attachment #2: added-pci=use_crs.diff --]
[-- Type: text/x-patch, Size: 6030 bytes --]

--- dmesg-orig.txt	2010-06-15 12:37:48.719905180 +0200
+++ dmesg-nn.txt	2010-06-15 13:06:54.803976765 +0200
@@ -1,7 +1,7 @@
 Initializing cgroup subsys cpuset
 Initializing cgroup subsys cpu
 Linux version 2.6.33.5-112.fc13.x86_64 (mockbuild@x86-09.phx2.fedoraproject.org) (gcc version 4.4.4 20100503 (Red Hat 4.4.4-2) (GCC) ) #1 SMP Thu May 27 02:28:31 UTC 2010
-Command line: ro root=/dev/mapper/vg_tumunzahar-lv_root nomodeset LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys vga=0x318
+Command line: ro root=/dev/mapper/vg_tumunzahar-lv_root nomodeset LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys vga=0x318 maxcpus=4 pci=use_crs
 BIOS-provided physical RAM map:
  BIOS-e820: 0000000000000000 - 000000000009e800 (usable)
  BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved)
@@ -192,7 +192,7 @@
 pcpu-alloc: [0] 0 1 2 3 4 5 6 7 
 Built 1 zonelists in Node order, mobility grouping on.  Total pages: 1010684
 Policy zone: Normal
-Kernel command line: ro root=/dev/mapper/vg_tumunzahar-lv_root nomodeset LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys vga=0x318
+Kernel command line: ro root=/dev/mapper/vg_tumunzahar-lv_root nomodeset LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=de-latin1-nodeadkeys vga=0x318 maxcpus=4 pci=use_crs
 PID hash table entries: 4096 (order: 3, 32768 bytes)
 Checking aperture...
 No AGP bridge found
@@ -264,7 +264,7 @@
 sizeof(task_struct)=5960 bytes
 devtmpfs: initialized
 regulator: core version 0.5
-Time: 12:32:57  Date: 06/15/10
+Time: 13:01:13  Date: 06/15/10
 NET: Registered protocol family 16
 ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
 ACPI: bus type pci registered
@@ -283,17 +283,16 @@
 \_SB_.PCI0:_OSC invalid UUID
 _OSC request data:1 8 1f 
 ACPI: PCI Root Bridge [PCI0] (0000:00)
-pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
-pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7] (ignored)
-pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000e0000-0x000e3fff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0x000e4000-0x000e7fff] (ignored)
-pci_root PNP0A08:00: host bridge window [mem 0xd0000000-0xfeafffff] (ignored)
+pci_root PNP0A08:00: host bridge window [io  0x0000-0x0cf7]
+pci_root PNP0A08:00: host bridge window [io  0x0d00-0xffff]
+pci_root PNP0A08:00: host bridge window [mem 0x000a0000-0x000bffff]
+pci_root PNP0A08:00: host bridge window [mem 0x000d0000-0x000d3fff]
+pci_root PNP0A08:00: host bridge window [mem 0x000d4000-0x000d7fff]
+pci_root PNP0A08:00: host bridge window [mem 0x000d8000-0x000dbfff]
+pci_root PNP0A08:00: host bridge window [mem 0x000dc000-0x000dffff]
+pci_root PNP0A08:00: host bridge window [mem 0x000e0000-0x000e3fff]
+pci_root PNP0A08:00: host bridge window [mem 0x000e4000-0x000e7fff]
+pci_root PNP0A08:00: host bridge window [mem 0xd0000000-0xfeafffff]
 pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
 pci 0000:00:01.0: PME# disabled
 pci 0000:00:1a.0: reg 10: [mem 0xe8e08000-0xe8e083ff]
@@ -380,7 +379,6 @@
 \_SB_.PCI0:_OSC invalid UUID
 _OSC request data:1 19 1f 
 ACPI: PCI Root Bridge [CPBG] (0000:3f)
-pci_root PNP0A03:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
 ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
 ACPI: PCI Interrupt Link [LNKB] (IRQs 1 *3 4 5 6 7 11 12 14 15)
 ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 *4 5 6 7 10 12 14 15)
@@ -471,8 +469,16 @@
 pci 0000:00:1c.5: PCI INT B -> GSI 17 (level, low) -> IRQ 17
 pci 0000:00:1c.5: setting latency timer to 64
 pci 0000:00:1e.0: setting latency timer to 64
-pci_bus 0000:00: resource 0 [io  0x0000-0xffff]
-pci_bus 0000:00: resource 1 [mem 0x00000000-0xffffffffffffffff]
+pci_bus 0000:00: resource 0 [io  0x0000-0x0cf7]
+pci_bus 0000:00: resource 1 [io  0x0d00-0xffff]
+pci_bus 0000:00: resource 2 [mem 0x000a0000-0x000bffff]
+pci_bus 0000:00: resource 3 [mem 0x000d0000-0x000d3fff]
+pci_bus 0000:00: resource 4 [mem 0x000d4000-0x000d7fff]
+pci_bus 0000:00: resource 5 [mem 0x000d8000-0x000dbfff]
+pci_bus 0000:00: resource 6 [mem 0x000dc000-0x000dffff]
+pci_bus 0000:00: resource 7 [mem 0x000e0000-0x000e3fff]
+pci_bus 0000:00: resource 8 [mem 0x000e4000-0x000e7fff]
+pci_bus 0000:00: resource 9 [mem 0xd0000000-0xfeafffff]
 pci_bus 0000:01: resource 0 [io  0xd000-0xdfff]
 pci_bus 0000:01: resource 1 [mem 0xd0000000-0xe30fffff]
 pci_bus 0000:02: resource 0 [io  0xc000-0xcfff]
@@ -487,8 +493,16 @@
 pci_bus 0000:05: resource 0 [io  0x9000-0x9fff]
 pci_bus 0000:05: resource 1 [mem 0xe3200000-0xe51fffff]
 pci_bus 0000:05: resource 2 [mem 0xe9500000-0xe96fffff 64bit pref]
-pci_bus 0000:0d: resource 3 [io  0x0000-0xffff]
-pci_bus 0000:0d: resource 4 [mem 0x00000000-0xffffffffffffffff]
+pci_bus 0000:0d: resource 3 [io  0x0000-0x0cf7]
+pci_bus 0000:0d: resource 4 [io  0x0d00-0xffff]
+pci_bus 0000:0d: resource 5 [mem 0x000a0000-0x000bffff]
+pci_bus 0000:0d: resource 6 [mem 0x000d0000-0x000d3fff]
+pci_bus 0000:0d: resource 7 [mem 0x000d4000-0x000d7fff]
+pci_bus 0000:0d: resource 8 [mem 0x000d8000-0x000dbfff]
+pci_bus 0000:0d: resource 9 [mem 0x000dc000-0x000dffff]
+pci_bus 0000:0d: resource 10 [mem 0x000e0000-0x000e3fff]
+pci_bus 0000:0d: resource 11 [mem 0x000e4000-0x000e7fff]
+pci_bus 0000:0d: resource 12 [mem 0xd0000000-0xfeafffff]
 pci_bus 0000:3f: resource 0 [io  0x0000-0xffff]
 pci_bus 0000:3f: resource 1 [mem 0x00000000-0xffffffffffffffff]
 NET: Registered protocol family 2

Re: "ignoring host bridge windows from ACPI" in a recent laptop

[Bjorn Helgaas]

On Tuesday, June 15, 2010 05:18:23 am Bernd Petrovitsch wrote:
> Hi!
> 
> I have a Sony Vaio VPCF11M1E since early this year. Looking through the
> output of `dmesg`, I noticed
> ----  snip  ----
> pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
> ----  snip  ----
> So I tried that.
> The laptop boots and works without problems so far. I attached a diff of
> the first approx. 630 lines of the `dmesg` outputs without and with the
> above parameter. It gets pretty messy afterwards because (at least) the
> USB and/or SATA initialization runs apparently in parallel.
> 
> After finding http://lkml.org/lkml/2010/2/12/174, it seems that we might
> need another quirk to activate that automatically.
> 
> At the end, I lost also dozens of
> ----  snip  ----
> name_count maxed, losing inode data: dev=00:07, inode=
> ----  snip  ----
> lines (which are also not in the attached diff). I don't know if that
> has something to do with the above.

Until the patch you mentioned above, Linux silently ignored window
information from ACPI.  On your machine, the only effect of the
patch was to print the new line you mentioned, which was only intended
as a hint that "if PCI devices don't work correctly, here's something
we can try."

If your devices *are* working correctly, you can just ignore the hint.

You mention the "name_count maxed" messages, and I think you meant
they go away when you use "pci=use_crs".  I don't see how that would
be connected, since that's from syscall auditing code that is several
layers removed from PCI device resource management.

Bjorn

Re: "ignoring host bridge windows from ACPI" in a recent laptop

[Bernd Petrovitsch]

Hi!

On Die, 2010-06-15 at 07:27 -0600, Bjorn Helgaas wrote:
> On Tuesday, June 15, 2010 05:18:23 am Bernd Petrovitsch wrote:
[...]
> > I have a Sony Vaio VPCF11M1E since early this year. Looking through the
> > output of `dmesg`, I noticed
> > ----  snip  ----
> > pci_root PNP0A08:00: ignoring host bridge windows from ACPI; boot with "pci=use_crs" to use them
> > ----  snip  ----
> > So I tried that.
> > The laptop boots and works without problems so far. I attached a diff of
> > the first approx. 630 lines of the `dmesg` outputs without and with the
> > above parameter. It gets pretty messy afterwards because (at least) the
> > USB and/or SATA initialization runs apparently in parallel.
> > 
> > After finding http://lkml.org/lkml/2010/2/12/174, it seems that we might
> > need another quirk to activate that automatically.
> > 
> > At the end, I lost also dozens of
> > ----  snip  ----
> > name_count maxed, losing inode data: dev=00:07, inode=
> > ----  snip  ----
> > lines (which are also not in the attached diff). I don't know if that
> > has something to do with the above.
> 
> Until the patch you mentioned above, Linux silently ignored window
> information from ACPI.  On your machine, the only effect of the
> patch was to print the new line you mentioned, which was only intended
> as a hint that "if PCI devices don't work correctly, here's something
> we can try."
> 
> If your devices *are* working correctly, you can just ignore the hint.

OK.
The not really correctly working device (so far) is the graphics card
---- snip  ----
01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2)
---- snip  ---- 
as I get only some standard VESA resolution (800x600 or so - but there
is a full-hd-screen on it) with X.
I'm in the process of playing around with that ("nv vs nouveau driver"
or "is it a system-config-display issue") and writing something in the
Fedora-12 bugzilla eventually - if only to see where the real problem
lies.

> You mention the "name_count maxed" messages, and I think you meant
> they go away when you use "pci=use_crs".  I don't see how that would

ACK.

> be connected, since that's from syscall auditing code that is several
> layers removed from PCI device resource management.

I (also) thought similar - I also just googled for the line (and didn't
find anything useful, probably not enough googled) and just wondered why
it was gone.
So I take is as "not related".

Thanks for the quick answer BTW,
	Bernd
-- 
mobile: +43 664 4416156              http://www.sysprog.at/
    Linux Software Development, Consulting and Services

Re: "ignoring host bridge windows from ACPI" in a recent laptop

[Bjorn Helgaas]

On Tuesday, June 15, 2010 07:45:13 am Bernd Petrovitsch wrote:
> The not really correctly working device (so far) is the graphics card
> ---- snip  ----
> 01:00.0 VGA compatible controller: nVidia Corporation GT216 [GeForce GT 330M] (rev a2)
> ---- snip  ---- 
> as I get only some standard VESA resolution (800x600 or so - but there
> is a full-hd-screen on it) with X.
> I'm in the process of playing around with that ("nv vs nouveau driver"
> or "is it a system-config-display issue") and writing something in the
> Fedora-12 bugzilla eventually - if only to see where the real problem
> lies.

If the behavior changes with "pci=use_crs", let me know because I
should look into that more.  If "pci=use_crs" doesn't make any
difference with this issue, then it's probably a config or driver
issue that's beyond my knowledge.

Bjorn