From owner-freebsd-current@FreeBSD.ORG Thu Sep 24 14:24:33 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 ADC85106566B; Thu, 24 Sep 2009 14:24:33 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7B8738FC29; Thu, 24 Sep 2009 14:24:33 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 01E7046B09; Thu, 24 Sep 2009 10:24:33 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 289F28A01B; Thu, 24 Sep 2009 10:24:32 -0400 (EDT) From: John Baldwin To: Alexander Motin Date: Thu, 24 Sep 2009 08:36:40 -0400 User-Agent: KMail/1.9.7 References: <20090923055647.GA2183@a91-153-125-115.elisa-laajakaista.fi> <20090924060805.GA2057@a91-153-125-115.elisa-laajakaista.fi> <4ABB3DA6.5090004@FreeBSD.org> In-Reply-To: <4ABB3DA6.5090004@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200909240836.41775.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 24 Sep 2009 10:24:32 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: FreeBSD-Current , Peter Holm , scottl@freebsd.org, Andriy Gapon , Jaakko Heinonen , Thomas Quinot , Kostik Belousov Subject: Re: Fwd: core dump on kldload atapicam 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: Thu, 24 Sep 2009 14:24:33 -0000 On Thursday 24 September 2009 5:36:38 am Alexander Motin wrote: > Jaakko Heinonen wrote: > > On 2009-09-23, Alexander Motin wrote: > >> Then please explain me how it happens. I don't think that explanation > >> "it just works" sufficient. > >> > >> Any ideas what needed to reproduce that? Because it looks like not going > >> to fall in my case: > > > > It happens if a parent ata device is not attached. I can reproduce the > > problem on system which hash ata0, ata2 and ata3 devices but ata1 fails > > to probe. > > Nice catch. I think it is newbus problem, not ata. I am able to simulate > this problem locally and attached patch fixes it. Any objections? I think this is ok. Possibly ask Warner (imp@) as well to make sure. -- John Baldwin