Bug 715741 - kdump is not performed as expected
Summary: kdump is not performed as expected
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact: Caspar Zhang
URL:
Whiteboard:
: 748700 (view as bug list)
Depends On:
Blocks: 748748 748749
TreeView+ depends on / blocked
 
Reported: 2011-06-23 14:57 UTC by QinXie
Modified: 2011-10-26 14:29 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 748748 (view as bug list)
Environment:
Last Closed: 2011-10-26 14:29:01 UTC


Attachments (Terms of Use)

Description QinXie 2011-06-23 14:57:49 UTC
1. kdump status is odd:
restarting kdump with new configuration...
Stopping kdump:[  OK  ]
Error: kdump restart failed
"service kdump start" has output on stderr
mount: block device debug is write-protected, mounting read-only
mount: cannot mount block device debug read-only
Checking kdump service
kdump is running

2. kdump was not really performed before reboot

For detail, please refer to the belowing test output, kdump is stataus is odd, and kdump was not really :
https://hardware.redhat.com/results.cgi?cert_id=709613&id=231345

Comment 1 QinXie 2011-06-23 15:02:11 UTC
cert#709613: https://hardware.redhat.com/hwcert/show.cgi?id=709613

Comment 3 Greg Nichols 2011-10-13 19:31:17 UTC
 From the logs:

Error: kdump restart failed
"service kdump start" has output on stderr
mount: block device debug is write-protected, mounting read-only
mount: cannot mount block device debug read-only


it seems as though kdump may not be running correctly.  Can it be restarted manually via:

> service kdump restart

Comment 4 Caspar Zhang 2011-10-25 08:32:06 UTC
*** Bug 748700 has been marked as a duplicate of this bug. ***

Comment 6 Caspar Zhang 2011-10-26 14:18:05 UTC
(In reply to comment #3)
> it seems as though kdump may not be running correctly.  Can it be restarted
> manually via:
> 
> > service kdump restart

Yes, only stderr output were printed, which caused v7 to fail.


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