Date: Thu, 15 Apr 2004 22:56:29 -0400 (EDT) From: "Mike Jakubik" <mikej@rogers.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-current@freebsd.org Subject: Re: Is a BAD BAR something to worry about? Message-ID: <1073.192.168.0.200.1082084189.squirrel@192.168.0.1> In-Reply-To: <20040415.141333.67561583.imp@bsdimp.com> References: <20040415.092434.22229494.imp@bsdimp.com><63887.66.11.183.182.1082059063.squirrel@69.193.41.47><20040415.140738.42906545.imp@bsdimp.com> <20040415.141333.67561583.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh said: > : : > In message: <20040414171146.GF64506@arved.at> > : : > Tilman Linneweh <tilman@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) ---
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1073.192.168.0.200.1082084189.squirrel>