Bug 60613 - kernel-2.4.9-31 (athlon) oops
kernel-2.4.9-31 (athlon) oops
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
7.2
athlon Linux
medium Severity medium
: ---
: ---
Assigned To: Stephen Tweedie
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-03-02 08:07 EST by Nils Philippsen
Modified: 2007-04-18 12:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-03-02 10:57:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
kernel oops message (1.10 KB, text/plain)
2002-03-02 08:08 EST, Nils Philippsen
no flags Details

  None (edit)
Description Nils Philippsen 2002-03-02 08:07:32 EST
Description of Problem:

kernel oopsed while installing some packages with RPM

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

2.4.9-31 (athlon)

How Reproducible:

hard to say

Steps to Reproduce:

generate I/O?!

Actual Results:

Oops

Expected Results:

No oops
Comment 1 Nils Philippsen 2002-03-02 08:08:36 EST
Created attachment 47200 [details]
kernel oops message
Comment 2 Stephen Tweedie 2002-03-02 10:57:21 EST
You've got corruption in the page->buffers ring for a page that happens to be in
use by ext3.  This is almost always a sign of bad memory, although it sometimes
indicates a device driver stomping on memory randomly.

I'd suggest running memtest86 overnight to see if that shows anything up. 
Otherwise, there's not much we can do with this report unless it's repeatable.
Comment 3 Nils Philippsen 2002-03-13 08:51:03 EST
Ran memtest and it shoed that one of my DIMMs hat three 1 bit errors cold and more
when heated up. I've changed it for a new one which passed memtest without
glitches, will report if this ever happens again (doubt it).

Note You need to log in before you can comment on or make changes to this bug.