From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Meelis Roos <mroos@linux.ee>,
linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Sparc ESP problem with blk-mq
Date: Wed, 15 Oct 2014 06:35:51 -0700 [thread overview]
Message-ID: <20141015133551.GA15539@infradead.org> (raw)
In-Reply-To: <543D355A.3030605@kernel.dk>
On Tue, Oct 14, 2014 at 08:38:18AM -0600, Jens Axboe wrote:
> 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.
Seems like this is the first command we send. I don't really have an
idea at the moment, but it would be good to increase the scsi_logging
level to the maximum and/or add some traces to the esp driver to figure
out where the command gets lost.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Meelis Roos <mroos@linux.ee>,
linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Sparc ESP problem with blk-mq
Date: Wed, 15 Oct 2014 13:35:51 +0000 [thread overview]
Message-ID: <20141015133551.GA15539@infradead.org> (raw)
In-Reply-To: <543D355A.3030605@kernel.dk>
On Tue, Oct 14, 2014 at 08:38:18AM -0600, Jens Axboe wrote:
> 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.
Seems like this is the first command we send. I don't really have an
idea at the moment, but it would be good to increase the scsi_logging
level to the maximum and/or add some traces to the esp driver to figure
out where the command gets lost.
next prev parent reply other threads:[~2014-10-15 13:35 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
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 [this message]
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=20141015133551.GA15539@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-scsi@vger.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.