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 63664 - magic sysrq not fully functional
magic sysrq not fully functional
Product: Red Hat Public Beta
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2002-04-16 22:31 EDT by Kris Urquhart
Modified: 2007-04-18 12:42 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-04-16 22:31:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:348 normal SHIPPED_LIVE Updated sysklogd package 2004-08-18 00:00:00 EDT

  None (edit)
Description Kris Urquhart 2002-04-16 22:31:37 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98; Win 9x 4.90)

Description of problem:
h and s work, but p, m, and t just produce the header with no data from the 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. echo "1" > /proc/sys/kernel/sysrq
2. alt-sysrq-t (for example)

Actual Results:  SysRq: Show State
<no data>

Expected Results:  SysRq: Show State
<data from kernel>

Additional info:
Comment 1 Bill Nottingham 2002-04-17 18:11:38 EDT
Fixed in kudzu-0.99.52-1 and sysklogd-1.4.1rh-8.
Comment 2 John Flanagan 2004-08-18 10:55:31 EDT
An errata 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.


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