Date: Thu, 11 Feb 2016 11:43:02 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org>, Scott Long <scott4long@yahoo.com> Cc: scsi@FreeBSD.org, Sreekanth Reddy <sreekanth.reddy@broadcom.com>, ken@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Panic on reloading a driver with same DEVICE_PROBE() return value Message-ID: <56BC57A6.7090205@FreeBSD.org> In-Reply-To: <1675870.rYHsh4pVC7@ralph.baldwin.cx> References: <CAK=zhgoGwXSsD-mNF=jGov1FJFnpM7m_fZ0Jwsq4JR5yazB%2Bww@mail.gmail.com> <2227929.z5Tr1XC1Xs@ralph.baldwin.cx> <0C31DEA0-0AD0-4E1B-9656-C6ABB6AA854A@yahoo.com> <1675870.rYHsh4pVC7@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/02/2016 01:02, John Baldwin wrote: > I'm actually not certain of what triggered the fault. The check that emits > the printf should also be failing the kldload with EEXIST (but that doesn't > work for the case where both are compiled into the kernel). The new driver > should have just never been registered, but then I'm not sure how its method > could be called at all. The only reference to the driver's methods are in the > struct driver which also has the associated softc size (so you shouldn't get > a mismatch between softc size and the driver methods used). I haven't really followed this thread and my memory about my own problem has significantly faded, but could the issue #2 in the following post be related? http://thread.gmane.org/gmane.os.freebsd.current/147256 Sorry for the noise if it's totally unrelated. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56BC57A6.7090205>