network hang using intel em nic
Hi, I've got some new hardware and have been experiencing lockups using the em driver. They seem to only happen on large downloads, smaller things like ssh and web browsing work OK. The hardware is: em0@pci0:0:25:0:class=0x02 card=0x309f17aa chip=0x153a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection I217-LM' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xf7c0, size 131072, enabled bar [14] = type Memory, range 32, base 0xf7c3d000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0xf080, size 32, enabled I did have the vboxnet driver loaded, but tried unloading that and still saw the issue. One thing I notice is some garbage at the top of the screen when the hang happens, perhaps there's a conflict with the vesa video. (This system is Haswell, using the vga/vesa driver.) Any suggestions on how to debug? Thanks, Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: network hang using intel em nic
On 2014-09-08 13:14, Steve Wills wrote: Hi, I've got some new hardware and have been experiencing lockups using the em driver. They seem to only happen on large downloads, smaller things like ssh and web browsing work OK. The hardware is: em0@pci0:0:25:0:class=0x02 card=0x309f17aa chip=0x153a8086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = 'Ethernet Connection I217-LM' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xf7c0, size 131072, enabled bar [14] = type Memory, range 32, base 0xf7c3d000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0xf080, size 32, enabled I did have the vboxnet driver loaded, but tried unloading that and still saw the issue. One thing I notice is some garbage at the top of the screen when the hang happens, perhaps there's a conflict with the vesa video. (This system is Haswell, using the vga/vesa driver.) Any suggestions on how to debug? Thanks, Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Try periodically setting dev.em.0.debug=1 it will dump a bunch of stats to syslog then set it self back to -1 there are also a bunch of useful stats under: dev.em.0 including things like: dev.em.0.mbuf_alloc_fail dev.em.0.watchdog_timeouts dev.em.0.mac_stats.collision_count etc that might provide some insight. I have a box with 4x of the i210 (but that shows up as igb(4)) I have one of the i217LM nics in this machine, but it is used for video production so it isn't running BSD at the moment. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: network hang using intel em nic
On Mon, Sep 08, 2014 at 01:29:31PM -0400, Allan Jude wrote: Try periodically setting dev.em.0.debug=1 it will dump a bunch of stats to syslog then set it self back to -1 there are also a bunch of useful stats under: dev.em.0 including things like: dev.em.0.mbuf_alloc_fail dev.em.0.watchdog_timeouts dev.em.0.mac_stats.collision_count etc that might provide some insight. I have a box with 4x of the i210 (but that shows up as igb(4)) I have one of the i217LM nics in this machine, but it is used for video production so it isn't running BSD at the moment. Thanks for the suggestions, I think I may have solved it just by ensuring my kernel modules for vbox and cuse were in sync with the kernel. Steve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
