mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: hmh@debian.org (Henrique de Moraes Holschuh)
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: linux-kernel@vger.kernel.org, Jani Forssell <jani.forssell@viasys.com>
Subject: Re: Via KT133 pci corruption: stock 2.4.18pre2 oopses as well
Date: Thu, 10 Jan 2002 10:01:02 -0200	[thread overview]
Message-ID: <20020110100101.A25366@khazad-dum> (raw)
In-Reply-To: <20020109235722.L1200@niksula.cs.hut.fi> <Pine.LNX.4.21.0201100025440.14057-100000@tux.rsn.bth.se>
In-Reply-To: <Pine.LNX.4.21.0201100025440.14057-100000@tux.rsn.bth.se>; from gandalf@wlug.westbo.se on Thu, Jan 10, 2002 at 12:30:37AM +0100

On Thu, 10 Jan 2002, Martin Josefsson wrote:
> We've replaved that memory module now and now it's better but I have to
> say that the KT133 or atleast the Asus A7V motherboard seems to be quite
> broken. we have a lot of spurious irq's and the ide controllers freak when
> but under some load and start getting irq timeouts and resets the ide
> channels over and over again with some delay in between when it kind of
> works, slow as hell but works.

Well, my A7V is also acting up, with spurious IRQs (but not too many), and
PCI lockups if the load on the PCI bus increases too much -- this is
probably the last time I ever buy a VIA board (because they take soooo much
time to acknowledge their screw ups and help people fix it) unless they
start issuing non-binary-only fixes (heck, all it takes is a doc telling us
what to do on the PCI registers!).

The IDE corruption and lockups you can fix, just apply the latest IDE
patches, the 2.4.18pre IDE subsystem is not to be used on a KT133, it will
not work at all if you give it a slightly bigger load on the promise
controller, for example.

> We are going to replace the motherboard with one with VIA KT266A chipset,
> hope that works better.

Without the IDE patches, it will (most probably) not help.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

  parent reply	other threads:[~2002-01-10 12:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-08 19:58 2.2.21pre2 oops Ville Herva
2002-01-08 20:16 ` Alan Cox
2002-01-08 20:13   ` Ville Herva
2002-01-09 12:45     ` Ville Herva
2002-01-09 15:26       ` Via KT133 pci corruption: stock 2.4.18pre2 oopses as well Ville Herva
2002-01-09 21:00         ` Andrew Morton
2002-01-09 21:57           ` Ville Herva
2002-01-09 23:30             ` Martin Josefsson
2002-01-10  0:19               ` Daniel J Blueman
2002-01-10  0:41                 ` Martin Josefsson
2002-01-10  1:04                   ` Daniel J Blueman
2002-01-10  5:34               ` Ville Herva
2002-01-10 12:01               ` Henrique de Moraes Holschuh [this message]
2002-01-10 12:56                 ` Martin Josefsson
2002-01-10 13:37                 ` Ville Herva
2002-01-09 23:33             ` Daniel J Blueman
2002-01-10  6:34           ` Ville Herva
2002-01-10  6:40             ` Andrew Morton

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=20020110100101.A25366@khazad-dum \
    --to=hmh@debian.org \
    --cc=gandalf@wlug.westbo.se \
    --cc=jani.forssell@viasys.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

Powered by JetHome