Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 22 Mar 2009 13:14:52 +0300
From:      pluknet <pluknet@gmail.com>
To:        "M. Warner Losh" <imp@bsdimp.com>
Cc:        mav@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: Unable to set devclass (devname: (null)
Message-ID:  <a31046fc0903220314h520688fqf94f9d89863d434b@mail.gmail.com>
In-Reply-To: <20090321.211654.1102538138.imp@bsdimp.com>
References:  <gp418i$kc8$1@FreeBSD.cs.nctu.edu.tw> <49B58CF6.7070104@FreeBSD.org> <a31046fc0903091504h24626240p3bb46401fedb37a@mail.gmail.com> <20090321.211654.1102538138.imp@bsdimp.com>

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
2009/3/22 M. Warner Losh <imp@bsdimp.com>:
> 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?

Pretty standard (see attach).


-- 
wbr,
pluknet

[-- Attachment #2 --]
# $FreeBSD: src/sys/i386/conf/GENERIC.hints,v 1.21 2008/07/13 07:20:14 ed Exp $
hint.fdc.0.at="isa"
hint.fdc.0.port="0x3F0"
hint.fdc.0.irq="6"
hint.fdc.0.drq="2"
hint.fd.0.at="fdc0"
hint.fd.0.drive="0"
hint.fd.1.at="fdc0"
hint.fd.1.drive="1"
hint.ata.0.at="isa"
hint.ata.0.port="0x1F0"
hint.ata.0.irq="14"
hint.ata.1.at="isa"
hint.ata.1.port="0x170"
hint.ata.1.irq="15"
hint.adv.0.at="isa"
hint.adv.0.disabled="1"
hint.bt.0.at="isa"
hint.bt.0.disabled="1"
hint.aha.0.at="isa"
hint.aha.0.disabled="1"
hint.aic.0.at="isa"
hint.aic.0.disabled="1"
hint.atkbdc.0.at="isa"
hint.atkbdc.0.port="0x060"
hint.atkbd.0.at="atkbdc"
hint.atkbd.0.irq="1"
hint.psm.0.at="atkbdc"
hint.psm.0.irq="12"
hint.vga.0.at="isa"
hint.sc.0.at="isa"
hint.sc.0.flags="0x100"
hint.apm.0.disabled="1"
hint.apm.0.flags="0x20"
hint.uart.0.at="isa"
hint.uart.0.port="0x3F8"
hint.uart.0.flags="0x10"
hint.uart.0.irq="4"
hint.uart.1.at="isa"
hint.uart.1.port="0x2F8"
hint.uart.1.irq="3"
hint.uart.2.at="isa"
hint.uart.2.disabled="1"
hint.uart.2.port="0x3E8"
hint.uart.2.irq="5"
hint.uart.3.at="isa"
hint.uart.3.disabled="1"
hint.uart.3.port="0x2E8"
hint.uart.3.irq="9"
hint.ppc.0.at="isa"
hint.ppc.0.irq="7"
hint.ed.0.at="isa"
hint.ed.0.disabled="1"
hint.ed.0.port="0x280"
hint.ed.0.irq="10"
hint.ed.0.maddr="0xd8000"
hint.cs.0.at="isa"
hint.cs.0.disabled="1"
hint.cs.0.port="0x300"
hint.sn.0.at="isa"
hint.sn.0.disabled="1"
hint.sn.0.port="0x300"
hint.sn.0.irq="10"
hint.ie.0.at="isa"
hint.ie.0.disabled="1"
hint.ie.0.port="0x300"
hint.ie.0.irq="10"
hint.ie.0.maddr="0xd0000"
hint.fe.0.at="isa"
hint.fe.0.disabled="1"
hint.fe.0.port="0x300"
hint.le.0.at="isa"
hint.le.0.disabled="1"
hint.le.0.port="0x280"
hint.le.0.irq="10"
hint.le.0.drq="0"
hint.atrtc.0.at="isa"
hint.atrtc.0.port="0x70"
hint.atrtc.0.irq="8"

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a31046fc0903220314h520688fqf94f9d89863d434b>