Bug 687858 - Kernel panics "Kernel panic - not syncing: kernel/sched.c:2983: spin_lock(kernel/printk.c:ffffffff80455900) already locked by kernel/sched.c/2983"
Summary: Kernel panics "Kernel panic - not syncing: kernel/sched.c:2983: spin_lock(ker...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Prarit Bhargava
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-15 15:35 UTC by Petr Matousek
Modified: 2012-06-20 16:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 16:09:04 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.