https://bugzilla.kernel.org/show_bug.cgi?id=220491 --- Comment #37 from Alan Stern (stern@xxxxxxxxxxxxxxxxxxx) --- The usbmon trace in comment #35 does contain a disconnect/reconnect. And it did propagate up to the usbcore level, which is where the usb-persist mechanism lives. usb-persist is what keeps it from going any farther, in particular, from showing up in the dmesg log. In case you're curious, in that trace: ffff9bb60d581f00 127168165 S Ci:3:001:0 s a3 00 0000 0004 0004 4 < ffff9bb60d581f00 127168171 C Ci:3:001:0 0 4 = 03020100 ffff9bb60d581f00 127168174 S Co:3:001:0 s 23 01 0010 0004 0000 0 ffff9bb60d581f00 127168181 C Co:3:001:0 0 0 The first two lines are Get-Port-Status for port 4 (the port the card reader is plugged into) near the start of the resume, with the returned status showing a connect-change. The next two lines are a command to clear the port's connect-change status bit. The fact that these lines are present is proof that usbcore was aware of the disconnection, because usbcore is the component that ordered the status bit to be cleared. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
