Bug 62786

Summary: Kernel oops on a slimmerlot with beta4 -- "Unable to handle kernel paging request at virtual address"
Product: [Retired] Red Hat Linux Reporter: Clay Cooper <clay_cooper>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: afom_m, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, joshua_giles, matt_domsch, michael_e_brown, robert_hentosh, rogelio_noriega
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-04-11 20:00:04 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
Ksymoops output from newburn kernel oops none

Description Clay Cooper 2002-04-05 16:50:04 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011019
Netscape6/6.2

Description of problem:
On a slimmerlot with hampton beta4 (2.4.18-0.13smp) installed, bios A02, 1GB
ram, 2GB swap, LSI 22320 boot controller:

Kernel oops running newburn with following error message:
"Unable to handle kernel paging request at virtual address 37aedeee
c0131036"

Occured after less than an hour of newburn.

Ksymoops output attached.

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


How reproducible:
Always

Steps to Reproduce:
1.Install hampton beta4 on a slimmerlot
2.Run newburn for atleast an hour
3.Note kernel oops
	

Actual Results:  Oops

Expected Results:  No oops

Additional info:

Appears to be a different oops than bug 61033
Comment 1 Clay Cooper 2002-04-05 16:50:53 UTC 
Created attachment 52384 [details]
Ksymoops output from newburn kernel oops
Comment 2 Arjan van de Ven 2002-04-05 16:54:47 UTC 
2.4.18-0.13 had a broken oops reporter; you hit an oops and then the oops
reporter oopsed ;( fixed in 2.4.18-0.16
Comment 3 Clay Cooper 2002-04-11 19:59:57 UTC 
Not reproduced after 24 hours of newburn on a slimmerlot w/ 2.4.18-0.16smp.
Comment 4 Arjan van de Ven 2002-04-12 12:29:56 UTC 
That's called fixed; if it oopses later on please reopen