public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jure Pecar <pegasus@telemach.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.0 hangs with PIII i815e system
Date: Wed, 24 Jan 2001 22:58:28 +0100	[thread overview]
Message-ID: <3A6F5004.D8954FA4@telemach.net> (raw)



> Recently, i got a new and shiny PIII 700Mhz, 64MB box, with Intel 
> motherboard based on the i815e chipset, with intergrated 
> NIC/Audio/Graphic. 

> The machine ran smoothly with the supplied 2.2.16 kernel, yet i decided 
> to upgrade to 2.4.0. 

> But since upgrading to 2.4.0, i have random, unexpected lock-ups, and that 
> means TOTAL lock-up, no console switching, no SysRQ key, nothing responds. 

> I first tried removing all of the(probably troublemaking) i81x features, 
> ICH2 audio driver, DRI and AGP were all moved out of the kernel, yet 
> lockups still occour. 

> If i can point at a common cause, all these lock-ups except one occoured 
> while downloading something, and in all cases squid 2.2. was running. 

> I include the kernel config file, and kernel bootup messages,hopefully, it 
> will help debugging the problem 

I can only confirm that strange things are happening indeed with intel's
D815EEA board and 2.4.0 kernels. I have 15 such boxen (and lot more to
come next month), all with exact same configuration, yet 10 of these are
working ok, of other 5 one cant even reach a couple of hours of uptime,
other four managed 2 days uptime so far. They all have installed redhat7
with their rawhide 2.4.0-0.43 kernel rpm. So far all 15 boxen stand
idle, i just ping them from time to time to check if they're still up.
I really _really_ hope this is a hardware problem. One weird thing i
came up with is that all boxen that were crashing have noticeably warmer
cpu heatsinks that those which dont crash, yet all fans were spinning as
they should. So could this be something in the kernel? There are
absolutely no mesgs ni logs indicating that something is wrong... 

All suggestions welcome.

--

Jure Pecar
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2001-01-24 21:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24 21:58 Jure Pecar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-23 22:54 2.4.0 hangs with PIII i815e system Idan Sofer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3A6F5004.D8954FA4@telemach.net \
    --to=pegasus@telemach.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox