From owner-freebsd-current@FreeBSD.ORG Mon Mar 9 22:26:13 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6A2710656DB; Mon, 9 Mar 2009 22:26:13 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-bw0-f164.google.com (mail-bw0-f164.google.com [209.85.218.164]) by mx1.freebsd.org (Postfix) with ESMTP id CDAA28FC28; Mon, 9 Mar 2009 22:26:12 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: by bwz8 with SMTP id 8so1297168bwz.43 for ; Mon, 09 Mar 2009 15:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=OBkwun3mVuEpGv7SgdWr0f33AKwgjbH2jWxzSbWSKqs=; b=AJMCFFibUuOiH5QEyRZTCU4H4YGne3PEmjOIufM8Ibbnej/Nz+mO0//7jcfETjjYLh xTPtkfTxTlVa2Up0fGy6LVpzypbXJDvfhb1RxCQfqTz/R+SbrSoCG15TJ0a0SKE+bfDW kCYXcHe3q5tHmv/xrzfVUH3XIW9jMlnLp9Pc0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=JSDgsrU83EGuVxQTF1rsiRQCZ4qBG+CUBJhV6+Ushyi0EYOumeaM9EI0XzzA8YtlWq xE9hH8+WDytBFfCuT102TuKAI2sySwR3mTKk6Xxvv7lWXrm9xkJBmXcK7u84Z9C6cVPa 5kb7VtjBYHo5rL6jVwNySPTMs0VKVdEIxK3o0= MIME-Version: 1.0 Received: by 10.86.60.14 with SMTP id i14mr4425881fga.69.1236637571431; Mon, 09 Mar 2009 15:26:11 -0700 (PDT) In-Reply-To: <49B594B5.2060706@FreeBSD.org> References: <49B58CF6.7070104@FreeBSD.org> <49B594B5.2060706@FreeBSD.org> Date: Tue, 10 Mar 2009 01:26:11 +0300 Message-ID: From: pluknet To: Alexander Motin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD-Current Subject: Re: Unable to set devclass (devname: (null) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Mar 2009 22:26:14 -0000 2009/3/10 Alexander Motin : > pluknet wrote: >> >> 2009/3/10 Alexander Motin : >>> >>> 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