Red Hat Bugzilla – Bug 155992
[RHEL4-U3] Diskdump - Salvage kernel messages
Last modified: 2010-10-21 22:56:07 EDT
1. Feature Name: Salvage kernel messages which were not written
to a log file from a crash dump
Diskdump salvages lost messages from the crash dump
and appends to a log file.
Architectures (mark all that apply)
x 32-bit x86
x 64-bit Itanium2
x 64-bit AMD64/Intel EM64T
x 64-bit IBM POWER
31-bit IBM S/390
64-bit IBM zSeries
Dependencies: Diskdump, Sysklogd
External links: None
Priority (H,M,L): Low
Target Releases: RHEL4-U2
Target Release Date: 5/23/05
Drivers or hardware dependency: None
Target Kernel: RHEL4-U2 Beta
PM ACK for U2.
Status update from Nagahama-san:
Currently Tachino-san is working on making prototype.
30% done. That is diskdumputils modification only.
I want to drop this feature for RHEL4U2 because this has low priority and I have
other more important things which should be done. Please drop this from CanFix list.
Status update from Tachino-san indicates that this one won't be completed in
time for RHEL4 U2. So I am taking it off the U2 canfix list and moving it over
to the U3 proposed list.
I changed the component to diskdumputils because This feature does not require
Feature applied in RHEL4 version diskdumputils-1.2.1-2.
Akira-san, can you please provide verification that diskdumputils-1.2.1-2, as
referenced in RHEA-2006:066-03, addresses this bugzilla to your satisfaction and
that your quality testing was successful?
Since we have done testing, we report the results here.
1. Result of the testing
Overall result: PASS
- Regressions: None
- Unfixed bugs: None
2. Hardware that we used for the testing
3. Version of packages that we used for the testing
4. Additional Comments
Although there are slight bugs such as typo, we regard
the testing as PASS because this functionality itself works
We will fix the bugs in the next release timeframe.
Thanks for the testing results. Please make sure to open new bugzillas for the
additional issues you want to address (if you haven't done so already) because
this one will be closed as we go through the errata process.
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.