public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: hmh@debian.org (Henrique de Moraes Holschuh)
To: Mark Cooke <mpc@star.sr.bham.ac.uk>
Cc: "David Härdeman" <david@2gen.com>,
	LinuxKernel <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.4.17 with VT8367 [KT266] crashes on heavy ide load togeter
Date: Mon, 1 Apr 2002 16:34:09 -0300	[thread overview]
Message-ID: <20020401163409.F22174@khazad-dum> (raw)
In-Reply-To: <3CA88BC0.2000603@2gen.com> <Pine.LNX.4.44.0204011810380.16203-300000@pc24.sr.bham.ac.uk>

On Mon, 01 Apr 2002, Mark Cooke wrote:
> On Mon, 1 Apr 2002, David Härdeman wrote:
> > Date: Mon, 01 Apr 2002 18:33:04 +0200
> > From: David Härdeman <david@2gen.com>
> > To: Mark Cooke <mpc@star.sr.bham.ac.uk>
> > Cc: LinuxKernel <linux-kernel@vger.kernel.org>
> > Subject: Re: Kernel 2.4.17 with VT8367 [KT266] crashes on heavy ide load
> >     togeter
> > 
> > Mark Cooke wrote:
> > > If I run a simultaneous one on hdc and hde, the combined rate tops 
> > > out at 50MB again.  Hence, the limitation isn't the raid card.  Or at 
> > > least I'd be exceedingly surprised.
> > 
> > The bugs that exist in VIA chipsets and Barracuda drives have already 
> > exceedingly surprised me many, many times :-)

Yes. For the VIA side, I have this in my rc.S stuff:

#!/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr/bin
export PATH

echo -n "Optimizing hardware configuration: "

if command -v setpci >/dev/null 2>&1; then
    echo -n "PCI"
    #
    # Optimize PCI latency for IDE controllers
    #
    setpci -d 1106:0571 latency_timer=60  >/dev/null 2>&1
    setpci -d 105a:*	latency_timer=60  >/dev/null 2>&1
    echo "."
else
    echo '(lspci/setpci not available!)'
fi

Normal latency set by the BIOS is 32, which is too damn small for IDE.

You may have to tweak the PCI ids a bit. You want all storage controllers
(both chipset, Promise and any extra cards). The IDs up there are for my VIA
kt133, and Promise PDC20265.

Oh, some of the PCI 'optimizations' in BIOS must be enabled for that to
actually help a bit. Stuff like the PCI caches.

VIA PCI is utter crap. I am not buying anything of theirs ever again :(

-- 
  "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

  reply	other threads:[~2002-04-01 19:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0203301850410.24920-100000@pc24.sr.bham.ac.uk>
2002-04-01 16:33 ` Kernel 2.4.17 with VT8367 [KT266] crashes on heavy ide load togeter David Härdeman
2002-04-01 17:32   ` Mark Cooke
2002-04-01 19:34     ` Henrique de Moraes Holschuh [this message]
2002-03-30  1:12 Dieter Nützel
2002-03-30 13:22 ` David Härdeman

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=20020401163409.F22174@khazad-dum \
    --to=hmh@debian.org \
    --cc=david@2gen.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mpc@star.sr.bham.ac.uk \
    /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