From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Ming Lei <tom.leiming@gmail.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
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, 01 Aug 2018 17:03:25 -0700 [thread overview]
Message-ID: <1533168205.3158.12.camel@HansenPartnership.com> (raw)
In-Reply-To: <CACVXFVMrzLRP5Q=cwZGnqeUeyODL3Pq9jMkT7czZouK9510fUA@mail.gmail.com>
On Thu, 2018-08-02 at 07:57 +0800, Ming Lei wrote:
> On Thu, Aug 2, 2018 at 7:47 AM, Guenter Roeck <linux@roeck-us.net>
> wrote:
> > On Wed, Aug 01, 2018 at 03:52:45PM -0700, James Bottomley wrote:
> > > On Wed, 2018-08-01 at 15:48 -0700, Guenter Roeck wrote:
> > > > On Wed, Aug 01, 2018 at 05:58:52PM +1000, Stephen Rothwell
> > > > wrote:
> > > > > Hi all,
> > > > >
> > > > > Changes since 20180731:
> > > > >
> > > > > The pci tree gained a conflict against the pci-current tree.
> > > > >
> > > > > The net-next tree gained a conflict against the bpf tree.
> > > > >
> > > > > The block tree lost its build failure.
> > > > >
> > > > > The staging tree still had its build failure due to an
> > > > > interaction
> > > > > with
> > > > > the vfs tree for which I disabled CONFIG_EROFS_FS.
> > > > >
> > > > > The kspp tree lost its build failure.
> > > > >
> > > > > Non-merge commits (relative to Linus' tree): 10070
> > > > > 9137 files changed, 417605 insertions(+), 179996 deletions(-
> > > > > )
> > > > >
> > > > > -----------------------------------------------------------
> > > > > ------
> > > > > -----------
> > > > >
> > > >
> > > > The widespread kernel hang issues are still seen. I managed
> > > > to bisect it after working around the transient build failures.
> > > > Bisect log is attached below. Unfortunately, it doesn't help
> > > > much.
> > > > The culprit is reported as:
> > > >
> > > > 2d542828c5e9 Merge remote-tracking branch 'scsi/for-next'
> > > >
> > > > The preceding merge,
> > > >
> > > > 453f1d821165 Merge remote-tracking branch 'cgroup/for-next'
> > > >
> > > > checks out fine, as does the tip of scsi-next (commit
> > > > 103c7b7e0184,
> > > > "Merge branch 'misc' into for-next"). No idea how to proceed.
> > >
> > > This sounds like you may have a problem with this patch:
> > >
> > > commit d5038a13eca72fb216c07eb717169092e92284f1
> > > Author: Johannes Thumshirn <jthumshirn@suse.de>
> > > Date: Wed Jul 4 10:53:56 2018 +0200
> > >
> > > scsi: core: switch to scsi-mq by default
> > >
> > > To verify, boot with the additional kernel parameter
> > >
> > > scsi_mod.use_blk_mq=0
> > >
> > > Which will reverse the effect of the above patch.
> > >
> >
> > Yes, that fixes the problem.
>
> That may not the root cause, given this issue is only started to
> see from next-20180731, but d5038a13eca7 (scsi: core: switch to
> scsi-mq by default)
> has been in -next for quite a while.
>
> Seems something new causes this issue.
Read my other email about how to find this.
https://marc.info/?l=linux-scsi&m=153316446223676
Now that we've confirmed the issue, Gunter, could you attempt to bisect
it as that email describes?
Thanks,
James
next prev parent reply other threads:[~2018-08-02 0:03 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
2018-08-01 23:47 ` Guenter Roeck
2018-08-01 23:57 ` Ming Lei
2018-08-02 0:03 ` James Bottomley [this message]
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=1533168205.3158.12.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sfr@canb.auug.org.au \
--cc=tom.leiming@gmail.com \
/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).