Bug 64492 - Red Hat 7.2 with kernel 2.4.9-18 does not reset after an MCA
Summary: Red Hat 7.2 with kernel 2.4.9-18 does not reset after an MCA
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.2
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-06 18:57 UTC by Need Real Name
Modified: 2008-08-01 16:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:39:33 UTC
Embargoed:

Attachments (Terms of Use)
MCA Logging patch for 2.4.9-18 kernel (30.13 KB, patch)
2002-05-15 00:43 UTC, Jenna Hall 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:104 0 high SHIPPED_LIVE Several bugs fixed in new kernel 2002-05-30 04:00:00 UTC

Description Need Real Name 2002-05-06 18:57:56 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)

Description of problem:
After an MCA, the OS (2.4.9-18) does not reset as it should have per IA-64 
Error Handling Guide. The post code goes to E8 as expected, and then to E6. The 
MCA error log is correctly written to the flash but OS hangs in the MCA handler 
prior to the SAL call for reset. The system requires a manual reset.


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


How reproducible:
Always

Steps to Reproduce:

	

Additional info:
Comment 1 Jenna Hall 2002-05-15 00:43:49 UTC 
Created attachment 57345 [details]
MCA Logging patch for 2.4.9-18 kernel
Comment 2 Bugzilla owner 2004-09-30 15:39:33 UTC 
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/
Note You need to log in before you can comment on or make changes to this bug.