Bug 367781

Summary: kernel paging request at virtual address hangs system
Product: Red Hat Enterprise Linux 4 Reporter: Jim Waldram <jwaldram>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED NOTABUG QA Contact: Martin Jenner <mjenner>
Severity: high Docs Contact:
Priority: low    
Version: 4.5CC: jbaron, prarit
Target Milestone: ---   
Target Release: ---   
Hardware: athlon   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-26 16:34:03 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
/var/log/messages at 2 hangs
none
Sysreport on system none

Description Jim Waldram 2007-11-06 00:52:54 UTC 
Description of problem:system hangs with: 
kernel: Unable to handle kernel paging request at virtual address 009a7b5c

Version-Release number of selected component (if applicable):
Linux sova.uwyo.edu 2.6.9-55.0.2.EL #1 Tue Jun 12 17:47:10 EDT 2007 i686 athlon
i386 GNU/Linux

How reproducible:
Variable

Steps to Reproduce:Appears under heavy load, intermittently
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jim Waldram 2007-11-06 00:52:54 UTC 
Created attachment 248721 [details]
/var/log/messages at 2 hangs
Comment 2 Prarit Bhargava 2007-11-07 14:14:03 UTC 
Hi Jim, could you generate a sysreport from your system and attach it to this BZ?

Also, have you tried a newer version of RHEL4?

Thanks,

P.
Comment 3 Jim Waldram 2007-11-07 18:50:29 UTC 
Created attachment 250611 [details]
Sysreport on system

This is the sysreport on the system having the kernel paging request fault. 
The system has had various socketed hardware reseated.	No faults for last 24
hrs.  Previously faults would occurr 2 per day under heavy load.  Heavy load is
a compute and memory (1.5-2.5 GB) intensive application ITT IDL.
Comment 4 Prarit Bhargava 2007-11-13 14:22:01 UTC 
Jim, it seems like reseating changed the system behavior.  Could you give us a
status report in a few days to let us know if you are still seeing this panic?

Until then I am going to place this BZ in "NEEDINFO".

Thanks,

P.
Comment 5 Jim Waldram 2007-11-20 19:48:31 UTC 
The problem has not cropped up again.  The bug can be closed.  Replacing a
memory SIMM appears to have fixed the problem.  No memory errors were generated
with the "bad" SIMM.