From owner-freebsd-current@FreeBSD.ORG Sun Mar 22 03:19:26 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 21740106566C; Sun, 22 Mar 2009 03:19:26 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (bsdimp.com [199.45.160.85]) by mx1.freebsd.org (Postfix) with ESMTP id D59468FC08; Sun, 22 Mar 2009 03:19:25 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.14.2/8.14.1) with ESMTP id n2M3GJtW029801; Sat, 21 Mar 2009 21:16:19 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sat, 21 Mar 2009 21:16:54 -0600 (MDT) Message-Id: <20090321.211654.1102538138.imp@bsdimp.com> To: pluknet@gmail.com From: "M. Warner Losh" In-Reply-To: References: <49B58CF6.7070104@FreeBSD.org> X-Mailer: Mew version 5.2 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: mav@freebsd.org, freebsd-current@freebsd.org 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: Sun, 22 Mar 2009 03:19:26 -0000 In message: pluknet writes: : 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). Looks like something to do with atakbd or psm. What does your hints file look like? Warner