Is a BAD BAR something to worry about?

[Mike Jakubik]

M. Warner Losh said:

> : : > In message: <20040414171146.GF64506 at arved.at>
> : : >             Tilman Linneweh <tilman at arved.at> writes:
> : : > : atapci2: BAD BAR: skipping checks
> : : >
> : : > These are fine.
> : : >
> : : > Warner
> : :
> : : Well, they are kind of annoying. Is this temporary debugging stuff, or
> : : will this be permanent?
> :
> : Read the code:
> :
> : 		/* if (bootverbose) */
> : 		device_printf(child, "BAD BAR: skipping checks\n");
>
> eg, I plan on making it bootverbose fodder.

I see. Any ideas why my fdc stopped working and acpi reports a number of
errors? It used to work fine before.

What is all of this?

---
pci0: <serial bus, USB> at device 4.2 (no driver attached)
pci0:4:2: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
pci0: <serial bus, USB> at device 4.3 (no driver attached)
pci0:4:3: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
pci0: <bridge, PCI-unknown> at device 4.4 (no driver attached)
pci0:4:4: Transition from D0 to D3
pci0: Failed to set ACPI power state D3 on (null): AE_BAD_PARAMETER
...
fdc0: cannot reserve I/O port range (1 ports)
---