All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Domke <tmbinc@elitedvb.net>
To: linux-kernel@vger.kernel.org
Subject: IDE 48 bit addressing causes data corruption
Date: Tue, 18 Mar 2003 15:30:57 +0100	[thread overview]
Message-ID: <3E772DA1.5080504@elitedvb.net> (raw)

Hi,

i'm having linuxppc-embedded based system (2.4.21-pre, but 2.4.20 shows 
same results) with a normal ATAPI-5-styled IDE controller.

When using a 200GB Maxtor HDD, there are strange effects. When writing 
just the sector number to every sector (or every 100MB is enough), and 
reading back, data from incorrect sectors is read. The upper 24bit of 
the LBA seem to be invalid, shows like the upper 24bit aren't updated in 
the 2 cycle LBA-write in the ide-disk.c. For example, reading from 
0x946000000 (LBA 0x4A30000) will read from 0x2f46000000 (LBA 0x17A30000).
note that i lineary fill the disk, and 0x17xxxxxx is the highest 
possible LBA, so the last upper bit from the write won't be actualized 
any more when reading back from lower addresses.

However, reading them back (using the HOB-bit) will work and give 
correct results. I don't really know whats going wrong, except that 
there are addressing-faults.

Is this a known bug of the Maxtor 6Y200L maybe? the 160GB version showed 
the same effect.

Is it possible that the IDE-Controller causes the fault? normal 28bit 
HDDs work just fine.


Can somebody please confirm again that i don't need an atapi-6 (ATA133) 
controller to use LBA48 ?

Regulary some people are stating this, and regulary some people tell 
that these people are wrong.


felix



             reply	other threads:[~2003-03-18 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-18 14:30 Felix Domke [this message]
2003-03-18 16:24 ` IDE 48 bit addressing causes data corruption Alan Cox
2003-03-18 18:20   ` Felix Domke
2003-03-18 19:37     ` Alan Cox

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=3E772DA1.5080504@elitedvb.net \
    --to=tmbinc@elitedvb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.