Bug 82774

Summary: paging request oops under high I/O activity
Product: [Retired] Red Hat Linux Reporter: Mark Henson <mark>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-30 15:40:27 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
syslog kernel messages none

Description Mark Henson 2003-01-26 06:59:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

Description of problem:
Two oops:

1: copying cd using xcdroast to hard disk (hda) see attached file for detail. 
copy failed at 180MB/625MB

2: oops: copying nfs to another machine over LAN, the copy completed but when
attempting ls on remote dir:

cd read to iso files was being done around the same time. second oops could have
occured during cd read, but cd read completed ok only the ls failed.

the machine locked up straight away...  any disk access resulting in hung session.

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

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
1. see description

Actual Results:  machine froze - reset required

Expected Results:  task: copying cd image to HD should have completed normally,
2nd task should have provided ls of nfs directory

Additional info:

will attempt to recreate, the machine (hw) has recently been upgraded from RH7.3
which had no such issue with similar tasks.

Comment 1 Mark Henson 2003-01-26 07:00:31 UTC
Created attachment 89605 [details]
syslog kernel messages

Comment 2 Arjan van de Ven 2003-01-26 10:58:44 UTC
this looks like bad memory corruption.
What filesystem are you using?

Comment 3 Mark Henson 2003-01-26 12:02:33 UTC
a mixture of ext3/reiserfs and nfs.

[mark@skink mark]$ mount
/dev/hda1 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda3 on /boot type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda8 on /home type reiserfs (rw)
none on /dev/shm type tmpfs (rw)
/dev/hda6 on /tmp type ext3 (rw)
/dev/hda5 on /usr type ext3 (rw)
/dev/hda7 on /var type ext3 (rw)
sala:/home on /net type nfs (rw,addr=
[mark@skink mark]$

Comment 4 Arjan van de Ven 2003-01-26 12:16:15 UTC
it might be a good plan to run memtest86 to test the ram;
also does this happen if you don't use reiserfs?

Comment 5 Mark Henson 2003-01-26 19:46:46 UTC
ran memtest86 for 8 passes - clean
have not been able to recreate so far - (writing to reiserfs partition) and have
not tried when writing to ext2/3

Comment 6 Bugzilla owner 2004-09-30 15:40:27 UTC
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

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/