Bug 109006 - Latest RH 2.4.20 kernels crash on my Dell PE2650 under havy disk io
Summary: Latest RH 2.4.20 kernels crash on my Dell PE2650 under havy disk io
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 9
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-11-04 08:14 UTC by Rene Kapeller
Modified: 2007-04-18 16:59 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2004-09-30 15:41:41 UTC


Attachments (Terms of Use)

Description Rene Kapeller 2003-11-04 08:14:16 UTC
Description of problem:
RH kernels 2.4.20-20.9smp and 2.4.20-19.9smp crash (kernel trace) on
my Dell PE2650 after 1-3 hours while doing havy disk io.
RH kernel 2.4.20-8smp and 2.4.20-18.9smp do not have this problem! 


Version-Release number of selected component (if applicable):
Redhat-9.0 + glibc-2.3.2-27.9


How reproducible:
After testing for more than 10 days, I confirm 100% reproducibility.

Steps to Reproduce:
1. while 1; do dd if=/dev/zero of=big10 bs=1M count=10; done
2. wait ~1-3 hours
3.
  
Actual results:
kernel trace on console, but no log file entry!


Expected results:


Additional info:
- The PE2650 has 2 x 2.4 GHz Xeon 
- Hyperthreading on/off does not influence the mentioned effect.
- Booting with 'noapic' still crashes system
- Using latest bcm5700 instead of tg3 makes not difference
- Doing disk io on local disk (PERC) or external FC disk makes no
difference.

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