Bug 84332 - kernel 2.4.18-24.7.x i586 oops - Unable to handle kernel paging request at virtual address 8b4b75d2
kernel 2.4.18-24.7.x i586 oops - Unable to handle kernel paging request at vi...
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.3
i586 Linux
high Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-14 11:30 EST by Greg Bailey
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-09-30 11:40:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screen contents of kernel oops (1.01 KB, text/plain)
2003-02-14 11:31 EST, Greg Bailey
no flags Details

  None (edit)
Description Greg Bailey 2003-02-14 11:30:33 EST
Description of problem:

On an old pentium workstation (i586) I run a firewall/router/NAT between
internal network and cable-modem attached internet connection.  Twice in the
last 2 weeks I've come across an "Oops" on the screen.  Not sure what could have
caused it, but will attach what I saw on the screen.

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

RedHat 7.3 with current kernel (kernel-2.4.18-24.7.x.i586.rpm) and all other
errata up-to-date.

How reproducible:

Not very.  Not sure what caused it.

Steps to Reproduce:
1.  Leave machine alone??
2.  Wait indeterminate amount of time
3.
    
Actual results:

Total loss of functionality (obviously)

Expected results:

Working system.

Additional info:

I wasn't able to use any of the alt-scroll-lock or similar key
combinations--they didn't seem to do anything.  Nothing unusual in the logs
before the lockup occurred.
Comment 1 Greg Bailey 2003-02-14 11:31:50 EST
Created attachment 90090 [details]
Screen contents of kernel oops
Comment 2 acount closed by user 2003-02-28 23:47:51 EST
could be a hardware problem? 
does the system pass hardware test like memtes86 http://www.memtest86.org or
cpuburn http://users.ev1.net/~redelm ?
Comment 3 Greg Bailey 2003-03-24 13:04:37 EST
I did try memtest86 (which is at http://www.memtest86.com, not memtest86.org
BTW) and it did not return any memory errors.  Thanks for the suggestion!

I'm still running the 2.4.18-24 kernel on it--I haven't seen any indications
that the recent patches in the kernels would have anything to do with this
problem but I can always put the latest on it if need be.
Comment 4 Bugzilla owner 2004-09-30 11:40:31 EDT
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.