kernel log messages: sonewconn

[avalon60]

Firts of all, let me say that I know I have had a similar problem before, maybe 2 or 3 years back, but I am not sure what the solution was at that time. Also I have since changed all windows OS to Linux Ubuntu.

For that last few days, I have been getting emails telling me:

sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (8 occurrences)
sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (12 occurrences)
sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (8 occurrences)
sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (10 occurrences)
sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (11 occurrences)
sonewconn: pcb 0xfffff800cb538ae0: Listen queue overflow: 151 already in queue awaiting acceptance (10 occurrences)
arp: 192.168.0.14 moved from 00:25:56:87:13:67 to 00:1f:16:a8:9e:ef on epair1b
and many more of the of the same as above.

The ip of 192.168.0.14 is my laptop, and is connected by an ethernet cable.

Are the said messages anything I sould be concerned about.

 

[sretalla]

I get these daily also and have worked on eliminating them in another thread with no success. I don't think there's anything specifically harmful about them, but I have some theories around having a browser connected to the GUI and putting that PC to sleep being somehow related.

 

[avalon60]

Ok, I know I should have done this before posting, but I didn't.
There is some information here:
https://forums.freenas.org/index.php?threads/freenas-9-2-error-listen-queue-overflow.17774/

And here as well:
https://lists.freebsd.org/pipermail/freebsd-net/2013-July/036017.html

To the mods, my apologies for duplicate posting on a problem that seems well documented, but I didn't think to find out.

 

[sretalla]

To clarify my point (since I see you were reprimanded for using Broadcom NICs), I use only Intel NICs and see the problem on both igb and em drivers.