Bug 956831 - Instability with kernel-3.9.0-0.rc8.git0.1.fc19 on highbank systems
Summary: Instability with kernel-3.9.0-0.rc8.git0.1.fc19 on highbank systems
Keywords:
Status: CLOSED DUPLICATE of bug 963873
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 19
Hardware: arm
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jon Masters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 901844 901848
TreeView+ depends on / blocked
 
Reported: 2013-04-25 17:59 UTC by Paul Whalen
Modified: 2013-05-16 17:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-16 17:14:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Paul Whalen 2013-04-25 17:59:09 UTC
Description of problem:

When running the 3.9+ kernel on a highbank system it will crash with:

BUG: soft lockup - CPU#0 stuck for 23s! [python:850]
...
BUG: scheduling while atomic: python/850/0x40010000

When the system is reset with ipmi and rebooted it fail to boot with a kernel panic.


Version-Release number of selected component (if applicable):

kernel-3.9.0-0.rc8.git0.1.fc19

How reproducible:

Very, 'dmesg | fpaste' should produce the initial crash. 


Steps to Reproduce:
1. Install kernel-3.9.0-0.rc8.git0.1.fc19, reboot and run 'dmesg|fpaste'. If it works on the first attempt, reboot the system and try again.
 
  
Actual results:

System will crash, with:

BUG: soft lockup - CPU#0 stuck for 23s! [python:850]
...
BUG: scheduling while atomic: python/850/0x40010000

Reset the system with the ipmi tool, during the boot it will panic and oops.


Expected results:

Dmesg piped into fpaste with corresponding URL returned.

Additional info:

Full fpastes:

Initial crash with fpaste - http://fpaste.org/DULO/
After reset with ipmi - http://fpaste.org/wQbE/

Comment 1 Josh Boyer 2013-05-16 17:14:15 UTC

*** This bug has been marked as a duplicate of bug 963873 ***


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