From: Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>
To: Mikael Olenfalk <mikael@netgineers.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Alot of DMA errors in 2.4.18, 2.4.20 and 2.5.52
Date: Thu, 26 Dec 2002 13:37:10 +0100 [thread overview]
Message-ID: <20021226123710.GA2442@iapetus.localdomain> (raw)
In-Reply-To: <20021225115820.GB7348@louise.pinerecords.com>
On Wed, Dec 25, 2002 at 12:58:20PM +0100, Tomas Szepe wrote:
> > For some funny reason, a 2.4.20 kernel refuses to set the DMA-level on
> > the new disks (all connected to a UDMA5-capable Ultra100 TX2 controller)
> > to UDMA5,4,3 and settles it for UDMA2, which is the highest possibility
> > for the OLD onboard-controller (but NOT for the promise card).
>
> You need to boot 2.4.19 and 2.4.20 with 'ideX=ata66' where X is the
> number of the channel where you wish to use transfer modes above UDMA2.
> For instance, "ide0=ata66 ide1=ata66" will do the trick for the first two
hdparm -X69 /dev/hda will put it into UDMA5/ata100 mode as well
(69 == 64 + UDMA mode). No need to specify it at boot time.
(this discussion reminded me of my own TX2 adapter and 100GB disk:
adjusting its setting improved sequential disk reads: now 36MB/sec
instead of 24MB/sec)
--
Frank
next prev parent reply other threads:[~2002-12-26 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 11:19 Alot of DMA errors in 2.4.18, 2.4.20 and 2.5.52 Mikael Olenfalk
2002-12-25 11:58 ` Tomas Szepe
2002-12-26 12:37 ` Frank van Maarseveen [this message]
2002-12-26 13:22 ` Tomas Szepe
2002-12-26 16:42 ` Frank van Maarseveen
2002-12-26 17:35 ` Tomas Szepe
2002-12-26 18:40 ` Frank van Maarseveen
2002-12-26 19:28 ` Frank van Maarseveen
2002-12-27 13:14 ` Mikael Olenfalk
2002-12-27 15:13 ` jw schultz
2002-12-27 22:38 ` Mikael Olenfalk
2002-12-28 0:45 ` Alan Cox
2002-12-28 14:31 ` Mikael Olenfalk
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=20021226123710.GA2442@iapetus.localdomain \
--to=f.vanmaarseveen@inter.nl.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael@netgineers.se \
/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