From owner-freebsd-current@FreeBSD.ORG Tue Nov 9 18:14:53 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB13A1065674; Tue, 9 Nov 2010 18:14:52 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 8AE898FC18; Tue, 9 Nov 2010 18:14:52 +0000 (UTC) Received: by yxf34 with SMTP id 34so116375yxf.13 for ; Tue, 09 Nov 2010 10:14:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=aIEBIX+J5I2X/qKgklk8miz5HGAJTbl7IFB8KPS8jK4=; b=GLAPK1a3RfoshbGL2j06xl4U2C2oscbzEKNu5SPB7yuYEJ0wg8KYMxUmv2Dq/Qd4wC DJp+WeDIHAt0AhpBWNN3WUK0/g/BPE6rPgjECygRE+eHu9ROzuIT6Op+q1408DNVbfFC LMnhfYO2y0AOcJf6Yhhf7DerYCqQxommzuyj8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=nH7dSODcmV6GOvGkM0iOuZyd1XMd9Zj+vtF+j+15EogssYCoETxgIIPZBVHAlNOL6Q mSonTXvShVTFYHH3g/D+ZW7LeSzasF1r4JE9qz0Vr9+XwKAEotJFqqHv409muDrID+2f MWh21IovFa2rCgbp79RMmmJD2FPpEVNGo04ew= Received: by 10.204.68.142 with SMTP id v14mr6646251bki.106.1289326490998; Tue, 09 Nov 2010 10:14:50 -0800 (PST) Received: from mavbook2.mavhome.dp.ua (pc.mavhome.dp.ua [212.86.226.226]) by mx.google.com with ESMTPS id t10sm1235771bkj.16.2010.11.09.10.14.48 (version=SSLv3 cipher=RC4-MD5); Tue, 09 Nov 2010 10:14:49 -0800 (PST) Sender: Alexander Motin Message-ID: <4CD98F84.10907@FreeBSD.org> Date: Tue, 09 Nov 2010 20:14:28 +0200 From: Alexander Motin User-Agent: Thunderbird 2.0.0.23 (X11/20091212) MIME-Version: 1.0 To: Andriy Gapon References: <4CD97F04.6010009@FreeBSD.org> <4CD98130.6020705@freebsd.org> In-Reply-To: <4CD98130.6020705@freebsd.org> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: current Subject: Re: ATA: driver bug: Unable to set devclass 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: Tue, 09 Nov 2010 18:14:53 -0000 Andriy Gapon wrote: > on 09/11/2010 19:04 Alexander Motin said the following: >> Andriy Gapon wrote: >>> Since one of the recent updates (not sure which revision though) I started to get >>> "Unable to set devclass" messages in boot dmesg. I'd say that I see the message >>> every other boot, i.e. not always. >>> >>> I added some more debug code there and here's a tack trace: >>> >>> driver bug: Unable to set devclass (child = 0xffffff00070d0100, devname: (null)) >>> #0 0xffffffff803ae127 at device_probe_child+0x127 >>> #1 0xffffffff803ae40c at device_probe+0x7c >>> #2 0xffffffff803ae4a1 at device_probe_and_attach+0x11 >>> #3 0xffffffff803ae56a at bus_generic_attach+0x1a >>> #4 0xffffffff801df93c at ata_identify+0x2ec >>> #5 0xffffffff801dfcdb at ata_boot_attach+0x6b >>> #6 0xffffffff803a8577 at run_interrupt_driven_config_hooks+0xf7 >>> #7 0xffffffff803a8993 at boot_run_interrupt_driven_config_hooks+0x23 >>> #8 0xffffffff8032f227 at mi_startup+0xc7 >>> #9 0xffffffff801719cc at btext+0x2c >>> >>> >From kgdb: >>> (kgdb) p *(device_t)0xffffff00070d0100 >>> $1 = {ops = 0xffffff0001b07000, link = {tqe_next = 0xffffff0001a65100, tqe_prev = >>> 0xffffff0006eb0130}, devlink = {tqe_next = 0xffffff0001a65100, tqe_prev = >>> 0xffffff000706e318}, >>> parent = 0xffffff0006eb0100, children = {tqh_first = 0xffffff0001a5b200, >>> tqh_last = 0xffffff0001a5b208}, driver = 0xffffffff8079bc80, devclass = >>> 0xffffff0001add080, unit = 0, >>> nameunit = 0xffffff00070931a0 "ad0", desc = 0xffffff000711e7c0 >>> "ST3320620A/3.AAF", busy = 0, state = DS_ATTACHED, devflags = 0, flags = 89, order >>> = 0, ivars = 0xffffff000711e5e0, >>> softc = 0xffffff000706a400, sysctl_ctx = {tqh_first = 0xffffff000711e600, >>> tqh_last = 0xffffff000711e708}, sysctl_tree = 0xffffff00070f9500} >>> >>> Apparently sometimes something happens too soon? :-) >> What controller is there? Any other differences/interesting things in >> verbose dmesg? Any new "CONNECT requested" messages or anything else? > > It's SB700 integrated controller (ATI IXP700/800 UDMA133 controller). > This happens during boot, there are no other unusual ata-related messages. > I have device ahci in kernel, but no ATA_CAM option, so PATA stuff works via > "pure" ata code. Hmm. There was not much changes in ATA last time and I can't expect what of them could affect PATA. Probe code wasn't changed for long time. This check was actually added after some ata(4) bug found two years ago. So I am not sure your problem is something new. May be something else just triggered it again. -- Alexander Motin