Bug 98943 - kernel BUG dump in messages file, during heavy disk I/O
Summary: kernel BUG dump in messages file, during heavy disk I/O
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-07-10 17:44 UTC by zic
Modified: 2007-04-18 16:55 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2004-09-30 15:41:17 UTC
Embargoed:


Attachments (Terms of Use)
/var/log/messages (13.12 KB, text/plain)
2003-07-10 17:46 UTC, zic
no flags Details

Description zic 2003-07-10 17:44:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624

Description of problem:
using the kernel-2.4.20-18.9 i686, memory 1.5GB, Pentium4
hda, hdb are IDE
reiserfs is consists of LVM partitions.

about 10s of reiserfs mounted using autofs,
3 of smbfs mounted manually, 2 of them are local mount(//localhost/SHARE),

using disk write to automounted reiserfs via VMWare
and at the same time, to smbfs(local one),

suddenly those errors occured.

(I typed Ctrl-SysReq-S, U, B, after that)

so far, it happened just this once, that I cannot/do not want to reproduce it.


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


How reproducible:
Didn't try


Additional info:

see attached file(messages file)

N.B.
I used the smbfs locally because I just wanted filename case insensitive filesystem.

Comment 1 zic 2003-07-10 17:46:55 UTC
Created attachment 92864 [details]
/var/log/messages

I first thought HDD broken, but it was not.
I checked hdb using smartctl, but it says the disk is OK.
there are no relocated sectors.

Comment 2 Bugzilla owner 2004-09-30 15:41:17 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
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.