Bug 706812 - Kernel panic after the CPU load rearch 100% nearly
Summary: Kernel panic after the CPU load rearch 100% nearly
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-23 05:46 UTC by Zhongqiang Dou
Modified: 2015-05-11 22:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-07-11 13:39:06 UTC
Target Upstream Version:

Attachments (Terms of Use)
The snapshot of the kernel panic. (90.05 KB, image/png)
2011-05-23 05:46 UTC, Zhongqiang Dou 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Zhongqiang Dou 2011-05-23 05:46:35 UTC 
Created attachment 500332 [details]
The snapshot of the kernel panic.

Description of problem:
Our server is a VM on qemu hypevisor and it hit the kernel panic many times in past weeks. We got a snapshot, please help to analyse the snapshot.

Version-Release number of selected component (if applicable):
2.6.32-71.7.1.el6.x86_64

How reproducible:
Sometimes

Steps to Reproduce:
Don't know how to reproduce and provide the information of the server.
1. It is running the perl scripts to provide service.
2. The CPU load would reach 100% nearly before the kernel panic.
  
Actual results:


Expected results:
no panic.

Additional info:
Comment 2 RHEL Program Management 2011-10-07 15:36:04 UTC 
Since RHEL 6.2 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Comment 3 Siddharth Nagar 2012-07-11 13:39:06 UTC 
Closing as I believe this is no longer an issue. Please re-open if necessary.
Note You need to log in before you can comment on or make changes to this bug.