From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
B.Zolnierkiewicz@elka.pw.edu.pl
Subject: Re: 21rc6 serverworks IDE blows even more than is usual :)
Date: Thu, 29 May 2003 17:24:44 +0200 [thread overview]
Message-ID: <20030529152444.GL7217@louise.pinerecords.com> (raw)
In-Reply-To: <1054216894.20167.76.camel@dhcp22.swansea.linux.org.uk>
> [alan@lxorguk.ukuu.org.uk]
>
> On Iau, 2003-05-29 at 12:40, Tomas Szepe wrote:
> > o 2.4.21-rc6
> > intrerrupt timeouts, can't r/w from/to drive reliably in pio, dma hosed
> >
> > o 2.4.21-rc2-ac3
> > r/w in pio ok, dma hosed
> >
> > o 2.4.20
> > intrerrupt timeouts, can't r/w from/to drive reliably in pio, dma hosed
>
> The driver basically hasnt changed throughout these. Are you sure you
> don't just have a bust Proliant - anyone else runnign 2.4.21-rc on a
> proliant?
No, I can't be sure.
Basically I posted the report just in case somebody finds it useful,
for production use I'm sticking in an add-on cmd64x-based controller.
Thanks, Alan.
--
Tomas Szepe <szepe@pinerecords.com>
next prev parent reply other threads:[~2003-05-29 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 11:40 21rc6 serverworks IDE blows even more than is usual :) Tomas Szepe
2003-05-29 14:01 ` Alan Cox
2003-05-29 15:07 ` Marc-Christian Petersen
2003-05-29 15:16 ` Tomas Szepe
2003-05-29 15:24 ` Tomas Szepe [this message]
2003-05-29 15:53 ` Tomas Szepe
2003-05-29 16:57 ` kwijibo
2003-05-29 17:03 ` Tomas Szepe
2003-05-30 10:05 ` Alan Cox
2003-05-29 22:25 ` Duncan Laurie
2003-05-29 23:00 ` kwijibo
2003-05-30 7:17 ` Tomas Szepe
2003-05-30 10:11 ` Stephan von Krawczynski
2003-05-30 16:51 ` Duncan Laurie
2003-05-30 16:52 ` Tomas Szepe
2003-05-30 23:22 ` Stephan von Krawczynski
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=20030529152444.GL7217@louise.pinerecords.com \
--to=szepe@pinerecords.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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