Bug 86214 - System frezees at least once a day regardless of work it performs
System frezees at least once a day regardless of work it performs
Status: CLOSED WORKSFORME
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
8.0
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-17 05:53 EST by AMur
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-03-26 07:13:52 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description AMur 2003-03-17 05:53:35 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
I'm running RedHat 8.0 with kernel 2.4.18-14 on Dell Precision 450 workstation.
Hardware installed: 2xPentium 4 Xeon 2.8 GHz proccessors, 2.0G SDRAM, 2x 100G
HDD (Western Digital WD1200JB-75CRA0) and 82545EM Gigabit Network controller.
I've recompiled the kernel with only the following changes from standart SMP
configuration: added NTFS support, removed PCMCIA stuff. The system keeps
freezing, at least once a day with no pattern visible - sometimes as I type,
sometimes when running heavy calculations, sometimes even when only activity is
screensaver. After reading the forums I've found that driver for Gigabit nic may
be responsible for freeze. I obtained latest (4.4-12) driver from Intel and
compiled it, with no change to the problem.

Version-Release number of selected component (if applicable):
kernel-2.4.18-14smp

How reproducible:
Always

Steps to Reproduce:
1. Boot the system, wait for couple of hours
.
    

Actual Results:  System freezes -- no response to mouse, keyboard, network, etc.

Expected Results:  Working system

Additional info:
Comment 1 Arjan van de Ven 2003-03-17 05:55:44 EST
can you paste the output of lsmod ?
also can you try adding "nmi_watchdog=1" to the vmlinuz line in  the
/boot/grub/grub.conf file, this will enable a kernel deadlock detector.

note: you kernel is quite a few security and bugfix errata behind 
Comment 2 AMur 2003-03-26 07:13:52 EST
Issue resolved by upgrading to kernel-2.14.18-27smp 

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