Bug 870117 - Kernel Panic in cfq_dispatch_requests()
Kernel Panic in cfq_dispatch_requests()
Status: NEW
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity unspecified
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
Depends On:
  Show dependency treegraph
Reported: 2012-10-25 11:09 EDT by William Lovaton
Modified: 2017-02-10 06:49 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Screenshot of the kernel panic (90.41 KB, image/jpeg)
2012-10-25 11:09 EDT, William Lovaton
no flags Details

  None (edit)
Description William Lovaton 2012-10-25 11:09:23 EDT
Created attachment 633404 [details]
Screenshot of the kernel panic

Description of problem:
This is a virtual machine (under VMWare ESX 4.2) acting as a web server running Apache/PHP/MySQL from the distro and all of a sudden it showed in the console the panic attached to this bug report.

I have been searching all over but I failed to find something related to this.  I'm in the plan to updating to RHEL 6.3 but I'm reporting the problem anyway.

Version-Release number of selected component (if applicable):
* Red Hat Enterprise Linux Server release 6.2 (Santiago)
* kernel-2.6.32-220.el6.x86_64
* glibc-2.12-1.47.el6.x86_64

How reproducible:
This was the first time so far.  The server usually is very stable so I have no idea how to reproduce this.
Comment 2 RHEL Product and Program Management 2012-12-14 03:24:02 EST
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3 Anonymous 2017-02-10 06:49:41 EST

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