DescriptionYuuichi Nagahama
2004-12-07 19:43:17 UTC
Description of problem:
When panic occurs, diskdump stalls before printing any messages on
console.
RHEL4 has the same issue as BZ#138815.
Version-Release number of selected component (if applicable):
RHEL4 Beta2
How reproducible: Sometimes
Steps to Reproduce:
1. Set up diskdump with dump device on megaraid2.o
2. Put I/O load on the disk in which dump device is included
3. Crash kernel by SysRq+c
Actual results:After oops message, no diskdump related message
is printed on console.
Expected results:The message below follows oops message:
CPU frozen: #0#1#2#3
CPU#0 is executing diskdump.
start dumping
check dump partition
...
Additional info:
Comments from meeting we are having with the Fujitsu team: Tatsu is currently
working on a RHEL3 based resolution to this problem. Pending successful review
there, he will port to RHEL4.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHSA-2005-420.html