From: Brad Campbell <brad@wasp.net.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Dave <dave.jiang@gmail.com>,
linux-ide@vger.kernel.org,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: max_sectors in libata when using md
Date: Thu, 26 Aug 2004 20:44:11 +0400 [thread overview]
Message-ID: <412E135B.1030605@wasp.net.au> (raw)
In-Reply-To: <412E1039.7030508@pobox.com>
Jeff Garzik wrote:
> Dave wrote:
>
>> I believe. I wish the SATA layer would allow a mechanism to auto
>> detect drive being LBA48 or LBA28 and adjust accordingly instead of
>> just default to a very low sector count.
>
>
>
> The SATA layer already does this... but only on 2.6.x kernels.
>
> drivers/scsi/libata-scsi.c, ata_scsi_slave_config()
>
(Groan) <Places head in hands weeping>
I give up Batman.
In which case, these drives need to be knocked back to UDMA66 to function properly on anything later
than 2.6.6. Don't know why.
I have tried multiple drives (I have 5 of them), multiple cables (lots of those) and multiple bridge
boards (I have 6 of those). There is no combination that is reliable on the VIA controller with any
transfer larger than about 0x80 sectors *OR* speeds greater than UDMA66 *OR* Kernel 2.6.6 or prior.
Regards,
Brad
next prev parent reply other threads:[~2004-08-26 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 15:20 max_sectors in libata when using md Brad Campbell
2004-08-26 15:52 ` Dave
2004-08-26 16:30 ` Jeff Garzik
2004-08-26 16:44 ` Brad Campbell [this message]
2004-08-26 17:26 ` Jeff Garzik
2004-08-26 17:34 ` Dave
2004-08-26 17:44 ` Jeff Garzik
2004-08-26 17:50 ` Brad Campbell
2004-08-26 17:54 ` Jeff Garzik
2004-08-26 18:34 ` Brad Campbell
2004-08-26 17:37 ` Brad Campbell
2004-08-26 16:37 ` Brad Campbell
2004-08-26 17:51 ` Jeff Garzik
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=412E135B.1030605@wasp.net.au \
--to=brad@wasp.net.au \
--cc=dave.jiang@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@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).