From: Tomas Szepe <szepe@pinerecords.com>
To: Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>
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 18:35:28 +0100 [thread overview]
Message-ID: <20021226173528.GF7348@louise.pinerecords.com> (raw)
In-Reply-To: <20021226164229.GA26413@iapetus.localdomain>
> On Thu, Dec 26, 2002 at 02:22:28PM +0100, Tomas Szepe wrote:
> > >
> > > 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.
> >
> > Not true. You definitely need to use the ideX boot param AND
> > run hdparm -X?? /dev/hd? to make use of UDMA3+ on newer PDC
> > controllers (unless you apply the patch posted on Dec 24 by
> > Nikolai Zhubr).
>
> Driver says otherwise on RH8.0 + 2.4.20:
> iapetus /proc/ide# cat pdc202xx
>
> PROMISE Ultra series driver Ver 1.20.0.7 2002-05-23 Adapter: Ultra100 TX2
> --------------- Primary Channel ---------------- Secondary Channel -------------
> enabled enabled
> 66 Clocking enabled enabled
> Mode MASTER MASTER
> --------------- drive0 --------- drive1 -------- drive0 ---------- drive1 ------
> DMA enabled: yes no no no
> UDMA Mode: 5 0 0 0
> PIO Mode: 4 0 0 0
Fair enough. Can you give me your PCI ids, Promise BIOS version
and "hdparm -Iv /dev/hda"?
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2002-12-26 17:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 11:19 Mikael Olenfalk
2002-12-25 11:58 ` Tomas Szepe
2002-12-26 12:37 ` Frank van Maarseveen
2002-12-26 13:22 ` Tomas Szepe
2002-12-26 16:42 ` Frank van Maarseveen
2002-12-26 17:35 ` Tomas Szepe [this message]
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=20021226173528.GF7348@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=F.vanMaarseveen@inter.NL.net \
--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