[Bug 996062] New: kernel: connection1:0: detected conn error (1020)
http://bugzilla.suse.com/show_bug.cgi?id=996062 Bug ID: 996062 Summary: kernel: connection1:0: detected conn error (1020) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers@forge.provo.novell.com Reporter: steve.moring@microfocus.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- iscsi connection stability problems following kernel update to 4.1.27-27-default. Reversion to 4.1.12-1-default restores iscsi functionality. When you attempt to write large files in rapid succession to the mount point that's backed by an iscsi target, it results in the following errors being thrown at the iscsi-client server. I used dd to through zero's at a file on the mountpoint. Aug 26 13:03:21 kvmfr kernel: connection1:0: detected conn error (1020) Aug 26 13:03:21 kvmfr iscsid[7968]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TC .... repeats multiple times .... Aug 26 13:03:27 kvmfr kernel: connection1:0: detected conn error (1020) Aug 26 13:03:27 kvmfr iscsid[7968]: iscsid: Kernel reported iSCSI connection 1:0 error (1020 - ISCSI_ERR_TCP_CONN_CLOSE: TC Aug 26 13:03:31 kvmfr kernel: sd 7:0:0:1: [sdd] FAILED Result: hostbyte=DID_TRANSPORT_DISRUPTED driverbyte=DRIVER_OK Aug 26 13:03:31 kvmfr kernel: sd 7:0:0:1: [sdd] CDB: Write(10) 2a 00 7c cc c8 80 00 10 00 00 Aug 26 13:03:31 kvmfr kernel: blk_update_request: I/O error, dev sdd, sector 2093795456 It does not lose the mount point, but any further writes to it will fail with the errors above. Reverting to an older kernel returns functionality. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=996062
Steven Moring
http://bugzilla.suse.com/show_bug.cgi?id=996062
Steven Moring
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c1
Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c2
--- Comment #2 from Steven Moring
Could you check with the newer 4.1.x kernel that is available in OBS Kernel:openSUSE-42.1 repo?
Pardon my ignorance. Do you want me to add this as a repo then consume the kernel as built, or do you want me to download the sources and go from there? http://download.opensuse.org/repositories/Kernel:/openSUSE-42.1/standard/x86... This shows 4.1.31 (I'm running 27). Thanks -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c3
--- Comment #3 from Takashi Iwai
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c4
--- Comment #4 from Steven Moring
Either way, as you like. You can download kernel-default.rpm from the URL you pointed, and install it via "zypper in" or "rpm -ivh", too. The point is to see whether this was already fixed in the recent 4.1.x kernel.
Symptom still occurs with: 4.1.31-30-default. Reverting back to 4.1.12-1-default, error goes away. I'm beginning to suspect jumbo packets might be my problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c5
Steven Moring
http://bugzilla.suse.com/show_bug.cgi?id=996062
http://bugzilla.suse.com/show_bug.cgi?id=996062#c6
Jiri Slaby
participants (1)
-
bugzilla_noreply＠novell.com