Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition

From: Nix <nix@esperi.org.uk>
To: Bernd Schubert <bernd.schubert@fastmail.fm>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	nick.cheng@areca.com.tw, stable@vger.kernel.org
Subject: Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition
Date: Mon, 29 Jul 2013 22:09:31 +0100	[thread overview]
Message-ID: <87fvuxdqes.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <51F67959.2060803@fastmail.fm> (Bernd Schubert's message of "Mon, 29 Jul 2013 16:16:57 +0200")

On 29 Jul 2013, Bernd Schubert uttered the following:

> On 07/29/2013 03:05 PM, Nix wrote:
>> On 29 Jul 2013, Bernd Schubert said:
>>
>>> Hi Nick,
>>>
>>> On 07/29/2013 12:10 PM, Nick Alcock wrote:
>>>> arcmsr0: abort device command of scsi id = 0 lun = 1
>>>> arcmsr0: abort device command of scsi id = 0 lun = 0
>>>> arcmsr: executing bus reset eh.....num_resets=0, num_[...]
>>>>
>>>> arcmsr0: wait 'abort all outstanding command' timeout
>>>> arcmsr0: executing hw bus reset ....
>>>> arcmsr0: waiting for hw bus reset return, retry=0
>>>> arcmsr0: waiting for hw bus reset return, retry=1
>>>> Areca RAID Controller0: F/W V1.46 2009-01-06 & Model ARC-1210
>>>> arcmsr: scsi  bus reset eh returns with success
>>>> [and back to the top of the error messages again, apparently forever,
>>>>    not that the machine would be much use without its RAID array even
>>>>    if this loop terminated at some point, so I only gave it a couple
>>>>    of minutes]
>>>>
>>>> The failure happens precisely at the moment we transition to early
>>>> userspace, so presumably userspace I/O is failing (or something related
>>>> to raw device access, perhaps, since the first thing it does is a
>>>> vgscan).
>>>>
>>>> I haven't bisected yet (sorry, I have work to do which means this
>>>> machine must be running right now), but nothing has changed in the
>>>> arcmsr controller, nor in SCSI-land excepting
>>>>
>>>> commit 98dcc2946adbe4349ef1ef9b99873b912831edd4
>>>> Author: Martin K. Petersen <martin.petersen@oracle.com>
>>>> Date:   Thu Jun 6 22:15:55 2013 -0400

I can now confirm that reverting this commit causes this problem to go
away, and my machine boots fine again.

Please revert (and figure out what is wrong so that 3.11 doesn't
implode in the same way? I'm happy to assist...)

(My apologies if a 'please revert' from someone bitten by a stable
regression isn't adequate reason to revert the thing: I've never been
quite sure who should report regressions in stable patches to Greg. It
should at least be *evidence*. So here's my "it crashed and now it
doesn't" evidence. :} )

-- 
NULL && (void)