Bug 145409 - panic_on_oops hook removed on ia64 by diskdump patch
panic_on_oops hook removed on ia64 by diskdump patch
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
3.0
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Tatsuo Uchida
Brian Brock
:
Depends On:
Blocks: 132991
  Show dependency treegraph
 
Reported: 2005-01-17 21:19 EST by Ernie Petrides
Modified: 2007-11-30 17:07 EST (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-05-18 09:29:08 EDT
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 Ernie Petrides 2005-01-17 21:19:29 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
The "diskdump for IPF" support patch added in RHEL3 U3 mistakenly
disabled support for panic_on_oops on the ia64 architecture.  I
believe that:

  if (panic_on_oops)
    panic("Fatal exception");

should be added after the call to:

  try_crashdump(regs);

in the ia64 version of die(), which would mirror how x86 and x86_64 work.

Version-Release number of selected component (if applicable):
kernel-2.4.21-27.EL

How reproducible:
Always

Steps to Reproduce:
1. invoke code path w/BUG() or cause an oops via /proc/sysrq-trigger (with "c")
2.
3.
  

Actual Results:  oops printed to /var/log/messages, but system keeps running

Expected Results:  system should panic

Additional info:
Comment 4 Ernie Petrides 2005-02-23 17:53:24 EST
A fix for this problem has just been committed to the RHEL3 U5
patch pool this afternoon (in kernel version 2.4.21-28.EL).
Comment 5 Tim Powers 2005-05-18 09:29:08 EDT
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.

http://rhn.redhat.com/errata/RHSA-2005-294.html

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