Bug 1043204

Summary: kernel oops in dvb_frontend/kthread_stop
Product: [Fedora] Fedora Reporter: Arne Woerner <arne_woerner>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-01-04 04:24:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
syslog messages regardind the failed disconnect attempt
none
first Trace none

Description Arne Woerner 2013-12-14 22:33:02 UTC
Created attachment 836851 [details]
syslog messages regardind the failed disconnect attempt

Description of problem:
When I disconnect my DVB-T USB stick, I sometimes get a kernel oops and the DVB subsystem is unusable, so that I have to reboot, which makes automatic recording unstable.

Version-Release number of selected component (if applicable):
Linux neo.intern.wgboome.org 3.11.10-200.fc19.i686 #1 SMP Mon Dec 2 20:48:22 UTC 2013 i686 i686 i386 GNU/Linux

How reproducible:
seldom (maybe 1% of all disconnects)

Steps to Reproduce:
1. connect the stick
2. disconnect the stick

Actual results:
sometimes I get a kernel oops (see attachment).

Expected results:
it should just destroy the unneeded dvb structures...

Additional info:

Comment 1 Josh Boyer 2013-12-16 14:41:14 UTC
It's tainted as D in the backtrace you provided, which means the machine was already dying.  Do you happen to have the first backtrace printed out?

Comment 2 Arne Woerner 2013-12-16 19:41:34 UTC
the backtrace is the first Oops since the reboot at 2013-12-07...

could the D come from the "BUG:" message some lines above?
it is the first "BUG:" since the reboot at 2013-12-07...

-arne

Comment 3 Arne Woerner 2013-12-16 19:46:54 UTC
Created attachment 837389 [details]
first Trace

oops...

there was a "divide error" some minutes before...
I attached that Trace...

-arne

Comment 4 Justin M. Forbes 2014-01-03 22:03:31 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs.

Fedora 19 has now been rebased to 3.12.6-200.fc19.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20.

If you experience different issues, please open a new bug report for those.

Comment 5 Arne Woerner 2014-01-03 22:50:01 UTC
that problem did not occur again...

i am testing kernel 3.12 since today...
no problem so far... :-)

thx.

-arne

Comment 6 Justin M. Forbes 2014-01-04 04:24:39 UTC
Closing then, feel free to reopen if it is still occuring.