On Fri, 5 May 2017, Andreas Hartmann wrote: > > Ah, I see. The card reader disconnects itself from the USB bus when > > there is no card inserted. This means you shouldn't even need to write > > to /sys/block/sdb/device/delete; after unmounting all you have to do is > > remove the card. Then the device manager should see that it is gone. > > I tested this situation with the driver from 4.4.x, too, with two Did you apply my patches to the 4.4.x driver? If not, can you try doing the same thing with the patches installed? > different SD cards. One of the sdcard has a fat FS, the other one reiserfs. > > The card with the fat fs didn't show any USB traffic while clicking on remove. > The GUI just stated, that the SD card could be removed now. > > The card with the reiserfs did show some USB traffic during unmount > (most probably closing the FS). This part can be seen in the attached trace. > > But it doesn't contain any rescan. And therefore, the behavior, which can > be seen in the GUI device manager, is completely normal as expected. Does this mean you suspect my patches are somehow responsible for the rescans? > I attached a trace containing the same action with the unchanged > driver from 4.4.x By "unchanged" you mean with no patches, right? > Packages 1-92: Initialization of USB trace > Packages 93-284: Clicking on remove device (device was mounted before): > May 05 15:11:56 notebook2 udisksd[1795]: Cleaning up mount point /run/media/andreas/59c9a0c1-30c7-4be9-b739-73187d586e08 (device 8:17 is not mounted) > May 05 15:11:57 notebook2 udisksd[1795]: Unmounted /dev/sdb1 on behalf of uid 1000 > > Packages 285-332: > May 05 15:12:17 notebook2 kernel: usb 1-1.1: USB disconnect, device number 8 > > > => There can't be seen any rescan. True. But the rescans could be caused by some other change to the kernel between 4.4 and 4.10. The way to find out is to try various kernels with the patches applied to the driver. Incidentally, do you have any idea why your usbmon capture includes duplicates of every packet starting from 93? (This has happened in your previous captures also.) And why some of the packets are listed out of order (see the timestamps on packets 23, 25, 27, 29, and others)? It looks very odd. You might want to try using the text interface described in Documentation/usb/usbmon.txt instead of wireshark. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
