mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bobby D. Bryant" <bdbryant@mail.utexas.edu>
To: linux-kernel@vger.kernel.org
Cc: Dennis Bjorklund <db@zigo.dhs.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: PROBLEM: Slowdown for ATA/100 drive on PCI card, after 2.4.3upgrade.
Date: Tue, 17 Apr 2001 07:41:36 -0500	[thread overview]
Message-ID: <3ADC3A00.A9954E08@mail.utexas.edu> (raw)
In-Reply-To: <Pine.LNX.4.30.0104171408050.20942-100000@zigo.dhs.org>

Dennis Bjorklund wrote:

> On Tue, 17 Apr 2001, Alan Cox wrote:
>
> > try and avoid a hardware problem. VIA have finally released an 'official'
> > fix which seems to be a lot less damaging to performance on the whole. That
> > I hope will be in 2.4.4
>
> What is this official fix? I've only seen unofficial ones (like the one in
> your ac7, or was it ac6). What are the implications of the fix
> (compabilitywise and speedwise)?
>
> I looked on via's homepage but could not find anything about this fix.
> I've very interested since I have a new mobo unopened in a box that I can
> still return and choose something with another chipset.

Notice that with 2.4.3 it *only* affects the disk on the PCI controller card; a
similar ATA/100 disk on the motherboard's controller did not experience the
slowdown.

Also, FYI, I noticed the mention of VIA fixes in the -ac7 change list, but those
changes did not cause or fix this particular problem.  The problem occurs in all
the 2.4.3's that I've tried: -ac5, -ac6, -ac7.

BTW, It's not hurting me right now, because the disk on the PCI card hasn't been
put to work yet.  I just want to make sure you guys are aware of it.

Bobby Bryant
Austin, Texas



      reply	other threads:[~2001-04-17 12:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-16 13:14 PROBLEM: Slowdown for ATA/100 drive on PCI card, after 2.4.3 upgrade Bobby D. Bryant
2001-04-17 11:33 ` Alan Cox
2001-04-17 12:13   ` Dennis Bjorklund
2001-04-17 12:41     ` Bobby D. Bryant [this message]

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=3ADC3A00.A9954E08@mail.utexas.edu \
    --to=bdbryant@mail.utexas.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=db@zigo.dhs.org \
    --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®