All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Meelis Roos <mroos@linux.ee>,
	linux-scsi@cger.kernel.org, sparclinux@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: Sparc ESP problem with blk-mq
Date: Tue, 14 Oct 2014 08:37:14 -0600	[thread overview]
Message-ID: <543D351A.1020505@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1410140102230.18488@adalberg.ut.ee>

On 2014-10-13 16:07, Meelis Roos wrote:
> I turned on blk-mq for all my test machines today and got a failure from
> Sun Ultra 1 with Sparc ESP SCSI (dmesg below). Booting with
> scsi_mod.use_blk_mq=0 fixes the problem. The problem is reproducible.

[snip]

> [   63.244199] esp: esp0, regs[1ffe8800000:1ffe8400000] irq[10]
> [   63.310055] esp: esp0 is a FAS100A, 40 MHz (ccf=0), SCSI ID 7
> [   66.383895] scsi host0: esp
> [  148.437533] scsi 0:0:0:0: timing out command, waited 82s
> [  149.674112] ESP: unexpected IREG 40
> [  149.713889] esp: esp0: Dumping command log
> [  149.762847] esp: esp0: ent[14] CMD val[01] sreg[93] seqreg[04] sreg2[00] ireg[18] ss[00] event[0d]

[snip]

Christoph, any idea on this? The command just times out, for some 
reason. Only thing I could think of was related to perhaps missing 
bouncing or similar, but I don't think that's the case. But the hba must 
not like the request somehow. Or perhaps it sets up the wrong number of 
segments.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Meelis Roos <mroos@linux.ee>,
	linux-scsi@cger.kernel.org, sparclinux@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: Sparc ESP problem with blk-mq
Date: Tue, 14 Oct 2014 14:37:14 +0000	[thread overview]
Message-ID: <543D351A.1020505@kernel.dk> (raw)
In-Reply-To: <alpine.LRH.2.11.1410140102230.18488@adalberg.ut.ee>

On 2014-10-13 16:07, Meelis Roos wrote:
> I turned on blk-mq for all my test machines today and got a failure from
> Sun Ultra 1 with Sparc ESP SCSI (dmesg below). Booting with
> scsi_mod.use_blk_mq=0 fixes the problem. The problem is reproducible.

[snip]

> [   63.244199] esp: esp0, regs[1ffe8800000:1ffe8400000] irq[10]
> [   63.310055] esp: esp0 is a FAS100A, 40 MHz (ccf=0), SCSI ID 7
> [   66.383895] scsi host0: esp
> [  148.437533] scsi 0:0:0:0: timing out command, waited 82s
> [  149.674112] ESP: unexpected IREG 40
> [  149.713889] esp: esp0: Dumping command log
> [  149.762847] esp: esp0: ent[14] CMD val[01] sreg[93] seqreg[04] sreg2[00] ireg[18] ss[00] event[0d]

[snip]

Christoph, any idea on this? The command just times out, for some 
reason. Only thing I could think of was related to perhaps missing 
bouncing or similar, but I don't think that's the case. But the hba must 
not like the request somehow. Or perhaps it sets up the wrong number of 
segments.

-- 
Jens Axboe


  reply	other threads:[~2014-10-14 14:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 22:07 Sparc ESP problem with blk-mq Meelis Roos
2014-10-13 22:07 ` Meelis Roos
2014-10-14 14:37 ` Jens Axboe [this message]
2014-10-14 14:37   ` Jens Axboe
2014-10-14 14:38 ` Jens Axboe
2014-10-14 14:38   ` Jens Axboe
2014-10-15 13:35   ` Christoph Hellwig
2014-10-15 13:35     ` Christoph Hellwig
2014-10-15 20:53     ` David Miller
2014-10-15 20:53       ` David Miller
2014-10-16  6:43       ` mroos
2014-10-16  6:43         ` mroos
2014-10-17 19:56         ` David Miller
2014-10-17 19:56           ` David Miller
2014-10-18 17:31           ` David Miller
2014-10-18 17:31             ` David Miller
2014-10-18 17:57             ` Christoph Hellwig
2014-10-18 17:57               ` Christoph Hellwig
2014-10-19 12:10               ` mroos
2014-10-19 12:10                 ` mroos
2014-10-19 14:10                 ` Christoph Hellwig
2014-10-19 14:10                   ` Christoph Hellwig

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=543D351A.1020505@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=linux-scsi@cger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=sparclinux@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.