From: Jeff Garzik <jgarzik@pobox.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andries Brouwer <aebr@win.tue.nl>,
Andre Hedrick <andre@linux-ide.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Lionel Bergeret <lbergeret@swing.be>,
JunHyeok Heo <jhheo@idis.co.kr>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] Bogus LBA48 drives
Date: Thu, 01 Apr 2004 13:24:11 -0500 [thread overview]
Message-ID: <406C5E4B.4020505@pobox.com> (raw)
In-Reply-To: <Pine.GSO.4.58.0404010933190.12148@waterleaf.sonytel.be>
Geert Uytterhoeven wrote:
> On Wed, 31 Mar 2004, Jeff Garzik wrote:
>
>>Andries Brouwer wrote:
>>
>>>Hmm. I read in my copy of ATA7:
>>>
>>> 6.16.55 Words (103:100): Maximum user LBA for 48-bit Address feature set
>>> Words (103:100) contain a value that is one greater than the maximum LBA
>>> in user accessable space when the 48-bit Addressing feature set is supported.
>>> The maximum value that shall be placed in this field is 0000FFFFFFFFFFFFh.
>>> Support of these words is mandatory if the 48-bit Address feature set is supported.
>>>
>>>Do you read differently?
>>
>>The errata is, one needs to check that field for zero, and use the other
>>one if so...
>
>
> Which is not sufficient for `my' drives, since I get disk errors if I just use
> the other capacity field and don't disable LBA48 completely.
>
> I'll check the ATA specs myself, if I find some time...
If it's reporting the "48-bit feature set supported" but doesn't really
support it, I'd vote for broken drive :) Maybe check for a firmware
update on the manufacturer's web site?
Jeff
prev parent reply other threads:[~2004-04-01 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-30 15:22 [PATCH] Bogus LBA48 drives Geert Uytterhoeven
2004-03-30 15:26 ` Geert Uytterhoeven
2004-03-30 15:28 ` Geert Uytterhoeven
2004-03-30 15:51 ` Bartlomiej Zolnierkiewicz
2004-03-30 16:38 ` Andre Hedrick
2004-03-30 16:50 ` Jeff Garzik
2004-03-31 18:34 ` Andries Brouwer
2004-03-31 18:58 ` Jeff Garzik
2004-04-01 9:06 ` Geert Uytterhoeven
2004-04-01 18:24 ` Jeff Garzik [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=406C5E4B.4020505@pobox.com \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=aebr@win.tue.nl \
--cc=andre@linux-ide.org \
--cc=geert@linux-m68k.org \
--cc=jhheo@idis.co.kr \
--cc=lbergeret@swing.be \
--cc=linux-ide@vger.kernel.org \
--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