Date: Thu, 15 Apr 2004 14:13:33 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: mikej@rogers.com Cc: freebsd-current@freebsd.org Subject: Re: Is a BAD BAR something to worry about? Message-ID: <20040415.141333.67561583.imp@bsdimp.com> In-Reply-To: <20040415.140738.42906545.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>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20040415.140738.42906545.imp@bsdimp.com>
"M. Warner Losh" <imp@bsdimp.com> writes:
: In message: <63887.66.11.183.182.1082059063.squirrel@69.193.41.47>
: "Mike Jakubik" <mikej@rogers.com> writes:
: : 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.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040415.141333.67561583.imp>