linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Duff <jfduff@mtu.edu>
To: linux-kernel@vger.kernel.org
Cc: rjh@groucho.maths.monash.edu.au, barryn@pobox.com
Subject: Apollo Pro266 system freeze followup
Date: Tue, 28 Aug 2001 20:20:48 -0400 (EDT)	[thread overview]
Message-ID: <200108290020.f7T0Km901301@tamarack.cs.mtu.edu> (raw)

Hello,

I noticed a thread on this list about a month ago regarding complete system
freezes on machines using the VIA Apollo Pro266 chipset:

http://uwsg.iu.edu/hypermail/linux/kernel/0107.3/0514.html

I too have such a system: 
(Iwill DVD266-R, two 1GHz PIIIs, 512M of Crucial PC2100, 4 IBM 75GXP 30G 
hard drives each hanging off one of the onboard IDE channels, running 
software RAID-5, Plextor CDRW),
and have seen the same thing.  I first noticed the problem when I decided
to do a stress test involving two simultaneous linux kernel compiles, 
continuously doing make clean and then make bzImage.  This will freeze
the system every time after a few hours or so, guaranteed.

Then I tried compiling a 2.4.9 kernel without SMP support, and it has
been running two simultaneous linux kernel compiles continuously for
more than two days straight on my Iwill box.  I dunno if this is very
helpful in figuring out where the bug may lie in the chipset, but I
thought it might be of interest to others with Apollo Pro266 chipset
boxes, that at least they can run reliably (keeping my fingers crossed)
on just one cpu for now.

(I don't subscribe to the list, so please CC me on any follow-ups).

-John
jfduff@mtu.edu


             reply	other threads:[~2001-08-29  0:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-29  0:20 John Duff [this message]
     [not found] <no.id>
2001-08-31  3:31 ` Apollo Pro266 system freeze followup Barry K. Nathan

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=200108290020.f7T0Km901301@tamarack.cs.mtu.edu \
    --to=jfduff@mtu.edu \
    --cc=barryn@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjh@groucho.maths.monash.edu.au \
    /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;
as well as URLs for NNTP newsgroup(s).