From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Marc <linux-kernel@liquid-nexus.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_promise / libata defaulting to UDMA/33
Date: Thu, 03 Aug 2006 18:14:49 +0100 [thread overview]
Message-ID: <1154625289.23655.97.camel@localhost.localdomain> (raw)
In-Reply-To: <20060803163002.M27080@liquid-nexus.net>
Ar Gwe, 2006-08-04 am 00:31 +0800, ysgrifennodd Marc:
> Hi.
>
> I'm having great difficulty solving a problem I've encountered. I have a
> Promise Fastrak TX4000 card:
We knock things down to UDMA33 if they are on an unsuitable cable. The
rest of the displayed data looks correct.
> ata2: PATA max UDMA/133 cmd 0xF8ABC280 ctl 0xF8ABC2B8 bmdma 0x0 irq 137
Controller does 133
> ata2: dev 0 cfg 49:2f00 82:346b 83:7f01 84:4003 85:3469 86:3c01 87:4003 88:203f
> ata2: dev 0 ATA-6, max UDMA/100, 312581808 sectors: LBA48
Devices does UDMA 100
> <b>ata2: dev 0 configured for UDMA/33</b>
So this appears to be a cable confusion. One thing that was fixed in
recent patches was a bug where if the core code decided something was
PATA but the drive setup was in fact SATA it incorrectly clipped to
UDMA33.
> I'm currently running kernel 2.6.17.3. In the controller's BIOS I've created 3
> 'stripe' arrays with 1 disk per array, the BIOS shows the 3 drives as U5 (UDMA
> mode 5 - which is UDMA/100 right?).
Correct
> I've searched high and low but haven't found an answer to this problem. Help
> appreciated. Please - I'm getting dismal performance.
I think the needed patch is in 2.6.18-mm, not sure about 2.6.18-rc base.
Jeff Garzik would be able to verify what has it merged.
next prev parent reply other threads:[~2006-08-03 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 16:31 sata_promise / libata defaulting to UDMA/33 Marc
2006-08-03 17:14 ` Alan Cox [this message]
2006-08-03 18:12 ` Marc
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=1154625289.23655.97.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@liquid-nexus.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