[Bug 944830] New: Very slow USB recognition
http://bugzilla.opensuse.org/show_bug.cgi?id=944830 Bug ID: 944830 Summary: Very slow USB recognition Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: 64bit OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: ionmich@libero.it QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Kingston USB3/2 stick not immediately recognized by openSUSE 13.2 64bit KDE running on desktop box OR on netbook. Steps taken to diagnose. 1. I booted a live Tumbleweed 64bit KDE DVD which I had downloaded about a month ago and have not bothered to use. This was on my 64bit daily used desktop box. Result-USB stick was incredibly slow to be recognized by Device Notifier or "fdisk -l". 2. I booted a live 13.2 32bit KDE DVD on the same desktop box. Result-USB stick was incredibly slow to be recognized by Device Notifier or "fdisk -l". 3. I booted my backup server which uses 13.1 32bit console-only installation. Result-USB stick was immediately recognized by "fdisk -l". 4. I booted a live 13.1 32bit KDE DVD on my 64bit daily used desktop box. Result-USB stick was immediately recognized by Device Notifier and "fdisk -l". 5. I booted a live 13.1 64bit KDE DVD on my 64bit daily used desktop box. Result (and I was surprised)-USB stick was immediately recognized by Device Notifier and "fdisk -l". Conclusion - Problem lies with 13.2 not with Kingston. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c1
Takashi Iwai
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c3
Raul Gomez
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c4
Oliver Neukum
[522497.817278] sd 4:0:0:0: [sdb] Assuming drive cache: write through [522497.845210] sdb: sdb1 [522497.846432] sd 4:0:0:0: [sdb] Attached SCSI removable disk [522558.442312] usb 2-2: reset SuperSpeed USB device number 2 using xhci_hcd
As you can see by the timing information, the device gets into some kind of error state, leading to a timeout and a subsequent reset. Unfortunately the log doesn't tell us, which command triggers the bad response. There are several candidates. Do you get a similar delay when you use "fdisk -l"? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c5
--- Comment #5 from Raul Gomez
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c6
--- Comment #6 from Oliver Neukum
Nope, fdisk -l finishes in 5ms approx.
Is there any work around for this?
The work around is to avoid the command that the device does not like. For that we need to find out which command is the problem. Could you run a kernel with CONFIF_USB_STORAGE_DEBUG set (e.g. the debug flavor)? It will show the commands going to the device in the log? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c9
Raul Gomez
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
Raul Gomez
http://bugzilla.opensuse.org/show_bug.cgi?id=944830
http://bugzilla.opensuse.org/show_bug.cgi?id=944830#c10
--- Comment #10 from Raul Gomez
(In reply to Raul Gomez from comment #5)
Nope, fdisk -l finishes in 5ms approx.
Is there any work around for this?
The work around is to avoid the command that the device does not like. For that we need to find out which command is the problem. Could you run a kernel with CONFIF_USB_STORAGE_DEBUG set (e.g. the debug flavor)? It will show the commands going to the device in the log?
Haven't had the time to try the debug Kernel, I'm planning to do this today Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com