From: David Greaves <lkml@dgreaves.com>
To: linux-ide@vger.kernel.org
Subject: Re: Promise Ultra100TX2 PDC20286 broken in 2.6.0-test9
Date: Wed, 26 Nov 2003 22:50:09 +0000 [thread overview]
Message-ID: <3FC52E21.6020605@dgreaves.com> (raw)
In-Reply-To: <3FAD5145.5040603@dgreaves.com>
Hi Bart
I've downloaded (but not yet tried) -test10 but as you said elsewhere,
there are no patches that seem to touch the area I had a problem with.
Do you think my problem is likely to be touched by -test11?
Are there any other patches you'd like me to try?
BTW this list is now on
http://marc.theaimsgroup.com/?l=linux-ide&r=1&w=2
Hank says
>I don't think vger keeps copies of older messages, but if you know of
>anywhere I can find 'em I'd be happy to bulk-add them to our archives.
>
I figured you may have them/some?
David
David Greaves wrote:
> Summary:
> PDC20286 fails horribly with 2 UDMA drives on its primary channel
> If I move one drive to the second channel it seems OK.
>
>
> I have compiled with and without "DMA on by default".
> I've also used the autotune options (and ata66)
> I looked for the most conservative config I could find before posting
> (well, I thought I did) :)
>
> ok...
> I tried again with:
> * DMA on by default (IDEDMA_PCI_AUTO) (done a partial config dump
> later...)
> * removed noapic and used both autotune options (not tried before)
> kernel /vmlinuz-2.6.0-test9 ro root=/dev/hdc3 ide2=autotune
> ide3=autotune single
>
> Result:
> same problem
next prev parent reply other threads:[~2003-11-26 22:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-08 20:25 Promise Ultra100TX2 PDC20286 broken in 2.6.0-test9 David Greaves
2003-11-26 22:50 ` David Greaves [this message]
[not found] <3FAD1F1C.2030405@dgreaves.com>
2003-11-08 17:18 ` Bartlomiej Zolnierkiewicz
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=3FC52E21.6020605@dgreaves.com \
--to=lkml@dgreaves.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).