Bug 687858

Summary:	Kernel panics "Kernel panic - not syncing: kernel/sched.c:2983: spin_lock(kernel/printk.c:ffffffff80455900) already locked by kernel/sched.c/2983"
Product:	Red Hat Enterprise Linux 4	Reporter:	Petr Matousek <pematous>
Component:	kernel	Assignee:	Prarit Bhargava <prarit>
Status:	CLOSED WONTFIX	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.9	CC:	prarit, vgoyal
Target Milestone:	rc	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 16:09:04 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Petr Matousek 2011-03-15 15:35:10 UTC

Description of problem:

After reserving a machine from beaker and starting test execution I got Kernel panic:
kernel/sched.c/2983
kernel/sched.c/483
kernel/module.c/2132 

os: RHEL4-U9 
arch: x86_64
Job: J:62365
machine: hp-dl785g6-01.rhts.eng.bos.redhat.com

console log:
http://lab2.rhts.eng.bos.redhat.com/beaker/logs/recipes/127511///console.log

Version-Release number of selected component (if applicable):
2.6.9-100.EL

How reproducible:
unknown

Steps to Reproduce:
1. Reserve the same machine from beaker
2. Clone the job J:62365
  
Actual results:
Job execution ends with Kernel panic

Expected results:
No Kernel panic appears

Additional info:

Comment 1 Prarit Bhargava 2011-03-18 12:30:49 UTC

console log:
http://lab2.rhts.eng.bos.redhat.com/beaker/logs/recipes/127511///console.log

404.

P.

Comment 2 Vivek Goyal 2011-03-18 13:32:11 UTC

Prarit above link does not work. Can you check again.

Comment 3 Vivek Goyal 2011-03-18 13:34:07 UTC

Oh, i noticed that prarit is also complaining about 404. Ignore my comment prarit. So this is question to petr to provide right link.

Comment 5 Jiri Pallich 2012-06-20 16:09:04 UTC

Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.