public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Marc" <linux-kernel@liquid-nexus.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sata_promise / libata defaulting to UDMA/33
Date: Fri, 4 Aug 2006 02:12:36 +0800	[thread overview]
Message-ID: <20060803180707.M8589@liquid-nexus.net> (raw)
In-Reply-To: <1154625289.23655.97.camel@localhost.localdomain>

On Thu, 03 Aug 2006 18:14:49 +0100, Alan Cox wrote
> 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.
> 
> -

Thank you. I've compiled and installed 2.6.18-rc3 and it now shows:

ata2: dev 0 configured for UDMA/100

Problem is the system locks up after a few minutes - not sure what's causing
that (no flashing keyboard LEDs so it's not a kernel panic). I'll try again
tomorrow - its very late here already!

Regards.

--

      reply	other threads:[~2006-08-03 18:12 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
2006-08-03 18:12   ` Marc [this message]

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=20060803180707.M8589@liquid-nexus.net \
    --to=linux-kernel@liquid-nexus.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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