2009/3/10 Alexander Motin <mav@freebsd.org>:
quoted text
> pluknet wrote:
>>
>> 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).
>
> It does not gives much info. Can you try to add dl->driver->name,
> device_get_unit(child) and device_set_devclass() result printing there?
>

That gives:
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
driver bug: Unable to set devclass (devname: (null))
dl->driver->name: atkbdc
device_get_unit(child): -1
device_set_devclass(): 17


-- 
wbr,
pluknet
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"