Bug 859296

Summary: kernel Oops kthread_data opcontrol
Product: [Fedora] Fedora Reporter: John Reiser <jreiser>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: gansalmon, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-04-08 14:47:14 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:
Embargoed:
Attachments:
Description Flags
photo of vga console with Oops traceback
none
syslog (/var/log/messages) for entire session none

Description John Reiser 2012-09-21 03:27:44 UTC
Created attachment 615258 [details]
photo of vga console with Oops traceback

Description of problem: random kernel Oops


Version-Release number of selected component (if applicable):
kernel-3.6.0-0.rc2.git2.1.fc18.x86_64


How reproducible: once only


Steps to Reproduce:
1. opcontrol --start
2. shutdown -h now
3.
  
Actual results: Oops; photo of VGA console will be attached


Expected results: no problem


Additional info:

Comment 1 Josh Boyer 2012-09-21 13:04:23 UTC
The picture of the traceback shows it isn't the first to happen on that machine.  It's tainted D and W.  Do you have the first oops in logs somewhere?

If you could update to the kernel in f18 updates-testing and try again that would be appreciated.

Comment 2 John Reiser 2012-09-21 14:04:54 UTC
Created attachment 615456 [details]
syslog (/var/log/messages) for entire session

No, there is no Oops report in syslog (entire syslog is attached.)  Perhaps this was an error-within-an-error.

I'm now running kernel-3.6.0-0.rc6.git0.2.fc18.x86_64, and I am also using serial console, logged via minicom on another machine.

Comment 3 Fedora End Of Life 2013-04-03 15:41:02 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19

Comment 4 Justin M. Forbes 2013-04-05 19:18:07 UTC
Is this still an issue with the 3.9 kernels in F19?

Comment 5 John Reiser 2013-04-05 20:31:30 UTC
I have not seen it in a few months on Fedora 18, kernel-3.8.4-202.fc18.x86_64 and recent predecessors.  I haven't seen it on Fedora 19, either; but that's on different hardware.