Summary: | em(4) network link state flapping after 11.2 upgrade | ||
---|---|---|---|
Product: | Base System | Reporter: | steven_nikkel |
Component: | kern | Assignee: | Eugene Grosbein <eugen> |
Status: | Closed DUPLICATE | ||
Severity: | Affects Only Me | CC: | eugen, sbruno, tomek |
Priority: | --- | Keywords: | IntelNetworking, regression |
Version: | 11.2-RELEASE | ||
Hardware: | amd64 | ||
OS: | Any |
Description
steven_nikkel
2018-09-05 01:52:12 UTC
Hi, it seems to be, a problem looks at similar on my case: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231169 from intel manual, try this: Important system configuration changes: --------------------------------------- When there is a choice run on a 64bit OS rather than 32, it makes a significant difference in improvement. The interface can generate high number of interrupts. To avoid running into the limit set by the kernel, adjust hw.intr_storm_threshold setting using sysctl: sysctl hw.intr_storm_threshold=9000 (the default is 1000) For this change to take effect on boot, edit /etc/sysctl.conf and add the line: hw.intr_storm_threshold=9000 If you still see Interrupt Storm detected messages, increase the limit to a higher number. Best throughput results are seen with a large MTU; use 9000 if possible. Weird behaviour today. I left the cable unplugged over night. Plugged it in this morning and the interface worked properly. It worked fine for an hour while I watched and poked at it, passed IPv6 packets fine, picked up IPv4 DHCP, forgot to test otherwise. Then I downed the realtek interface and things seemed to stop working on the intel interface as well. Downed and upped the intel interface and it came back to life, but the link state flapping started again. Trying all the usual things isn't making it go away again either. Per Compri, I am using 64bit OS, not seeing Interrupt Storm messages, don't think it's interrupt rate related as there is hardly any traffic flowing when this starts, but I did try upping the setting, which had no effect. Tried a different 82574 card I had and the behaviour was the same. As you use DHCP, this problem seems to be duplicate of already resolved problem https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229432. Take a look for a workaround and solution. Close per comment 5 @Steven Please re-open this issue with additional information if the workaround described in bug 229432 does not resolve the problem. *** This bug has been marked as a duplicate of bug 229432 *** |