mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Charlie Wilkinson <cwilkins@boinklabs.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Hard lock-ups on RH7.2 install - Via Chipset?
Date: Thu, 21 Feb 2002 13:02:40 -0500	[thread overview]
Message-ID: <20020221130240.B12456@boink.boinklabs.com> (raw)
In-Reply-To: <20020221105756.A9728@boink.boinklabs.com> <E16dw9r-0007R1-00@the-village.bc.nu>
In-Reply-To: <E16dw9r-0007R1-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Thu, Feb 21, 2002 at 04:33:23PM +0000

On Thu, Feb 21, 2002 at 04:33:23PM +0000, Alan Cox waxed eloquent:
> 
> > I can confirm that it still locks up.  :/  What can I do to help?
> 
> I'm assuming its a hardware issue. It works on non VIA for multiple people
> it fails on VIA for multiple people

yeah, appears to be specific to the KT133 (not 233), as Mark indicated.
If I recall I've seen reports that this has happened with the KT133A
as well, though I wonder if they are all related specifically to PCI
load, or might it be the old Athlon optimization problem in some cases?
(That was a seperate and distinct issue, generally unrelated to this
problem, yes?)

And then there was something about incorrect chipset register settings
from the BIOS...

I'm getting confused....  8-o

One thing I noticed - and it may mean nothing - but I noticed that
during my load tests the drive access lights were not always on solid,
that the lights went out for all drives for a small fraction of a second
occasionally.  (concurrent dd's from /dev/zero to each drive.)  I was
wondering if this might possibly work back to some kind of timeout issue.
And more importantly, is it possible to crank up debugging messages in
the kernel and watch for that sort of thing.  Is there any point?

Thanks for any tips.

-cw-

  reply	other threads:[~2002-02-21 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-12 15:56 Charlie Wilkinson
     [not found] ` <E16agiR-0002Sv-00@the-village.bc.nu>
2002-02-21 15:57   ` Charlie Wilkinson
2002-02-21 16:33     ` Alan Cox
2002-02-21 18:02       ` Charlie Wilkinson [this message]
2002-04-18 20:29       ` Charlie Wilkinson
     [not found] <20020221110156.B9728@boink.boinklabs.com>
     [not found] ` <Pine.LNX.4.33.0202211106340.16271-100000@coffee.psychology.mcmaster.ca>
2002-02-21 17:49   ` Charlie Wilkinson
2002-02-22 20:21 Michael B Allen

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=20020221130240.B12456@boink.boinklabs.com \
    --to=cwilkins@boinklabs.com \
    --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

all inboxes | Powered by JetHome®