From: Guenter Roeck <linux@roeck-us.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: linux-next: Tree for Aug 1
Date: Wed, 1 Aug 2018 18:19:00 -0700 [thread overview]
Message-ID: <83936bed-e783-191f-c308-8f8470a0dbf3@roeck-us.net> (raw)
In-Reply-To: <20180802100505.56e663cb@canb.auug.org.au>
On 08/01/2018 05:05 PM, Stephen Rothwell wrote:
> Hi all,
>
> On Wed, 01 Aug 2018 16:00:54 -0700 James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
>>
>> So what seems to be happening to cause this is that there's a patch
>> somewhere between the merge base of my scsi-next series and the next
>> tree and the patch just before scsi-next was actually merged that
>> actually causes a boot failure with blk-mq enabled. Could you try to
>> find this patch? I think the way to do it is to try to bisect this
>> range of linux-next using the command line
>>
>> scsi_mod.use_blk_mq=1
>>
>> Which forces block mq to be the default and seeing where the first boot
>> failure is (you don't need my scsi-next tree merged to do this because
>> all the offending patch does is flip the default state of the above
>> flag).
>
> So this means using v4.8-rc1 as the first good commit and 453f1d821165
> ("Merge remote-tracking branch 'cgroup/for-next'") as the first bad
> (assuming that this latter fails to boot with "scsi_mod.use_blk_mq=1").
>
Puzzled. Same results. 453f1d821165 works with both scsi_mod.use_blk_mq=0
and scsi_mod.use_blk_mq=1. next-20180801 works with scsi_mod.use_blk_mq=0
and fails with scsi_mod.use_blk_mq=1. Bisect still points to the same commit
(which just changes the default) as culprit. I know that doesn't make sense.
I'll need to think about it.
Guenter
next prev parent reply other threads:[~2018-08-02 1:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-01 7:58 linux-next: Tree for Aug 1 Stephen Rothwell
2018-08-01 22:48 ` Guenter Roeck
2018-08-01 22:52 ` James Bottomley
2018-08-01 23:00 ` James Bottomley
2018-08-02 0:05 ` Stephen Rothwell
2018-08-02 1:19 ` Guenter Roeck [this message]
2018-08-01 23:47 ` Guenter Roeck
2018-08-01 23:57 ` Ming Lei
2018-08-02 0:03 ` James Bottomley
2018-08-02 0:20 ` Guenter Roeck
2018-08-02 4:58 ` Guenter Roeck
2018-08-02 5:04 ` Bart Van Assche
2018-08-02 12:46 ` Guenter Roeck
2018-08-02 12:51 ` Johannes Thumshirn
2018-08-02 13:00 ` Guenter Roeck
2018-08-02 13:06 ` Johannes Thumshirn
2018-08-02 11:35 ` Ming Lei
2018-08-02 13:05 ` Guenter Roeck
2018-08-02 16:27 ` Ming Lei
2018-08-02 16:40 ` Bart Van Assche
2018-08-02 16:50 ` Ming Lei
2018-08-02 16:57 ` Bart Van Assche
2018-08-02 0:12 ` Guenter Roeck
-- strict thread matches above, loose matches on Subject: below --
2023-08-01 5:19 Stephen Rothwell
2019-08-01 6:14 Stephen Rothwell
2017-08-01 7:37 Stephen Rothwell
2017-08-01 12:42 ` Sergey Senozhatsky
2017-08-01 13:20 ` Arnd Bergmann
2017-08-01 13:28 ` Arnd Bergmann
2017-08-01 23:55 ` Sergey Senozhatsky
2017-08-02 11:13 ` Arnd Bergmann
2016-08-01 4:02 Stephen Rothwell
2014-08-01 9:14 Stephen Rothwell
2013-08-01 7:25 Stephen Rothwell
2013-08-01 7:50 ` Sedat Dilek
2011-08-01 4:47 Stephen Rothwell
2011-08-01 7:01 ` Sedat Dilek
2011-08-01 21:54 ` Randy Dunlap
2011-08-02 1:29 ` Stephen Rothwell
2011-08-02 10:38 ` Sedat Dilek
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=83936bed-e783-191f-c308-8f8470a0dbf3@roeck-us.net \
--to=linux@roeck-us.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).