linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: Re: [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition
Date: Mon, 29 Jul 2013 16:01:49 +0100	[thread overview]
Message-ID: <8738qxfm02.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 spake thusly:

> On 07/29/2013 03:05 PM, Nix wrote:
>> On 29 Jul 2013, Bernd Schubert said:
>>> I tested this patch with ARC-1260 and F/W V1.49, no issues. Also, this
>>> patch is only in 3.10.3, but not yet in 3.10.1.
>>
>> ... and I see this problem with 3.10.3 but not 3.10.1. (Haven't tried
>> 3.10.2.)
>
> Hmm, indeed that points to this commit. I just don't see what could fail there.
>
> Could you try to run these commands with 3.10.1?
>
> # # check if reporting opcodes works
> # sg_opcodes -v  -n /dev/sdX
>
> # check ata information page
> # sg_vpd --page=0x89 /dev/sdX

If this might cause the same problem I think I'd better wait until work
is done for the day and the machine is no longer loaded, and can be
rebooted without harm...

>> No changes to arcmsr between those versions... I suspect I'll have to
>> bisect, which will be a complete pig because every failure means a hard
>> powerdown of this box. Always-on servers rarely appreciate hard
>> powerdowns :(
>>
>
> Maybe just revert this commit? Helpful would be some scsi logging to
> see which command actually fails. I guess you don't have a serial
> console?

Not at that stage, no! And, yes, a test revert of this one commit will
be the first thing I try this evening / tomorrow morning (depending on
system load).

-- 
NULL && (void)

  reply	other threads:[~2013-07-29 15:01 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-29 10:10 [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition Nick Alcock
2013-07-29 13:01 ` Bernd Schubert
2013-07-29 13:05   ` Nix
2013-07-29 14:16     ` Bernd Schubert
2013-07-29 15:01       ` Nix [this message]
2013-07-29 20:04       ` Nix
2013-07-29 20:15         ` Martin K. Petersen
2013-07-29 21:09       ` Nix
2013-07-29 23:34         ` Martin K. Petersen
2013-07-30 18:09           ` Bernd Schubert
2013-07-31  0:07             ` Nick Alcock
2013-07-31  3:19               ` Martin K. Petersen
2013-07-31  3:15             ` Martin K. Petersen
2013-07-31 17:51               ` Bernd Schubert
2013-07-31 18:40                 ` Bernd Schubert
2013-08-01 14:34                   ` [PATCH] scsi disk: Use its own buffer for the vpd request Bernd Schubert
2013-08-01 14:37                     ` Bernd Schubert
2013-08-02  3:00                     ` Martin K. Petersen
2013-08-26 20:15                       ` Bernd Schubert
2013-08-02 23:46                     ` Nick Alcock
2013-08-03 11:17                     ` Nick Alcock
2013-08-30 10:01                     ` Nix
2013-08-31  1:53                       ` Greg KH
2013-08-31 19:48                         ` Nix
2013-09-01 18:40                           ` Bernd Schubert
2013-09-20 22:51                             ` Martin K. Petersen
2013-09-23 12:47                   ` [PATCH] scsi disk: Reduce buffer size for " Bernd Schubert
2013-07-30  0:28         ` [SCSI REGRESSION] 3.10.2 or 3.10.3: arcmsr failure at bootup / early userspace transition Douglas Gilbert
2013-07-30  0:56           ` Nix
2013-07-30 18:14             ` Bernd Schubert
2013-07-30 21:20               ` Nix
2013-08-01 14:55                 ` Bernd Schubert
2013-08-01 16:04                   ` Nix
2013-08-01 16:21                     ` Bernd Schubert
2013-07-31  3:10           ` Martin K. Petersen
2013-07-29 14:27   ` Martin K. Petersen
2013-07-29 14:26 ` Martin K. Petersen

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=8738qxfm02.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=bernd.schubert@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=nick.cheng@areca.com.tw \
    /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).