https://bugzilla.kernel.org/show_bug.cgi?id=220491 --- Comment #36 from Paul Ausbeck (paula@xxxxxxxxxxxxxxxxxxx) --- Oops, my just posted usbmon trace does contain urbs that I would interpret as talking to the associated hub, for some reason I just missed them on initial read. This is good as I was expecting hub destined urbs. But the idea that the device ID does not change is still like I initially interpreted. In the just posted trace I only see two addresses: Bi/Bo:3:001 and Bi/Bo:3:002. In a trace with a disconnect/reconnect there would be three addresses, always Bi/Bo:3:001, but two device addresses, say Bi/Bo:3:002 initially and then Bi/Bo:3:003. Depending upon how many times the disconnect/reconnect has occurred since boot the device numbers may be larger but always sequential. I've looked again at the trace from comment #9 and there are two device addresses. Curiously, device 4, presumably newer, appears before device 3, presumably older, then comes back again. I don't know what actually happened. Perhaps I traced the wrong host controller, but perhaps not. There is a second xhci host controller that I might have traced, and it does encompass two uvcvideo devices, but according to lsusb both of these devices have the same device ID and differ only in interface number. Since there is only one camera, the two interfaces must be an artifact of the physical device implementation. Anyway, I wouldn't put too much stock into the trace from comment #9. If you can make sense of it in light of what I've just told you, please do so. Oh, after reviewing my comment #10 I remember that on that run I mistakenly had a USB uas device plugged into the same host controller as the SD card reader. >From the amount of trace information for each, I would guess that device 003 is the uas SSD and device 004 is the SD card reader. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
