From: Christoph Hellwig <hch@infradead.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-usb <linux-usb@vger.kernel.org>,
SCSI development list <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [REGRESSION 3.17] scsi (uas) disks no longer using tagged command queuing
Date: Thu, 11 Sep 2014 09:13:31 -0700 [thread overview]
Message-ID: <20140911161331.GA24488@infradead.org> (raw)
In-Reply-To: <541172E9.8070309@redhat.com>
On Thu, Sep 11, 2014 at 12:01:13PM +0200, Hans de Goede wrote:
> > So we're initializing the tag map, but scsi_activate_tcq doesn't pick it
> > up. I can't really come up with a good explanation for it, but there
> > even without that there is an elephant in the room: as part of the
> > scsi-mq series I moved the bqt field used for this into a union with the
> > new blk_mq_tag_set. Below is a patch to get rid of that union, can you
> > try if that fixes it?
>
> Unfortunately that does not fix it :|
Alright, I guess we need the big bisect hammer unfortunately.
We should be able to start with trying the first and last commit
of the big SCSI merge:
start: fcc95a763444017288b318d48367098850c23c0d
end: c21a2c1a4973c8dde32557970fdb44eaa9489aeb
next prev parent reply other threads:[~2014-09-11 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 9:15 [REGRESSION 3.17] scsi (uas) disks no longer using tagged command queuing Hans de Goede
2014-09-09 15:27 ` Christoph Hellwig
2014-09-10 7:21 ` Hans de Goede
2014-09-10 15:45 ` Christoph Hellwig
2014-09-11 10:01 ` Hans de Goede
2014-09-11 16:13 ` Christoph Hellwig [this message]
2014-09-12 19:49 ` Hans de Goede
2014-09-12 23:00 ` [PATCH] scsi: fix regression that accidentally disabled block-based tcq Christoph Hellwig
2014-09-13 10:28 ` Hans de Goede
2014-09-13 17:50 ` Christoph Hellwig
2014-09-14 9:41 ` Hans de Goede
2014-09-15 18:47 ` review-ping: " Christoph Hellwig
2014-09-15 19:05 ` Webb Scales
2014-09-15 19:15 ` Hans de Goede
2014-09-15 19:39 ` Jeff Moyer
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=20140911161331.GA24488@infradead.org \
--to=hch@infradead.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@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 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).