All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stevie Trujillo <stevie.trujillo@gmail.com>
To: target-devel@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
	Doug Ledford <dledford@redhat.com>,
	Sean Hefty <sean.hefty@intel.com>,
	Hal Rosenstock <hal.rosenstock@gmail.com>
Subject: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot
Date: Sun, 29 Jan 2017 00:01:24 +0100	[thread overview]
Message-ID: <20170129000124.7199b7b5@localhost> (raw)

Hello

I'm trying (failing) to get iSER working. After rebooting with some settings
saved in targetcli, I got an endless stream of messages like this:

[  192.701299] isert: isert_setup_id: rdma_bind_addr() failed: -19
[  192.702733] isert: isert_setup_id: rdma_bind_addr() failed: -19
[  192.704021] isert: isert_setup_id: rdma_bind_addr() failed: -19
[  192.705458] isert: isert_setup_id: rdma_bind_addr() failed: -19
[  192.706979] isert: isert_setup_id: rdma_bind_addr() failed: -19

I tried deleting everything from targetcli, but the flood would not stop. The
ib_isert module did not unload. When rebooting I got a "Recursive Fault"
with a stacktrace inside configfs.

I hope this is enough information to fix this bug. I assumed the stacktrace
would be saved to the log so I didn't write it down, and I haven't been able to
retrace all the wrong stuff I did trying to make iSER work.

Linux Version: Linux 4.8.15-2~bpo8+2 (Debian 8 Backports)

--
Stevie Trujillo

             reply	other threads:[~2017-01-28 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-28 23:01 Stevie Trujillo [this message]
2017-01-29  7:39 ` "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot Sagi Grimberg
     [not found]   ` <81437a39-c0e0-0215-08e5-50d8b9da1d8b-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-01-30 22:52     ` Stevie Trujillo
2017-01-30 22:52       ` Stevie Trujillo

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=20170129000124.7199b7b5@localhost \
    --to=stevie.trujillo@gmail.com \
    --cc=dledford@redhat.com \
    --cc=hal.rosenstock@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sagi@grimberg.me \
    --cc=sean.hefty@intel.com \
    --cc=target-devel@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.