netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ville Herva <vherva@v.iki.fi>
To: netdev@vger.kernel.org
Subject: 2.6.17-rc1: ping: sendmsg: No buffer space available
Date: Fri, 5 May 2006 09:39:50 +0300	[thread overview]
Message-ID: <20060505063950.GA6538@v.iki.fi> (raw)
In-Reply-To: <20050606224729.B12034@flint.arm.linux.org.uk>

I don't know if 
http://bugzilla.kernel.org/show_bug.cgi?id=4615
has been solved yet, but I'm seeing a similar thing with 2.6.17-rc1 and a ppp
connection over ssh.

Earlier kernels (at least linux-2.6.14-rc4) did not show this with the
exactly same settings.

How it happens: 
 - open up the ppp connection over ssh.
 - stress it a bit with samba
 - after a few minutes, pinging the remote end gives
     ping: sendmsg: No buffer space available
   and I have to re-establish the connection

The ssh connection seems solid afaict. Also, with bare ssh connetion, no
problems occur even under load. The ppp connection seems prone to hang
especially with SMB traffic (don't know why.)

In dmesg, there seems to be nothing relevant. /proc/slabinfo doesn't seem to
to have anything alerting in it.

The underlying connection is ADSL (8/1Mbit). The driver is eepro100. ppp is
ppp-2.4.3-6.2.1. 

ppp_deflate is in use:

ppp_deflate             5536  3 
zlib_deflate           18360  1 ppp_deflate
bsd_comp                5312  0 
ppp_async               9664  2 
crc_ccitt               1952  1 ppp_async
ppp_generic            20468  11 ppp_deflate,bsd_comp,ppp_async



      parent reply	other threads:[~2006-05-05  6:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-06 21:47 Fwd: [Bug 4615] Modem connection stalls out Russell King
2005-06-06 23:19 ` Herbert Xu
2006-05-05  6:39 ` Ville Herva [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060505063950.GA6538@v.iki.fi \
    --to=vherva@v.iki.fi \
    --cc=Ville.Herva@iki.fi \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).