dhclient: send_packet: No buffer space available
Hello, Since I have updated my netbook to r255948 I see from time to time in the console the message: Nov 1 16:20:28 tiny-r255948 dhclient[696]: send_packet: No buffer space available The WLAN for the rest works fine without any problem or hick-ups and dhclient always gets and assigns the IP to the wlan0 (ath0) interface. Any idea? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: www.asciiribbon.org E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X - No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards ___ 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: dhclient: send_packet: No buffer space available
On Fri, Nov 1, 2013 at 8:32 AM, Matthias Apitz g...@unixarea.de wrote: Hello, Since I have updated my netbook to r255948 I see from time to time in the console the message: Nov 1 16:20:28 tiny-r255948 dhclient[696]: send_packet: No buffer space available Yes, this is a knownish issue which doesn't _seem_ to cause any other side-effects but its getting annoying now. I also see a lot of them lately. I do not think this has been tracked down yet. Cheers, Hiren ___ 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: dhclient: send_packet: No buffer space available
On 1 November 2013 08:45, hiren panchasara hiren.panchas...@gmail.com wrote: On Fri, Nov 1, 2013 at 8:32 AM, Matthias Apitz g...@unixarea.de wrote: Hello, Since I have updated my netbook to r255948 I see from time to time in the console the message: Nov 1 16:20:28 tiny-r255948 dhclient[696]: send_packet: No buffer space available Yes, this is a knownish issue which doesn't _seem_ to cause any other side-effects but its getting annoying now. I also see a lot of them lately. I do not think this has been tracked down yet. Well, the first thing to establish is whether it's occuring in net80211 or the driver. I _think_ it's a net80211 problem, where dhclient is sending a frame to an interface that isn't yet ready. It's yet another race condition that I must've uncovered when I made the switch to if_transmit() in net80211. Yes, I'd love it if someone looked into it for me. :) -adrian ___ 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
