Bug 134747 - Kernel Oops: kernel BUG at mm/vmscan.c:670!
Summary: Kernel Oops: kernel BUG at mm/vmscan.c:670!
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: 2
Hardware: athlon
OS: Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2004-10-05 23:39 UTC by Adam Bowns
Modified: 2015-01-04 22:10 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-11-24 01:36:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Kernel oops and stack trace (5.95 KB, text/plain)
2004-10-05 23:42 UTC, Adam Bowns
no flags Details

Description Adam Bowns 2004-10-05 23:39:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Gecko/20040808 Firefox/0.9.3

Description of problem:
I left my system for a while, when I returned it had crashed and
required a reboot. I have attached the oops and trace as a separate
file. If I can provide you with anything else let me know.

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

How reproducible: Couldn't Reproduce

Additional info:

Kernel is stock apart from the following patches: -



these were essential to fix the memory leak and disk corruption when
burning audio cd's with the kernel.

Comment 1 Adam Bowns 2004-10-05 23:42:29 UTC
Created attachment 104815 [details]
Kernel oops and stack trace

Comment 2 Dave Jones 2004-11-20 20:20:43 UTC
please try the latest errata kernel. a large number of vm fixes are included.

Comment 3 Adam Bowns 2004-11-21 00:33:05 UTC
I've not managed to reproduce it since. So like you say, its probably
been fixed. If I come across it again, I will let you have the latest

Comment 4 Adam Bowns 2004-11-24 01:36:00 UTC
I *think* I've found the cause of this bug, the terminator has gone
missing from the end of my scsi cable (god knows how or where its
gone). So I would guess that this is the cause of the problem. If I
experience this again (with proper termination), I will reopen the bug.

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