public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Bruce Harada <bruce@ask.ne.jp>, linux-kernel@vger.kernel.org
Subject: Re: Locked up 2.4.10-pre11 on Tyan 815t motherboard.
Date: Wed, 19 Sep 2001 12:53:31 -0700	[thread overview]
Message-ID: <3BA8F7BB.273734EA@candelatech.com> (raw)
In-Reply-To: <E15jmpB-0003Zn-00@the-village.bc.nu>

Alan Cox wrote:
> 
> > Doubtful. Since it's an 815, I presume you're running a PIII (correct me if
> > I'm wrong) - newish PIIIs have reasonable overheating cutout features, and
> > if overheating had damaged the CPU, I'd be very surprised if it worked at
> > all, rather than just locking up on certain sizes of network packets.
> 
> The 815 chipsets have known (and documented) problems with out of spec
> memory signals. Board vendors are supposed to have used workarounds but I
> have so far sent back 2 out of the 3 A/Open i815 boards with problems where
> they locked up occasionally under high load (in any OS) and also failed
> memtest86 (with known good tested ram) when placed in an electrically noisy
> environment.
> 
> I've seen lockups on high network load as part of that - but not packet size
> dependant ones.

Damn..someone has to make good stable motherboards...anyone got any
suggestions for one that will fit into a 1U server, with built-in
Video and preferably a NIC?  I had ok luck with an Intel board based
on the 815 chipset, so long as I used the e100 driver...maybe I'll
have to go back to it...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

  reply	other threads:[~2001-09-19 19:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-19  6:51 Locked up 2.4.10-pre11 on Tyan 815t motherboard Ben Greear
2001-09-19  7:10 ` Ben Greear
     [not found] ` <3BA8CCF1.CA2933B3@zip.com.au>
     [not found]   ` <3BA8D351.F57BE70D@candelatech.com>
     [not found]     ` <3BA8D619.9A607219@zip.com.au>
2001-09-19 18:09       ` Ben Greear
2001-09-19 18:38         ` Bruce Harada
2001-09-19 19:15           ` Alan Cox
2001-09-19 19:53             ` Ben Greear [this message]
2001-09-19 20:03               ` Jeff Garzik
2001-09-19 20:05               ` Alan Cox
2001-09-19 20:40                 ` Locked up 2.4.10-pre11 on Tyan 815t motherboard. [EEPRO-100 bugs] Ben Greear
2001-09-19 21:57                   ` Alan Cox
2001-09-20 19:28             ` Locked up 2.4.10-pre11 on Tyan 815t motherboard Martin Josefsson
2001-09-19 19:46           ` Ben Greear
2001-09-24 15:14         ` bill davidsen
2001-09-24 18:18           ` Ben Greear

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=3BA8F7BB.273734EA@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bruce@ask.ne.jp \
    --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