Red Hat Bugzilla – Bug 479337
[diskdumputils] Support halt_on_error option
Last modified: 2013-08-05 23:50:45 EDT
Created attachment 328501 [details]
A patch to support halt_on_error
Description of problem:
In RHEL4.8, the diskdump option "halt_on_error" will be newly supported(BZ#477635), so README document in diskdumputils needs to be fixed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Read README
The fix for this bug is part of the fix for bug 248666.
Bug 248666 is used for kernel, and this one is used for
user space pkg, diskdump. hence inherit bug 248666's flag/permission.
Created attachment 328505 [details]
A patch to support halt_on_error [v2]
Just fix typo
MODIFIED: CVS Tag: diskdumputils-1_4_1-7
(In reply to comment #1)
> The fix for this bug is part of the fix for bug 248666.
> Bug 248666 is used for kernel, and this one is used for
> user space pkg, diskdump. hence inherit bug 248666's flag/permission.
Actually the kernel part for this BZ is not bug 248666, but rather 477635:
Bug 477635 - If diskdump fails, panic information should be displayed.
Vivek Goyal will be applying the kernel-side patch today for
his next RHEL4 kernel rebuild.
Similar to what you did for version 1.4.1-6, can you re-run
basic sanity tests on the new diskdumputils-1.4.1-7 package
for the QA procedure for the diskdumputils errata?
RHEA-2009:8209-03 - diskdumputils documentation update
You can report your test results here, and I will re-post them
in the errata.
> Vivek Goyal will be applying the kernel-side patch today for
> his next RHEL4 kernel rebuild.
Update: Vivek will not be building a new kernel today, but rather
he will do so tomorrow.
The latest RHEL4 kernel version 2.6.9-78.28 contains the kernel-side patch
related for kernel bugzilla 477635:
* Tue Jan 13 2009 Vivek Goyal <email@example.com> [2.6.9-78.28]
-audit: remove bogus newlines in execve and path audit records (Jiri Pirko) 
-igb: set CONFIG_IGB_LRO=y for igb driver update (Vivek Goyal) [452289 435886]
-system reboot fails after diskdump/netdump (Takao Indoh) 
-diskdump: fix diskdump to stop system when diskdump fails (Takao Indoh) 
-igb: update to upstream version 1.2.45-k2 (Andy Gospodarek) [452289 435886]
-powernow k8: provide c state override when using tscsync (Brian Maly) 
-x86_64 race condition at shutdown panic (Ivan Vecera) 
-nfs4: handle incomplete opens more comprehensively (Jeff Layton) 
-identify pm timer calibration issues during boot (Prarit Bhargava) 
-Fix pm timer kernel option in Kconfig file (Prarit Bhargava) 
-nfsv4: add support for rdattr_error in nfsv4 readdir requests (Jeff Layton) 
-nfsv4: fix problems with callback thread shutdown (Jeff Layton) 
Can you please run a basic sanity test using kernel 2.6.9-78.28 with
diskdumputils 1.4.1-7? And then report the results here.
Originally it seems that README is written so that the length of each line can be shorter than 80 columns, but I found that the new sentences I added include the lines which are longer than 80 columns. Should I fix this? I can fix this soon if needed.
(In reply to comment #9)
> Hi Dave,
> Originally it seems that README is written so that the length of each line can
> be shorter than 80 columns, but I found that the new sentences I added include
> the lines which are longer than 80 columns. Should I fix this? I can fix this
> soon if needed.
In my opinion, it's really not that important.
Ok, I also think it's trivial. I just wondered whether there are those who care this. Thanks.
>Can you please run a basic sanity test using kernel 2.6.9-78.28 with
>diskdumputils 1.4.1-7? And then report the results here.
I tested on i386/x86_64/ia64 and there is no problem.
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.