This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours
Bug 85964 - kernel oops on Pentium3
kernel oops on Pentium3
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
9
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-11 11:33 EST by Dams
Modified: 2008-01-17 12:49 EST (History)
1 user (show)

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


Attachments (Terms of Use)
The dmesg output just before the reboot. (15.24 KB, text/plain)
2003-03-11 11:35 EST, Dams
no flags Details

  None (edit)
Description Dams 2003-03-11 11:33:51 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20030131

Description of problem:
When the "swapoff" command did a segmentation fault, i just type "dmesg" and saw
the kernel oops trace. I dont know if it happened before or because of the
swapoff. The uptime of the computer was about 8-9 days.

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

How reproducible:
Didn't try

Steps to Reproduce:
i really dont know how to reproduce this.

    

Additional info:

The machine was a clean phoebe3 installation was some packages from fedora.us
and freshrpms.net.
Comment 1 Dams 2003-03-11 11:35:09 EST
Created attachment 90555 [details]
The dmesg output just before the reboot.
Comment 2 Bugzilla owner 2004-09-30 11:40:38 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.