[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1520953013.2638.2.camel@wdc.com>
Date: Tue, 13 Mar 2018 14:56:54 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "martin@...htvoll.de" <martin@...htvoll.de>,
"ming.lei@...hat.com" <ming.lei@...hat.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"hdegoede@...hat.com" <hdegoede@...hat.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"regressions@...mhuis.info" <regressions@...mhuis.info>,
"tj@...nel.org" <tj@...nel.org>,
"jejb@...ux.vnet.ibm.com" <jejb@...ux.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
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.
Powered by blists - more mailing lists