Red Hat Bugzilla – Bug 477635
If diskdump fails, panic information should be displayed.
Last modified: 2013-08-05 23:50:45 EDT
Description of problem:
If all the following conditions are met, the system is rebooted.
- kernel.panic in /etc/sysctl.conf is set (for example, 10 seconds).
- fallback_on_err is 1.
- Both diskdump and netdump fail(or diskdump fails and netdump is not enabled).
Then many users who don't use a serial console cannot see information
about the cause of the panic. Therefore, if diskdump fails, system should be halted with panic information(back trace, etc).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. service diskdump initialformat; service diskdump start
2. dd if=/dev/zero of=/dev/sdb1 bs=1024 count=10; # i know this is bad, i'm
simulating hardware failure
3. echo 5 > /proc/sys/kernel/panic
4. echo c > /proc/sysrq-trigger
Diskdump fails and system hangs up.
System hangs up because of bz248666. If bz248666 is fix, system doesn't hang up. The system is rebooted after diskdump fails.
Diskdump fails and system halts with panic information.
Originally this problem was discussed on bz248666. In bz248666, the following problem was discussed.
- System hangs up after diskdump fails.
- Panic information should be displayed if diskdump fails.
These problems is separatable, so this bz is newly opened for the latter problem.
Created attachment 327667 [details]
Patch to add reboot_on_err(kernel)
Created attachment 327668 [details]
Patch to add reboot_on_err(diskdumputils)
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
(In reply to comment #2)
> Created an attachment (id=327668) [details]
> Patch to add reboot_on_err(diskdumputils)
If you want to add this patch to the existing RHEL4.8 diskdumputils errata:
RHEA-2009:8209-01 - diskdumputils documentation update
Then a separate Bugzilla with the "diskdumputils" component must
be created. This BZ is for the "kernel" component only.
Then to get the diskdumputils change checked in, the new bugzilla
must adhere to the following:
RHEL4 CVS Check-in Policy
As of 11pm EDT on Tuesday March 13, 2007, commits to the RHEL-4 branch
need to contain at least one Resolves:, Related:, or Reverts: line,
containing at least one Bugzilla ID or CVE ID in a supported format,
in the log message or spec file %changelog.
Update: As of 4pm EDT on Monday August 25, 2008, checkins on the RHEL-4
branch must reference one or more Bugzillas with the following flag state
or the commit will be denied:
(rhel-4.8 == +) or
(cluster-4.8 == +) or
(rhel-4.8 == ? and pm_ack == +) or
(cluster-4.8 == ? and pm_ack == +)
> Then a separate Bugzilla with the "diskdumputils" component must
> be created. This BZ is for the "kernel" component only.
Thanks for the information. Now I am rewriting the patch of diskdumputils. I'll open new bz for it.
Created attachment 328499 [details]
A patch to support halt_on_error option
I upload the latest patch. This patch has been already posted to review.
> > Then a separate Bugzilla with the "diskdumputils" component must
> > be created. This BZ is for the "kernel" component only.
> Thanks for the information. Now I am rewriting the patch of diskdumputils. I'll
> open new bz for it.
I opened bz479337.
Committed in 78.28.EL . RPMS are available at http://people.redhat.com/vgoyal/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 therefore 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.