Date: Thu, 26 Feb 2015 11:32:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 193802] tso seems broken on RELENG10 for version 7.4.2 of em driver Message-ID: <bug-193802-8-gIKYBWeiDm@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-193802-8@https.bugs.freebsd.org/bugzilla/> References: <bug-193802-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193802 Karli.Sjoberg@slu.se changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |Karli.Sjoberg@slu.se --- Comment #2 from Karli.Sjoberg@slu.se --- Same here, on a Supermicro X9SRL-F. It would seem for us that iSCSI is more affected by this than NFS is: Feb 23 12:18:20 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 12:18:20 <fileserver> kernel: em1: link state changed to UP Feb 23 12:18:25 <fileserver> kernel: Feb 23 12:18:25 <fileserver> ctld[9389]: <ipaddress>: read: connection lost Feb 23 13:26:55 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 13:26:56 <fileserver> kernel: em0: link state changed to UP Feb 23 13:26:56 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 13:26:59 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): connection error; dropping connection Feb 23 14:46:23 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 14:46:23 <fileserver> kernel: em1: link state changed to UP Feb 23 14:46:24 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 14:46:30 <fileserver> kernel: Feb 23 14:46:30 <fileserver> ctld[36377]: <ipaddress>: read: connection lost Feb 23 15:13:40 <fileserver> kernel: em0: link state changed to UP Feb 23 15:13:40 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 15:20:31 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 23 15:20:31 <fileserver> kernel: em1: link state changed to UP Feb 23 15:20:31 <fileserver> kernel: WARNING: <ipaddress> (<iqn>): no ping reply (NOP-Out) after 5 seconds; dropping connection Feb 22 03:01:36 <fileserver> kernel: em0: Watchdog timeout -- resetting Feb 22 03:01:36 <fileserver> kernel: em0: Queue(0) tdh = 669, hw tdt = 623 Feb 22 03:01:36 <fileserver> kernel: em0: TX(0) desc avail = 32,Next TX to Clean = 655 # pciconf -lvcb em0 em0@pci0:9:0:0: class=0x020000 card=0x000015d9 chip=0x10d38086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82574L Gigabit Network Connection' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xfbe00000, size 131072, enabled bar [18] = type I/O Port, range 32, base 0xa000, size 32, enabled bar [1c] = type Memory, range 32, base 0xfbe20000, size 16384, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) cap 11[a0] = MSI-X supports 5 messages, enabled Table in map 0x1c[0x0], PBA in map 0x1c[0x2000] ecap 0001[100] = AER 1 0 fatal 0 non-fatal 0 corrected ecap 0003[140] = Serial 1 0cc47affff0cc034 FreeBSD 10.1-STABLE #0 r278568M Disabling TSO seems to have stabilized it, for now. /K -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-193802-8-gIKYBWeiDm>