From: Mark Lord <liml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: Harri Olin <harri.olin@gmail.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Brian Rademacher <rad@radfiles.net>,
Eamonn Hamilton <EAMONN.HAMILTON@saic.com>
Subject: Re: sata_mv: trial fix for lost NCQ interrupts
Date: Wed, 14 Jan 2009 17:08:25 -0500 [thread overview]
Message-ID: <496E6259.3000502@rtr.ca> (raw)
In-Reply-To: <496E589E.7090909@garzik.org>
Jeff Garzik wrote:
> Harri Olin wrote:
>> I still see timeouts only on 4 lower ports where disk has also been
>> connected to port +4. i.e. if port 7 is empty, port 3 will work just
>> fine. I just would like to see some confirmation that others are
>> seeing this same kind of behavior.
>
>
> hmmmm, that is quite interesting. That seems to indicate something
> related to the dual-HC mechanism (8-port cards are really two 4-port
> chips internally)...
..
Yup. As I just noted on the redhat bugzilla entry,
this bug only bites when drives are attached to *both*
the lower and upper halves of the chip.
The second patch fixes that problem.
Once we hear back again from some affected users,
I'll reissue it for upstream/backstream.
Thanks
next prev parent reply other threads:[~2009-01-14 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:17 sata_mv: trial fix for lost NCQ interrupts Mark Lord
2009-01-14 21:06 ` Harri Olin
2009-01-14 21:26 ` Jeff Garzik
2009-01-14 22:08 ` Mark Lord [this message]
2009-01-14 22:06 ` Mark Lord
2009-01-14 23:18 ` Harri Olin
2009-01-14 23:22 ` Brian Rademacher
2009-01-15 2:53 ` Mark Lord
2009-01-15 13:06 ` Artem Bokhan
2009-01-16 17:03 ` [PATCH] sata_mv: fix timeouts on lower ports of 508x/6081 chips Mark Lord
2009-01-16 20:08 ` Harri Olin
2009-01-17 2:10 ` Brian Rademacher
2009-01-14 22:01 ` sata_mv: trial fix for lost NCQ interrupts Brian Rademacher
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=496E6259.3000502@rtr.ca \
--to=liml@rtr.ca \
--cc=EAMONN.HAMILTON@saic.com \
--cc=harri.olin@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=rad@radfiles.net \
/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).