Bug 191964

Summary: Kernel panic
Product: Red Hat Enterprise Linux 3 Reporter: George DORILA <george.dorila>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED CANTFIX QA Contact: Brian Brock <bbrock>
Severity: urgent Docs Contact:
Priority: medium    
Version: 3.0CC: petrides
Target Milestone: ---   
Target Release: ---   
Hardware: ia64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-09-13 12:39:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the os message file none

Description George DORILA 2006-05-16 16:17:18 UTC 
Description of problem:
I have 2 identical nodes linked into a cluster. It is a hot standby 
configuration. It is a Oracle database production system. A Kernel panic rises 
on the âhotâ node (the nod with Oracle service) after 4-5 days of running. It 
is happen on both nodes.


Version-Release number of selected component (if applicable): 
Linux nod1 2.4.21-27.0.4.EL #1 SMP Sat Apr 16 18:37:19 EDT 2005 ia64 ia64 ia64 
GNU/Linux


How reproducible: ???


Steps to Reproduce:
1. increase the system load (startup Oracle database)
2. waiting for 4-5 days
3. during massive reads (the oracle export tool)

Actual results: The database froze sometime or entire system froze. When entire 
system froze the Cluster initiate a fail over procedure and the Oracle service 
switch to the second node.

Expected results: No Oops!


Additional info: message.1 lines .. search words "keventd[6]: Oops 
11003706212352"
A RedHat case is open 883032
Comment 1 George DORILA 2006-05-16 16:17:18 UTC 
Created attachment 129222 [details]
the os message file
Comment 2 Ernie Petrides 2006-05-16 20:55:56 UTC 
RHEL3 is now closed.
Comment 3 Ernie Petrides 2006-05-16 20:58:25 UTC 
*** Bug 191965 has been marked as a duplicate of this bug. ***
Comment 4 Prarit Bhargava 2007-09-13 12:39:27 UTC 
Closing re: comment #2.

P.