Unable to set devclass (devname: (null)
M. Warner Losh
imp at bsdimp.com
Sat Mar 21 20:19:26 PDT 2009
In message: <a31046fc0903091504h24626240p3bb46401fedb37a at mail.gmail.com>
pluknet <pluknet at gmail.com> writes:
: 2009/3/10 Alexander Motin <mav at 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?
More information about the freebsd-current