Some updates after more debugging. The original rule was
SUBSYSTEM=="scsi", ENV{DEVTYPE}=="scsi_device", TEST!="[module/sg]", \
RUN+="/sbin/modprobe -b sg"
and was added to fix [1].
Apparently this didn't cause any issues so far.
This was then modified to use the "kmod load" builtin in 204-11.
This is a new facility which is much faster. So this changed the timing
when loading the module.
We suspect, that loading sg *before* the SCSI subsystem has finished
doing the probing and detection and is what's causing the sd_mod to not
be loaded.
Reverting back to modprobe would be a possible workaround, as this would
change back the timing to the old behaviour.
We still would have a race, though, but apparently more unlikely to
cause any issues.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657948
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
