edd_id and floppy devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

(Sent this to the wrong list the first time around.  Let's try again.)

After upgrading to udev-124, my kernel started logging errors on each
boot (and in fact whenever "udevadm trigger" got run).  The errors were
as follows:

end_request: I/O error, dev fd0, sector 0

Based on the "dev fd0" part, I figured the issue was some rule that was
running on the fd0 device; I eventually tracked it down to edd_id.  (I
suspect I was getting errors because the drive had no media, but that's
probably the default state for most floppy drives most of the time
anyway.)  Adding the following rule to 61-persistent-storage-edd.rules
(as the second rule) makes the kernel errors stop:

KERNEL=="fd*", GOTO="persistent_storage_edd_end"

I am assuming that floppy disks can't possibly store an EDD signature
(and so there would be no problems disabling edd_id for fd* devices),
but I don't know that for sure.  Is this change safe for the rules
distributed with udev?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIdrjnS5vET1Wea5wRA5r+AJ4p9fXM++BYGAxanXMYOKNSL7KL9wCgm3Bn
+gCr9XQFvXA9rDGOTo22Yg0=
=O+Fq
-----END PGP SIGNATURE-----
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux