No buffer space available errors
Does anyone have any clue what could cause errors like this? I've been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure there's more information I should be giving, so just let me know what to find. dmesg is at the end. Sep 18 07:56:01 lithium last message repeated 17 times Sep 18 07:56:10 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 07:56:11 lithium dhclient: send_packet: No buffer space available Sep 18 07:56:29 lithium dhclient: send_packet: No buffer space available Sep 18 07:57:55 lithium last message repeated 4 times Sep 18 08:06:30 lithium last message repeated 14 times Sep 18 08:09:16 lithium dhclient: send_packet: No buffer space available Sep 18 08:09:39 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:10:49 lithium dhclient: send_packet: No buffer space available Sep 18 08:11:26 lithium last message repeated 4 times Sep 18 08:13:32 lithium last message repeated 4 times Sep 18 08:18:13 lithium last message repeated 3 times Sep 18 08:23:08 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:23:09 lithium dhclient: send_packet: No buffer space available Sep 18 08:23:30 lithium last message repeated 2 times Sep 18 08:24:31 lithium last message repeated 2 times Sep 18 08:31:00 lithium last message repeated 2 times Sep 18 08:36:37 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:37:10 lithium dhclient: send_packet: No buffer space available Sep 18 08:39:00 lithium dhclient: send_packet: No buffer space available Sep 18 08:41:10 lithium last message repeated 2 times Sep 18 08:50:01 lithium last message repeated 15 times Sep 18 08:50:06 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 08:50:34 lithium dhclient: send_packet: No buffer space available Sep 18 08:51:12 lithium last message repeated 2 times Sep 18 08:53:00 lithium last message repeated 7 times Sep 18 09:03:03 lithium last message repeated 18 times Sep 18 09:03:35 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:04:27 lithium dhclient: send_packet: No buffer space available Sep 18 09:04:57 lithium last message repeated 3 times Sep 18 09:06:50 lithium last message repeated 4 times Sep 18 09:15:35 lithium last message repeated 4 times Sep 18 09:17:04 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:17:20 lithium dhclient: send_packet: No buffer space available Sep 18 09:19:14 lithium dhclient: send_packet: No buffer space available Sep 18 09:21:01 lithium last message repeated 3 times Sep 18 09:30:04 lithium last message repeated 8 times Sep 18 09:30:33 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:32:33 lithium dhclient: send_packet: No buffer space available Sep 18 09:34:36 lithium dhclient: send_packet: No buffer space available Sep 18 09:35:31 lithium dhclient: send_packet: No buffer space available Sep 18 09:42:40 lithium last message repeated 7 times Sep 18 09:44:02 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:45:57 lithium dhclient: send_packet: No buffer space available Sep 18 09:47:17 lithium dhclient: send_packet: No buffer space available Sep 18 09:48:24 lithium last message repeated 3 times Sep 18 09:57:31 lithium last message repeated 25 times Sep 18 09:57:31 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 09:57:51 lithium dhclient: send_packet: No buffer space available Sep 18 09:58:35 lithium last message repeated 2 times Sep 18 10:00:43 lithium last message repeated 3 times Sep 18 10:07:45 lithium last message repeated 4 times Sep 18 10:11:00 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:12:49 lithium dhclient: send_packet: No buffer space available Sep 18 10:21:14 lithium dhclient: send_packet: No buffer space available Sep 18 10:24:29 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:37:58 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto 192.168.91.47: No buffer space available Sep 18 10:41:39 lithium dhclient: send_packet: No buffer space available Sep 18 10:46:54 lithium dhclient: send_packet: No buffer space available Sep 18 10:51:27 lithium timed[27809]: /current/src/usr.sbin/timed/timed/acksend.c 110: sendto
Re: No buffer space available errors
On Mon, 18 Sep 2000, Ben Smithurst wrote: Does anyone have any clue what could cause errors like this? I've been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure there's more information I should be giving, so just let me know what to find. dmesg is at the end. This looks an awful lot like something I was seeing during early testing while adding locking to the mbuf system. Try `netstat -m' to see how many mbuf clusters are allocated. I would guess that the system is unable to allocate clusters reliably. In my case, at the time, I had forgotten to change a pointer dereference to meet the new structure, and thus it just worked out that after allocating the initial amount of clusters, nothing more was possible to allocate. I haven't seen this problem after fixing my mistake, nor before introducing it. None of the work I mentionned has been committed at any point in time (yet), so the problem can only be similar, at best (in any case, a `netstat -m' should offer a clue). Regards, Bosko Milekic [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No buffer space available errors
On Mon, 18 Sep 2000, Ben Smithurst wrote: Does anyone have any clue what could cause errors like this? I've been seeing this sort of stuff since the SMPng commit, IIRC. I'm sure there's more information I should be giving, so just let me know what to find. dmesg is at the end. ... ep0: 3Com 3C509-Combo EtherLink III at port 0x300-0x30f irq 10 on isa0 ep0: Ethernet address 00:a0:24:eb:f4:a2 Run 'netstat -m' when you encounter the problem and email me the results. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: No buffer space available errors
On Wed, 10 Nov 1999, Doug Ambrisko wrote: On one out of 8 machines, I ran into this problem. My network is running at 100BaseTX. I noticed that ifconfig showed OACTIVE flag set and I was running in autosense mode. So I setup the media to 100BaseTX and now it works okay. My guess is the autosense gets confused sometimes. Doug, thanks for the tip, I'll give that a try as I haven't been forcing either card to 10Mbit or TP connections. I have added to the mystery however and this is aggravatingly puzzling. In my previous message I had mentioned that walking away fromt he console for any length of time would cause the machine to generate the "No buffer space" errors. Since then I've turned off my screensaver (Matrix from KDE) and the system has stabilized completely; well almost completely. I can still duplicate the buffer situation and I've still seen it occur when doing fairly high bandwidth (for cable, not for ethernet) file transfers. If I can manage to bring the xfer rate up to around 100K/sec total between inbound and outbound I experience the "Out of buffer" messages within a couple minutes. netstat -m doesn't show anything unusual. I am going to try removing both NMBCLUSTERS and NBUF from my config and just use a maxusers of 128 and see how that goes. --Bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
