Date: Tue, 16 Aug 2011 19:26:11 +0300 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@FreeBSD.org>, David Somayajulu <david.somayajulu@qlogic.com> Subject: Re: Loading drivers via kldload Message-ID: <4E4A9A23.7060807@FreeBSD.org> In-Reply-To: <201108161145.02733.jhb@freebsd.org> References: <75E1A2A7D185F841A975979B0906BBA67BCC877062@AVEXMB1.qlogic.org> <75E1A2A7D185F841A975979B0906BBA67BCC877180@AVEXMB1.qlogic.org> <4E4919DA.5000706@FreeBSD.org> <201108161145.02733.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E4A9A23.7060807>