From: Jeff Garzik <jeff@garzik.org>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-ide@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Dave Dillow <dave@thedillows.org>, dean gaudet <dean@arctic.org>
Subject: Re: [PATCH] sata_mv: new exception handling (hotplug, NCQ framework)
Date: Fri, 01 Jun 2007 16:17:51 -0400 [thread overview]
Message-ID: <46607EEF.8080602@garzik.org> (raw)
In-Reply-To: <464EE3E9.80708@wpkg.org>
Tomasz Chmielewski wrote:
> Jeff Garzik schrieb:
>> Below is a refresh of my on-going effort to convert sata_mv to the new
>> exception handling framework. sata_mv is one of the last hold-outs, and
>> its old-EH implementation blocks new features like hotplug and NCQ.
>>
>> It works for me on the one 50xx and one 60xx card I tested it on, but
>> other testers reported regressions, which is why it is not yet upstream.
>
> Hi,
>
> If I'm correct, this patch won't make to 2.6.22, and the first possible
> inclusion would be 2.6.23?
Correct... if that. No guarantee it will make 2.6.23 either, since it
is low priority :(
> Could you summarize what other regressions were reported? I can't find
> much information about sata_mv regressiobs on linux-ide list (at least
> when looking at the subjects: lots of patches from you, and two reports
> from me).
Dave Dillow and dean gaudet responded with reports that the
BUG_ON/WARN_ON traps in would trigger:
WARNING: at drivers/ata/sata_mv.c:1287 mv_qc_issue()
and
WARNING: at drivers/ata/sata_mv.c:1333 mv_get_crpb_status()
which leads me to think that my sata_mv new-EH patches are accidentally
turning on NCQ mode.
I have a feeling that I will be able to reproduce this once I attach an
NCQ-capable drive and re-test on my own systems, but again, haven't
found the time :/
Jeff
prev parent reply other threads:[~2007-06-01 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-19 5:42 [PATCH] sata_mv: new exception handling (hotplug, NCQ framework) Jeff Garzik
2007-05-19 11:47 ` Tomasz Chmielewski
2007-06-01 20:17 ` 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=46607EEF.8080602@garzik.org \
--to=jeff@garzik.org \
--cc=dave@thedillows.org \
--cc=dean@arctic.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mangoo@wpkg.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.