|
Bugzilla – Full Text Bug Listing |
| Summary: | Kernel panic when mounting USB hard disk | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Holger Sickenberg <holgi> |
| Component: | Kernel | Assignee: | E-mail List <kernel-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | holgi, jslaby, oneukum, tiwai |
| Version: | 13.2 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 13.2 | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
journalctl.log
journal-new-kernel.log dmesg output openSUSE 13.1 dmesg-new journal-new |
||
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.
kernel-desktop-3.16.7-51.1.gea5ed8c.x86_64.rpm did not solve the problem for me. See attached log file. Created attachment 626044 [details]
journal-new-kernel.log
(In reply to Takashi Iwai from comment #1) > 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. Please provide the log 13.1 if you still have it. Created attachment 626063 [details]
dmesg output openSUSE 13.1
openSUSE-SU-2015:0713-1: An update that solves 13 vulnerabilities and has 52 fixes is now available. Category: security (important) Bug References: 867199,893428,895797,900811,901925,903589,903640,904899,905681,907039,907818,907988,908582,908588,908589,908592,908593,908594,908596,908598,908603,908604,908605,908606,908608,908610,908612,909077,909078,909477,909634,910150,910322,910440,911311,911325,911326,911356,911438,911578,911835,912061,912202,912429,912705,913059,913466,913695,914175,915425,915454,915456,915577,915858,916608,917830,917839,918954,918970,919463,920581,920604,921313,922542,922944 CVE References: CVE-2014-8134,CVE-2014-8160,CVE-2014-8559,CVE-2014-9419,CVE-2014-9420,CVE-2014-9428,CVE-2014-9529,CVE-2014-9584,CVE-2014-9585,CVE-2015-0777,CVE-2015-1421,CVE-2015-1593,CVE-2015-2150 Sources used: openSUSE 13.2 (src): bbswitch-0.8-3.6.6, cloop-2.639-14.6.6, crash-7.0.8-6.6, hdjmod-1.28-18.7.6, ipset-6.23-6.6, kernel-docs-3.16.7-13.2, kernel-obs-build-3.16.7-13.7, kernel-obs-qa-3.16.7-13.1, kernel-obs-qa-xen-3.16.7-13.1, kernel-source-3.16.7-13.1, kernel-syms-3.16.7-13.1, pcfclock-0.44-260.6.2, vhba-kmp-20140629-2.6.2, virtualbox-4.3.20-10.2, xen-4.4.1_08-12.2, xtables-addons-2.6-6.2 It seems so. If not, please reopen. Created attachment 639662 [details]
dmesg-new
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.
So reopen the bug. (In reply to Holger Sickenberg from comment #11) > 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 When doing sysrq-T I get message:
"SysRq . This sysrq operation is disabled."
What do I need to do to enable?
Run once: sysctl kernel.sysrq=1 For permanent setup, use /etc/sysctl.conf or /etc/sysctl.d/* Or, you can manually trigger via echo t > /proc/sysrq-trigger This problem does not appear on openSUSE Leap 42,1 (In reply to Holger Sickenberg from comment #16) > 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 I unfortunately do not have a openSUSE 13.2 on that machine installed still. |
Created attachment 625353 [details] 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