Date: Tue, 10 Mar 2009 20:54:39 +0900 (JST) From: "M. Warner Losh" <imp@bsdimp.com> To: pluknet@gmail.com Cc: freebsd-current@FreeBSD.org Subject: Re: Unable to set devclass (devname: (null) Message-ID: <20090310.205439.-1525215866.imp@bsdimp.com> In-Reply-To: <a31046fc0903091420j359cfd77v17c651bb997fb55c@mail.gmail.com> References: <a31046fc0903091420j359cfd77v17c651bb997fb55c@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <a31046fc0903091420j359cfd77v17c651bb997fb55c@mail.gmail.com>
pluknet <pluknet@gmail.com> writes:
: Hi.
:
: Is it ok (and how much harmfull) to see this message?
:
: driver bug: Unable to set devclass (devname: (null))
:
: P.S.
: This is introduced in subr_bus.c, v1.216
: - PDEBUG(("Unable to set device class"));
: + printf("driver bug: Unable to set devclass (devname: %s)\n",
: + (child ? device_get_name(child) :
: + "no device"));
:
: where PDEBUG was moved from BUS_DEBUG to general output.
I would say generally no. when do you see it?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090310.205439.-1525215866.imp>