From: Sagi Grimberg <sagig-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 4.5-rc iser issues
Date: Sun, 14 Feb 2016 11:02:12 +0200 [thread overview]
Message-ID: <56C04294.3090701@dev.mellanox.co.il> (raw)
In-Reply-To: <20160214074119.GA24558-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
> iSER on 4.5-rc3 seems to fall over pretty quickly for me. The
> test is a a single LUN, against a Linux iSER target, also running
> 4.5-rc. Both are usinx mlx4 hardware. These messages appear
> immediately when running xfstests on xfs (but not during mkfs.xfs),
> and after a few dozend tests with ext4, and ultimiately lock up the
> system:
>
> Feb 13 13:33:57 redstar37 kernel: [ 566.871038] iser: iser_fast_reg_fmr: ib_fmr_pool_map_phys failed: -22
> Feb 13 13:33:57 redstar37 kernel: [ 566.878278] iser: iser_prepare_read_cmd: Failed to set up Data-IN RDMA
> Feb 13 13:33:57 redstar37 kernel: [ 566.885604] iser: iser_send_command: conn ffff8809261bbb28 failed task->itt 5 err -22
> Feb 13 13:33:57 redstar37 kernel: [ 566.899804] iser: iser_fast_reg_fmr: ib_fmr_pool_map_phys failed: -22
> Feb 13 13:33:57 redstar37 kernel: [ 566.907037] iser: iser_prepare_read_cmd: Failed to set up Data-IN RDMA
> Feb 13 13:33:57 redstar37 kernel: [ 566.914355] iser: iser_send_command: conn ffff8809261bbb28 failed task->itt 6 err -22
>
> When hacking the initiator to use FRs instead of FMRs I get something
> fairly similar:
>
> Feb 13 22:49:18 redstar37 kernel: [ 277.500477] iser: iser_fast_reg_mr: failed to map sg (5/6)
> Feb 13 22:49:18 redstar37 kernel: [ 277.506679] iser: iser_prepare_write_cmd: Failed to register write cmd RDMA mem
> Feb 13 22:49:18 redstar37 kernel: [ 277.514906] iser: iser_send_command: conn ffff88091ac8cb28 failed task->itt 59 err -22
> Feb 13 22:49:18 redstar37 kernel: [ 277.529614] iser: iser_fast_reg_mr: failed to map sg (5/6)
> Feb 13 22:49:18 redstar37 kernel: [ 277.535785] iser: iser_prepare_write_cmd: Failed to register write cmd RDMA mem
> Feb 13 22:49:18 redstar37 kernel: [ 277.544006] iser: iser_send_command: conn ffff88091ac8cb28 failed task->itt 29 err -22
> Feb 13 22:49:18 redstar37 kernel: [ 277.558669] iser: iser_fast_reg_mr: failed to map sg (5/6)
> Feb 13 22:49:18 redstar37 kernel: [ 277.564844] iser: iser_prepare_write_cmd: Failed to register write cmd RDMA mem
> Feb 13 22:49:18 redstar37 kernel: [ 277.573069] iser: iser_send_command: conn ffff88091ac8cb28 failed task->itt 78 err -22
> Feb 13 22:49:18 redstar37 kernel: [ 277.587677] iser: iser_fast_reg_mr: failed to map sg (5/6)
>
> The only other kernel version I had available quickly is 3.16 from Debian
> Jessie, and that works fine.
Thanks for reporting, I'll have a look.
I suspect this is coming from Keith+Ming changes in
blk_bio_segment_split()...
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-14 9:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 7:41 4.5-rc iser issues Christoph Hellwig
[not found] ` <20160214074119.GA24558-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2016-02-14 9:02 ` Sagi Grimberg [this message]
2016-02-14 9:59 ` Sagi Grimberg
2016-02-14 9:59 ` Sagi Grimberg
2016-02-14 11:36 ` Sagi Grimberg
2016-02-14 11:36 ` Sagi Grimberg
2016-02-14 14:02 ` Sagi Grimberg
2016-02-14 14:02 ` Sagi Grimberg
2016-02-14 15:22 ` Christoph Hellwig
2016-02-14 15:22 ` Christoph Hellwig
2016-02-14 16:20 ` Ming Lei
2016-02-14 16:20 ` Ming Lei
2016-02-14 16:29 ` Sagi Grimberg
2016-02-14 16:29 ` Sagi Grimberg
2016-02-14 16:39 ` Ming Lei
2016-02-14 16:39 ` Ming Lei
2016-02-15 7:11 ` Ming Lei
2016-02-15 7:11 ` Ming Lei
2016-02-15 7:45 ` Sagi Grimberg
2016-02-15 7:45 ` Sagi Grimberg
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=56C04294.3090701@dev.mellanox.co.il \
--to=sagig-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.