Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 591788 - Kdump hangs under RHEL5.5 64bit when sending SysRq in AMD platform
Kdump hangs under RHEL5.5 64bit when sending SysRq in AMD platform
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
5.5
athlon Linux
low Severity medium
: rc
: ---
Assigned To: Kiran Thirumalai
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-13 02:52 EDT by Rocky Shi
Modified: 2015-08-24 02:27 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-11-12 22:35:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Rocky Shi 2010-05-13 02:52:26 EDT
Description of problem:
>> Kdump hangs under RHEL5.4 when running the following commands.
>> # echo 1 > /proc/sys/kernel/sysrq
>> # echo c > /proc/sysrq-trigger

Version-Release number of selected component (if applicable):
>> RHEL 5.5 64bit

Steps to Reproduce:
>> 1. Boot to RHEL5.5 64bit
>> 2. Enter command line
>> 3. Kdump hangs under RHEL5.4 when running the following commands.
>> # echo 1 > /proc/sys/kernel/sysrq
>> # echo c > /proc/sysrq-trigger
  
Actual results:
>> System halt

Expected results:
>> System reboot

Additional info:
>> 1. Processor: AMD Budapest
>> 2. Chipset: MCP55

>> There is no issue on RHEL 5.5 32 bit
Comment 1 Rocky Shi 2010-05-13 03:01:48 EDT
https://bugzilla.redhat.com/show_bug.cgi?id=473404

This similar bug ever was reported, but it seems there were not do a complete fix since RHEL 5.5 64bit still failed in this command.
Comment 2 John Feeney 2013-11-12 22:35:24 EST
This Bugzilla has been reviewed by Red Hat and is not planned on being
addressed in Red Hat Enterprise Linux 5, and therefore is being closed.
If this bug is critical to production systems, please contact your Red
Hat support representative and provide a sufficient business justification
in order to re-open it.

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