Date: Sat, 21 Mar 2009 21:16:54 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: pluknet@gmail.com Cc: mav@freebsd.org, freebsd-current@freebsd.org Subject: Re: Unable to set devclass (devname: (null) Message-ID: <20090321.211654.1102538138.imp@bsdimp.com> In-Reply-To: <a31046fc0903091504h24626240p3bb46401fedb37a@mail.gmail.com> References: <gp418i$kc8$1@FreeBSD.cs.nctu.edu.tw> <49B58CF6.7070104@FreeBSD.org> <a31046fc0903091504h24626240p3bb46401fedb37a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <a31046fc0903091504h24626240p3bb46401fedb37a@mail.gmail.com>
pluknet <pluknet@gmail.com> writes:
: 2009/3/10 Alexander Motin <mav@freebsd.org>:
: > pluknet wrote:
: >>
: >> 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.
: >
: > Actually this check was introduced in rev. 1.214, just was not logged.
: > Before this change system could crash soon after this message. Now it should
: > not, but related device probably will not work properly. It is probably not
: > good and should be fixed, but it can be just a low memory symptom. It was
: > noticed for ata driver, but I hope it was fixed. Where have you get it?
:
: This is during the boot, see dmesg (attached).
Looks like something to do with atakbd or psm. What does your hints
file look like?
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090321.211654.1102538138.imp>