From owner-freebsd-current@FreeBSD.ORG Mon Mar 9 21:41:14 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 C88EF1065670 for ; Mon, 9 Mar 2009 21:41:14 +0000 (UTC) (envelope-from mav@FreeBSD.org) Received: from cmail.optima.ua (cmail.optima.ua [195.248.191.121]) by mx1.freebsd.org (Postfix) with ESMTP id 4C7488FC08 for ; Mon, 9 Mar 2009 21:41:13 +0000 (UTC) (envelope-from mav@FreeBSD.org) X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona-2.1.0 Received: from [212.86.226.226] (account mav@alkar.net HELO mavbook.mavhome.dp.ua) by cmail.optima.ua (CommuniGate Pro SMTP 5.2.9) with ESMTPSA id 236977745; Mon, 09 Mar 2009 23:41:13 +0200 Message-ID: <49B58CF6.7070104@FreeBSD.org> Date: Mon, 09 Mar 2009 23:41:10 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.19 (X11/20090118) MIME-Version: 1.0 To: pluknet References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed 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 21:41:15 -0000 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? -- Alexander Motin