Comment 97 for bug 925760

Revision history for this message
In , Petr (petr-redhat-bugs) wrote :

The kernel messages correlate with following kernel/udev events:

KERNEL[684.511147] change /devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
ACTION=change
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb
DEVTYPE=disk
DISK_MEDIA_CHANGE=1
MAJOR=8
MINOR=16
SEQNUM=725
SUBSYSTEM=block

UDEV [684.602048] change /devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
ACTION=change
DEVLINKS=/dev/disk/by-id/usb-Generic-_Multi-Card_20071114173400000-0:0 /dev/disk/by-path/pci-0000:00:0e.5-usb-0:1:1.0-scsi-0:0:0:0
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb
DEVTYPE=disk
DISK_MEDIA_CHANGE=1
ID_BUS=usb
ID_INSTANCE=0:0
ID_MODEL=Multi-Card
ID_MODEL_ENC=Multi-Card\x20\x20\x20\x20\x20\x20
ID_MODEL_ID=0158
ID_PATH=pci-0000:00:0e.5-usb-0:1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_0e_5-usb-0_1_1_0-scsi-0_0_0_0
ID_REVISION=1.00
ID_SERIAL=Generic-_Multi-Card_20071114173400000-0:0
ID_SERIAL_SHORT=20071114173400000
ID_TYPE=disk
ID_USB_DRIVER=ums-realtek
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Generic-
ID_VENDOR_ENC=Generic-
ID_VENDOR_ID=0bda
MAJOR=8
MINOR=16
SEQNUM=725
SUBSYSTEM=block
USEC_INITIALIZED=10909217

KERNEL[687.073016] change /devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
ACTION=change
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb
DEVTYPE=disk
DISK_MEDIA_CHANGE=1
MAJOR=8
MINOR=16
SEQNUM=726
SUBSYSTEM=block

UDEV [687.089178] change /devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb (block)
ACTION=change
DEVLINKS=/dev/disk/by-id/usb-Generic-_Multi-Card_20071114173400000-0:0 /dev/disk/by-path/pci-0000:00:0e.5-usb-0:1:1.0-scsi-0:0:0:0
DEVNAME=/dev/sdb
DEVPATH=/devices/pci0000:00/0000:00:0e.5/usb4/4-1/4-1:1.0/host2/target2:0:0/2:0:0:0/block/sdb
DEVTYPE=disk
DISK_MEDIA_CHANGE=1
ID_BUS=usb
ID_INSTANCE=0:0
ID_MODEL=Multi-Card
ID_MODEL_ENC=Multi-Card\x20\x20\x20\x20\x20\x20
ID_MODEL_ID=0158
ID_PATH=pci-0000:00:0e.5-usb-0:1:1.0-scsi-0:0:0:0
ID_PATH_TAG=pci-0000_00_0e_5-usb-0_1_1_0-scsi-0_0_0_0
ID_REVISION=1.00
ID_SERIAL=Generic-_Multi-Card_20071114173400000-0:0
ID_SERIAL_SHORT=20071114173400000
ID_TYPE=disk
ID_USB_DRIVER=ums-realtek
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Generic-
ID_VENDOR_ENC=Generic-
ID_VENDOR_ID=0bda
MAJOR=8
MINOR=16
SEQNUM=726
SUBSYSTEM=block
USEC_INITIALIZED=10909217

Both media-change events generated by kernel appears during one cycle.

Once I need to use the reader, I found kernel does not signal insertion of a medium, I had to manually rescan partion table with blockdev --rereadpt. These spurious periodic media events could be a work-around implemented in kernel for the special hardware.