Date: Thu, 24 Sep 2009 08:36:40 -0400 From: John Baldwin <jhb@freebsd.org> To: Alexander Motin <mav@freebsd.org> Cc: FreeBSD-Current <freebsd-current@freebsd.org>, Peter Holm <pho@freebsd.org>, scottl@freebsd.org, Andriy Gapon <avg@freebsd.org>, Jaakko Heinonen <jh@saunalahti.fi>, Thomas Quinot <thomas@freebsd.org>, Kostik Belousov <kostikbel@gmail.com> Subject: Re: Fwd: core dump on kldload atapicam Message-ID: <200909240836.41775.jhb@freebsd.org> In-Reply-To: <4ABB3DA6.5090004@FreeBSD.org> References: <20090923055647.GA2183@a91-153-125-115.elisa-laajakaista.fi> <20090924060805.GA2057@a91-153-125-115.elisa-laajakaista.fi> <4ABB3DA6.5090004@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909240836.41775.jhb>