https://bugzilla.kernel.org/show_bug.cgi?id=220491 --- Comment #19 from Paul Ausbeck (paula@xxxxxxxxxxxxxxxxxxx) --- I have a couple of AAEON emb-qm77 Intel ivy bridge motherboards, ivy bridge being the first Intel chipset generation to natively support USB 3.0. Both of these machines exhibit the same or a similarly situated problem as previously reported for my Samsung ativ9, Intel broadwell, laptop, that is USB connected storage devices do not usefully survive suspend/resume cycles. Because emb-qm77 connected USB 3.0 storage devices, usb_storage and/or uas, reliably disconnect/reconnect on every suspend/resume, I feel like the emb-qm77 MB is a better representative of the class of machines exhibiting this problem than the Samsung ativ9 where the problem only sporadically occurs. For me personally, machines of the ivy bridge to broadwell era are still eminently useful and would be even more useful if I could patch around this USB 3.0 storage device issue. Though the fault of these now longstanding problems could more accurately be ascribed to MB BIOS and/or device firmware failings, I feel like it may be easier and more general to patch around these problems at the OS kernel level rather than through individual BIOS or firmware patches. In particular, it seems conceptually desirable to extend the linux kernel's usb_persist mechanism to encompass disconnection and reconnection of USB 3.0 devices. Before I pursue this idea further I would like to ask: Does anyone else think that this would be a useful or even possible concept? If anyone is interested, I have previously attached usbmon, xhci_hcd, and usbcore traces of a emb-qm77 suspend resume cycle that encompass a connected USB 3.0 storage device. -- You may reply to this email to add a comment. You are receiving this mail because: You are watching the assignee of the bug.
