Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1569062 > unrolled thread
| Started by | Stevie Trujillo <stevie.trujillo@gmail.com> |
|---|---|
| First post | 2017-01-29 00:10 +0100 |
| Last post | 2017-01-29 08:50 +0100 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.kernel
"isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot Stevie Trujillo <stevie.trujillo@gmail.com> - 2017-01-29 00:10 +0100
Re: "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot Sagi Grimberg <sagi@grimberg.me> - 2017-01-29 08:50 +0100
| From | Stevie Trujillo <stevie.trujillo@gmail.com> |
|---|---|
| Date | 2017-01-29 00:10 +0100 |
| Subject | "isert: isert_setup_id: rdma_bind_addr() failed: -19" spam, followed by Recursive Fault on reboot |
| Message-ID | <t4Ki6-7Iv-7@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Sagi Grimberg <sagi@grimberg.me> |
|---|---|
| Date | 2017-01-29 08:50 +0100 |
| Message-ID | <t4Spj-4cV-1@gated-at.bofh.it> |
| In reply to | #1569062 |
> Hello Hey Steve, > 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 You get -ENODEV errors because you don't have an RDMA device. This is probably due to the fact that the mlx5_ib (or mlx4_ib, depending on your device) is not loaded. Can you try loading mlx[4|5]_ib module before you enable iser on a network portal? I do see that mlx5 and mlx4 are requesting the mlx_ib module at probe time, I wander how that didn't happen on your system.. I didn't see a endless loop of this error? can you share your targetcli json? > 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) Would it be possible to try with upstream kernel and report what you are seeing?
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web