From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "martin@lichtvoll.de" <martin@lichtvoll.de>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"regressions@leemhuis.info" <regressions@leemhuis.info>,
"tj@kernel.org" <tj@kernel.org>,
"jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>
Subject: Re: [Possible REGRESSION, 4.16-rc4] Error updating SMART data during runtime and could not connect to lvmetad at some boot attempts
Date: Tue, 13 Mar 2018 14:56:54 +0000 [thread overview]
Message-ID: <1520953013.2638.2.camel@wdc.com> (raw)
In-Reply-To: <20180313143222.GA10883@ming.t460p>
On Tue, 2018-03-13 at 22:32 +0800, Ming Lei wrote:
> On Tue, Mar 13, 2018 at 02:08:23PM +0100, Martin Steigerwald wrote:
> > Ming and Bart, I added you to cc, cause I had to do with you about another
> > blk-mq report, please feel free to adapt.
>
> Looks RIP points to scsi_times_out+0x17/0x1d0, maybe a SCSI regression?
I think that it's much more likely that this is a block layer regression. See
e.g. "[PATCH v2] blk-mq: Fix race between resetting the timer and completion
handling" (https://www.mail-archive.com/linux-block@vger.kernel.org/msg18338.html).
Bart.
next prev parent reply other threads:[~2018-03-13 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 8:20 Martin Steigerwald
2018-03-11 14:37 ` Hans de Goede
2018-03-11 16:28 ` Martin Steigerwald
2018-03-11 16:41 ` Hans de Goede
2018-03-13 13:08 ` Martin Steigerwald
2018-03-13 14:32 ` Ming Lei
2018-03-13 14:56 ` Bart Van Assche [this message]
2018-03-14 11:01 ` Martin Steigerwald
2018-03-14 11:05 ` Hans de Goede
2018-03-14 12:48 ` Martin Steigerwald
2018-03-18 21:34 ` Hans de Goede
2018-03-18 22:06 ` Martin Steigerwald
2018-03-19 9:32 ` Hans de Goede
2018-03-15 10:48 ` Martin Steigerwald
2018-03-19 9:42 ` Thorsten Leemhuis
2018-03-19 9:50 ` Hans de Goede
2018-03-19 12:35 ` Martin Steigerwald
2018-04-10 17:30 ` Martin Steigerwald
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=1520953013.2638.2.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=hdegoede@redhat.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=martin@lichtvoll.de \
--cc=ming.lei@redhat.com \
--cc=regressions@leemhuis.info \
--cc=tj@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
Powered by JetHome