From: Alexander Sabourenkov <screwdriver@lxnt.info>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org, htejun@gmail.com, jeff@garzik.org,
jgarzik@pobox.com
Subject: Re: [PATCH-RFC] Promise SATA300 TX4
Date: Sat, 27 Oct 2007 19:32:25 +0400 [thread overview]
Message-ID: <47235A09.7090409@lxnt.info> (raw)
In-Reply-To: <200710271453.l9RErRj9020770@harpo.it.uu.se>
Hello.
> Interesting, but can you please give more background information?
> I.e., how did you determine the existence of this bug?
I was experiencing read/write errors, with data corruption.
Dmesgs and lspcis are at http://lxnt.info/linux/
I downloaded driver from the promise.com, put up 2.6.11 and compiled it.
It worked ok.
I then unsuccessfully tried to port the driver to 2.6.22.
While I failed, this gave me enough insights into ATA workings, that I
could read the CAM module that comes with the driver.
Looking through it I found the SG_COUNT_ASIC_BUG constant and
corresponding code. I decided to try and implement the workaround in
sata_promise.c - and this fixed the problem.
> And please cc: the sata_promise maintainer on sata_promise patches.
> (Hint: that's me)
Hmm. sata_promise.c says:
* Maintained by: Jeff Garzik <jgarzik@pobox.com>
> Meanwhile I'll check the Promise driver(s) to see if there's
> something about SG table formatting restrictions there.
Take a look at:
cam_ata.c:6190
cam_ata.c:6259
The fix is also conditioned on sg segment length == 0, which I did not
implement. Is this at all possible in libata ?
--
./lxnt
next prev parent reply other threads:[~2007-10-27 15:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 14:53 [PATCH-RFC] (was: Re: Sata Sil3512 bug?; Promise SATA300 TX4) Mikael Pettersson
2007-10-27 15:32 ` Alexander Sabourenkov [this message]
2007-10-28 8:29 ` [PATCH-RFC] Promise SATA300 TX4 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=47235A09.7090409@lxnt.info \
--to=screwdriver@lxnt.info \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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.