From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Sander <sander@humilis.net>, Mark Lord <liml@rtr.ca>,
Mark Lord <lkml@rtr.ca>, Andrew Morton <akpm@osdl.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.6.xx: sata_mv: another critical fix
Date: Tue, 21 Mar 2006 16:37:20 -0500 [thread overview]
Message-ID: <44207210.9080903@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0603211316580.3622@g5.osdl.org>
Linus Torvalds wrote:
> Maybe back-porting any critical sata_mv fixes to 2.6.16.x is appropriate,
> considering that I don't think RH or SuSE will necessarily want to pull
> the whole thing.
Agreed -- in theory -- but I'll let Mark Lord or somebody else do that,
if they are motivated. sata_mv is labelled "HIGHLY EXPERIMENTAL" for a
reason :) Its a known bug report generator, with bugs far outpacing
fixes at present.
Key patches to backport or test, in priority order, would be:
[libata sata_mv] do not enable PCI MSI by default
[libata sata_mv] add 6042 support, fix 60xx/50xx EDMA configuration
[PATCH] Add missing FUA write to sata_mv dma command list
After that, you're at the mercy of not-yet-worked-around hardware bugs,
and (as Mark Lord appears to be finding) some driver bugs as well.
sata_mv development slowed to a trickle for a long time, after the
original developer disappeared, and I didn't have time to dig deep into
the hardware details. Mark Lord recently started picking up the pieces,
so things are looking much better already. I have another patch from
Mark to forward to you and 2.6.16.x (stable@), coming to you today.
Jeff
next prev parent reply other threads:[~2006-03-21 21:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 0:57 [git patch append] sata_mv fix Jeff Garzik
2006-03-21 5:00 ` [PATCH] 2.6.xx: sata_mv: another critical fix Mark Lord
2006-03-21 12:13 ` Sander
2006-03-21 13:51 ` Mark Lord
2006-03-21 15:37 ` Sander
2006-03-21 18:33 ` Linus Torvalds
2006-03-21 19:15 ` Sander
2006-03-21 19:22 ` Mark Lord
2006-03-21 19:35 ` Linus Torvalds
2006-03-21 20:44 ` Sander
2006-03-21 20:59 ` Linus Torvalds
2006-03-21 21:09 ` Jeff Garzik
2006-03-21 21:19 ` Linus Torvalds
2006-03-21 21:37 ` Jeff Garzik [this message]
2006-03-22 5:48 ` Sander
2006-03-22 9:00 ` Sander
2006-03-22 14:50 ` Mark Lord
2006-03-22 17:09 ` Sander
2006-03-22 17:53 ` Eric D. Mudama
2006-03-22 18:01 ` Sander
2006-03-22 17:55 ` Mark Lord
2006-03-28 4:34 ` Mark Lord
2006-05-03 12:16 ` Sander
2006-05-03 12:42 ` Mark Lord
2006-05-03 13:32 ` Sander
2006-05-03 16:46 ` Mark Lord
2006-05-03 18:39 ` Sander
2006-03-22 2:12 ` 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=44207210.9080903@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=sander@humilis.net \
--cc=torvalds@osdl.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).