From owner-freebsd-current@FreeBSD.ORG Tue Aug 16 16:26:16 2011 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 5C888106564A; Tue, 16 Aug 2011 16:26:16 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 75A188FC0C; Tue, 16 Aug 2011 16:26:14 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA07463; Tue, 16 Aug 2011 19:26:12 +0300 (EEST) (envelope-from avg@FreeBSD.org) Message-ID: <4E4A9A23.7060807@FreeBSD.org> Date: Tue, 16 Aug 2011 19:26:11 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:5.0) Gecko/20110705 Thunderbird/5.0 MIME-Version: 1.0 To: John Baldwin References: <75E1A2A7D185F841A975979B0906BBA67BCC877062@AVEXMB1.qlogic.org> <75E1A2A7D185F841A975979B0906BBA67BCC877180@AVEXMB1.qlogic.org> <4E4919DA.5000706@FreeBSD.org> <201108161145.02733.jhb@freebsd.org> In-Reply-To: <201108161145.02733.jhb@freebsd.org> X-Enigmail-Version: 1.2pre Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: "freebsd-current@freebsd.org" , David Somayajulu Subject: Re: Loading drivers via kldload 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, 16 Aug 2011 16:26:16 -0000 The following are pure speculations, I'd rather let David speak, but just in case; on 16/08/2011 18:45 John Baldwin said the following: > Well, that would seem odd, still. It only returns BUS_PROBE_GENERIC (not 0), so > David's driver's probe routine should still be called to get a chance to attach to > the device. Maybe it doesn't do that exactly because device and vendor ID are zeroes as David described earlier. > Also, the ATA driver only allocates its BAR once, so it shouldn't > trigger the panic in question in that case (the panic is only triggered when you > try to double-allocate a BAR). This makes only if the BAR has sane values. Not sure what happens if the BAR has some junk that duplicates other PCI device, or something like that. -- Andriy Gapon