[Bug 920581] New: Kernel panic when mounting USB hard disk
http://bugzilla.suse.com/show_bug.cgi?id=920581 Bug ID: 920581 Summary: Kernel panic when mounting USB hard disk Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: holgi@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 625353 --> http://bugzilla.suse.com/attachment.cgi?id=625353&action=edit journalctl.log I do have an USB hard disk that is mounted during boot via /etc/fstab UUID=f0dbd038-551d-4acf-8a0a-ce636e935b12 /usbvideo ext3 nofail 1 2 This is working fine with openSUSE 13.1. But with openSUSE 13.2 (all updates installed) accessing the data on that device is always resulting in a kernel Ops. I attached the journalctl output, if you need further information please let me know -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=920581
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=920581
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
--- Comment #3 from Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
--- Comment #4 from Oliver Neukum
The upstream has a fix 90a646c770c50cc206ceba0d7b50453c46c13c36 usb: Do not allow usb_alloc_streams on unconfigured devices
so 3.18 and later kernel should work. Meanwhile I backported the fix to openSUSE-13.2 branch now. Please test the kernel in OBS Kernel:openSUSE-13.2 repo later.
Feel free to reopen the bug if the problem still exists with the kernel containing this fix commit.
The device does not even accept its address after the reset. It looks like the state is not updated, but even if it were updated that would only prevent the oops, not make the device work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=920581
Oliver Neukum
http://bugzilla.suse.com/show_bug.cgi?id=920581
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c10
--- Comment #10 from Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c11
--- Comment #11 from Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c12
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c13
Oliver Neukum
Created attachment 639663 [details] journal-new
Issue still not solved. Device is there and can be mounted. "df command shows the size but when "ls" into the directory the command will not succeed. Instead attached messages in dmesg.
These are not kernel messages. Please do a sysrq-T -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c14
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c15
--- Comment #15 from Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=920581
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c16
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c17
Oliver Neukum
This problem does not appear on openSUSE Leap 42,1
Still, the fix went in and you now are seeing another error. We need to know, where "ls" hangs. Please do the sysrq-T -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=920581
http://bugzilla.suse.com/show_bug.cgi?id=920581#c18
Holger Sickenberg
http://bugzilla.suse.com/show_bug.cgi?id=920581
Oliver Neukum
participants (1)
-
bugzilla_noreply@novell.com