Bug 790445 - When using raw dump in kdump, no stats displayed and SIGUSR1 message appears.
Summary: When using raw dump in kdump, no stats displayed and SIGUSR1 message appears.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kexec-tools
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dave Young
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-14 14:50 UTC by Don Koch
Modified: 2013-02-13 22:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 22:14:16 UTC
Type: ---


Attachments (Terms of Use)
mkdumprd patch (367 bytes, patch)
2012-02-14 14:50 UTC, Don Koch
no flags Details | Diff

Description Don Koch 2012-02-14 14:50:00 UTC
Created attachment 561930 [details]
mkdumprd patch

Description of problem:
When kdump.conf is set for a raw dump, which uses dd, when the dump starts, a message like "1546: SIGUSR1" appears and no progress stats appear.

Version-Release number of selected component (if applicable):
kexec-tools-2.0.2-29.fc16

How reproducible:
Always.

Steps to Reproduce:
1.Set up machine for kernel dumps (install kexec-tools, change boot configure line, etc.).
2.echo c > /proc/sysrq-trigger
3.wait for start of dump
  
Actual results:
Prints out "1546: SIGUSR1" or similar (process number may change).

Expected results:
Progress stats should be displayed.

Additional info:
Problem is in created monitor_dd_progress script from mkdumprd. It looks for a process containing the string "dd" and periodically sends SIGUSR1 signals to it.
It's expecting to find "dd if=..." or "dd of=...", but finds monitor_dd_progress
and kills itself.

Patch attached.

Comment 1 Fedora Admin XMLRPC Client 2012-04-16 06:12:51 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2013-01-16 17:29:43 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 22:14:20 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.