Red Hat Bugzilla – Bug 142167
[RHEL4][Diskdump] smp_call_function issue
Last modified: 2007-11-30 17:07:15 EST
Description of problem:
When panic occurs, diskdump stalls before printing any messages on
RHEL4 has the same issue as BZ#138815.
Version-Release number of selected component (if applicable):
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.
check dump partition
Created attachment 108645 [details]
ppc64 support for dump_smp_call_function(), v1
Here's ppc64 support for the dump_smp_call_function() for RHEL4.
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.
Created attachment 110047 [details]
dump_smp_call_function(i386 and x86-64 )
This patch is for i386 and x86-64 for dump_smp_call_function(), v3.
The patches were posted to rhkernel-list.
The all of patches Tatsuo posted are incorporated in 2.6.9-6.18.EL on 3/3.
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.