Bug 455074

Summary: kernel panic with kernel version 2.6.9-67.0.20.EL
Product: Red Hat Enterprise Linux 4 Reporter: RHEL Product and Program Management <pm-rhel>
Component: kernelAssignee: Vitaly Mayatskikh <vmayatsk>
Status: CLOSED ERRATA QA Contact: Martin Jenner <mjenner>
Severity: high Docs Contact:
Priority: high    
Version: 4.8CC: jburke, kgraham, mmatsuya, phaleintx, pm-eus, pveiga, pzijlstr, sebastien.ruel, smikkili, sprabhu, tao, vgoyal
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-04 15:00:32 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 453507    
Bug Blocks:    

Description RHEL Product and Program Management 2008-07-11 16:23:15 EDT
This bug has been copied from bug #453507 and has been proposed
to be backported to 4.7 z-stream (EUS).
Comment 3 Vitaly Mayatskikh 2008-07-22 17:48:40 EDT
sys_times() patches were reverted in 78.0.1
Comment 8 errata-xmlrpc 2008-08-04 15:00:32 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.

Comment 10 Guy Streeter 2008-10-08 10:36:55 EDT
This BZ is hard to find in a search because it doesn't contain the strings you would search for, such as
kernel BUG at kernel/exit.c
so I'm adding them :)
Comment 11 Michael Kearey 2008-10-08 23:19:23 EDT
*** Bug 462280 has been marked as a duplicate of this bug. ***
Comment 12 Vitaly Mayatskikh 2008-10-22 18:01:46 EDT
*** Bug 467648 has been marked as a duplicate of this bug. ***
Comment 14 Prarit Bhargava 2009-03-31 10:16:46 EDT
*** Bug 491715 has been marked as a duplicate of this bug. ***