Panic on reloading a driver with same DEVICE_PROBE() return value
Andriy Gapon
avg at FreeBSD.org
Thu Feb 11 09:44:05 UTC 2016
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
More information about the freebsd-scsi
mailing list