Subject: Re: pppd "write: No buffer space available"
To: None <netbsd-users@NetBSD.org>
From: Bruce Anderson <brucea@spacestar.net>
List: netbsd-users
Date: 06/15/2004 15:58:56
On Mon, Jun 14, 2004 11:16 PM, Carl Brewer <mailto:carl@bl.echidna.id.au>
wrote:
>Every now and then (week or so) they see the following
>on the console :
>
>Jun 15 11:59:19 fw pppd[165]: write: No buffer space available
>
>And the link seems to die (I can't confirm link death,
>they normally reboot the box, which isn't the right thing to
>do ....).  I haven't been onsite when this has happened,
>so I can't confirm what's going on at the time.
>
>Has anyone seen this before and have any suggestions? 

The line went bad and the modem hungup and then pppd exhausts buffer space.

( On a normal connect I would see: May 28 00:07:30 puma pppd[14749]:
Terminating connection due to lack of activity.
preceding "Connection terminated.")

What I see in my log is this:

May 28 02:35:51 puma pppd[14749]: write: No buffer space available
May 28 02:36:21 puma last message repeated 2 times
May 28 02:36:24 puma pppd[14749]: Modem hangup
May 28 02:36:24 puma pppd[14749]: Connection terminated.
May 28 02:36:24 puma pppd[14749]: Connect time 8.4 minutes.
May 28 02:36:24 puma pppd[14749]: Sent 1831580 bytes, received 10683608
bytes.
May 28 02:36:31 puma pppd[14749]: Starting link
May 28 02:36:32 puma chat[10329]: timeout set to 15 seconds
May 28 02:36:32 puma chat[10329]: send (^N^N^NAT&V1Z!!^M)
May 28 02:36:33 puma chat[10329]: send (+++ATZH0!!^M)
May 28 02:36:33 puma chat[10329]: report (ERROR)
May 28 02:36:33 puma chat[10329]: report (BUSY)
May 28 02:36:33 puma chat[10329]: report (CONNECT)
May 28 02:36:33 puma chat[10329]: report (NO DIAL)
May 28 02:36:33 puma chat[10329]: abort on (ERROR)
May 28 02:36:33 puma chat[10329]: abort on (BUSY)
May 28 02:36:33 puma chat[10329]: abort on (NO CARRIER)
May 28 02:36:33 puma chat[10329]: abort on (NO DIAL)
May 28 02:36:33 puma chat[10329]: expect (OK)
May 28 02:36:33 puma chat[10329]: ^M
May 28 02:36:33 puma chat[10329]: TERMINATION REASON.......... EXCESSIVE
RETRANSMISSIONS^M
May 28 02:36:33 puma chat[10329]: LAST TX rate................ 28800 BPS^M
May 28 02:36:33 puma chat[10329]: HIGHEST TX rate............. 28800 BPS^M
May 28 02:36:33 puma chat[10329]: LAST RX rate................ 28800 BPS^M
May 28 02:36:33 puma chat[10329]: HIGHEST RX rate............. 28800 BPS^M
May 28 02:36:33 puma chat[10329]: PROTOCOL.................... LAPM^M
May 28 02:36:33 puma chat[10329]: COMPRESSION................. V42Bis^M
May 28 02:36:33 puma chat[10329]: Line QUALITY................ 028^M
May 28 02:36:33 puma chat[10329]: Rx LEVEL.................... 028^M
May 28 02:36:33 puma chat[10329]: Highest Rx State............ 67^M
May 28 02:36:33 puma chat[10329]: Highest TX State............ 67^M
May 28 02:36:33 puma chat[10329]: EQM Sum..................... 004C^M
May 28 02:36:33 puma chat[10329]: RBS Pattern................. FF^M
May 28 02:36:33 puma chat[10329]: Rate Drop................... FF^M
May 28 02:36:33 puma chat[10329]: Digital Pad................. None^M
May 28 02:36:33 puma chat[10329]: Local Rtrn Count............ 00^M
May 28 02:36:33 puma chat[10329]: Remote Rtrn Count........... 00^M
May 28 02:36:33 puma chat[10329]: V8bis K56Flex fail ^M
May 28 02:36:33 puma chat[10329]: ^M
May 28 02:36:33 puma chat[10329]: OK
May 28 02:36:33 puma chat[10329]:  -- got it 


NetBSD 1.6ZF (GENERIC) #0: Thu Nov 13 17:12:10 CST 2003
        bruce@leopard:/usr/obj/sys/arch/i386/compile/GENERIC
total memory = 127 MB
avail memory = 111 MB
using 1659 buffers containing 6636 KB of memory
BIOS32 rev. 0 found at 0xfb4a0
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: AMD K6-2 (586-class), 451.05 MHz, id 0x58c
cpu0: features 8021bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>