RE: ping: sendto: No buffer space available
Dear All,
: --- if_ep.c Fri Feb 1 19:51:43 2002
: +++ if_ep.c.fix Sat Feb 9 12:49:31 2002
: @@ -571,7 +571,6 @@
:
: if (status (S_RX_COMPLETE | S_RX_EARLY)) {
: epread(sc);
: - continue;
: }
: if (status S_TX_AVAIL) {
: /* we need ACK */
Committed this, and a couple other touch-ups to current.
I haven't been experiencing these lockups, but since the most recent buildworld I seem
to have it (once so far, doing a large ports build on an NFS mount to verify).
I looked at the code of if_ep.c and I see that the continue is indeed not there.
Here's the version of if_ep.c that I have:
$FreeBSD: src/sys/dev/ep/if_ep.c,v 1.95.2.3 2002/03/06 07:26:35 imp Exp $
This is a 3com Ethlerlink III pccard thingy, by the way.
angua% uname -a
FreeBSD angua.research.kpn.com 4.7-STABLE FreeBSD 4.7-STABLE #20: Thu Feb 6 12:12:56
CET 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ANGUA i386
angua% ifconfig ep0
ep0: flags=a843UP,BROADCAST,RUNNING,SIMPLEX,LINK1,MULTICAST mtu 1500
inet blotted out netmask 0xf800 broadcast 139.63.199.255
ether 00:60:08:23:20:5d
media: Ethernet 10baseT/UTP
angua% dmesg | grep ep0
ep0: 3Com Etherlink III 3C589 at port 0x240-0x24f irq 11 slot 0 on pccard0
ep0: Ethernet address 00:60:08:23:20:5d
Kees Jan
=
You can't have everything. Where would you put it?
[Steven Wright]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
RE: ping: sendto: No buffer space available
On Thu, 6 Feb 2003 [EMAIL PROTECTED] wrote: I looked at the code of if_ep.c and I see that the continue is indeed not there. AFAIK it needs to be there; at least it solves the hangs I see here. Dw To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
In message: [EMAIL PROTECTED]
Jonathan Hanna [EMAIL PROTECTED] writes:
:
: This looks like the bug in the ep driver. When the interrupt routine
: gets both TX and RX interrupts it acknowledges both but only services
: the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
: but my quick fix is to take out the continue after the epread() in
: ep_intr(). The buffer talked about is actually the ep queue being full.
:
: --- if_ep.c Fri Feb 1 19:51:43 2002
: +++ if_ep.c.fix Sat Feb 9 12:49:31 2002
: @@ -571,7 +571,6 @@
:
: if (status (S_RX_COMPLETE | S_RX_EARLY)) {
: epread(sc);
: - continue;
: }
: if (status S_TX_AVAIL) {
: /* we need ACK */
Committed this, and a couple other touch-ups to current.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
Thanks!
I commented out continue in if_ep.c.
There is no any No buffer space available any more.
Seva.
Jonathan Hanna [EMAIL PROTECTED] writes:
This looks like the bug in the ep driver. When the interrupt routine
gets both TX and RX interrupts it acknowledges both but only services
the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
but my quick fix is to take out the continue after the epread() in
ep_intr(). The buffer talked about is actually the ep queue being full.
--- if_ep.c Fri Feb 1 19:51:43 2002
+++ if_ep.c.fix Sat Feb 9 12:49:31 2002
@@ -571,7 +571,6 @@
if (status (S_RX_COMPLETE | S_RX_EARLY)) {
epread(sc);
- continue;
}
if (status S_TX_AVAIL) {
/* we need ACK */
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
RE: ping: sendto: No buffer space available
On Sat, 9 Feb 2002, Jonathan Hanna wrote:
This looks like the bug in the ep driver. When the interrupt routine
gets both TX and RX interrupts it acknowledges both but only services
the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
but my quick fix is to take out the continue after the epread() in
ep_intr(). The buffer talked about is actually the ep queue being full.
--- if_ep.c Fri Feb 1 19:51:43 2002
+++ if_ep.c.fix Sat Feb 9 12:49:31 2002
@@ -571,7 +571,6 @@
if (status (S_RX_COMPLETE | S_RX_EARLY)) {
epread(sc);
- continue;
}
if (status S_TX_AVAIL) {
/* we need ACK */
If this fix is solid, should it be applied now to the ep driver? Should
we wait until the driver merge is complete? I don't own any cards that
use the ep chipset, but if that change fixes bugs for multiple ep users I
wouldn't be opposed to committing it for you.
Mike Silby Silbersack
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
In message: [EMAIL PROTECTED]
Mike Silbersack [EMAIL PROTECTED] writes:
:
: On Sat, 9 Feb 2002, Jonathan Hanna wrote:
:
:
: This looks like the bug in the ep driver. When the interrupt routine
: gets both TX and RX interrupts it acknowledges both but only services
: the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
: but my quick fix is to take out the continue after the epread() in
: ep_intr(). The buffer talked about is actually the ep queue being full.
:
: --- if_ep.c Fri Feb 1 19:51:43 2002
: +++ if_ep.c.fix Sat Feb 9 12:49:31 2002
: @@ -571,7 +571,6 @@
:
: if (status (S_RX_COMPLETE | S_RX_EARLY)) {
: epread(sc);
: - continue;
: }
: if (status S_TX_AVAIL) {
: /* we need ACK */
:
: If this fix is solid, should it be applied now to the ep driver? Should
: we wait until the driver merge is complete? I don't own any cards that
: use the ep chipset, but if that change fixes bugs for multiple ep users I
: wouldn't be opposed to committing it for you.
I have ep ISA and PC Card devices. I can take the point on testing
it. I figure that at least the PC Card should be tested.
Also, Matt Dodd should also be contacted about the ep driver. He was
the maintainer of the ep driver for a long time.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
On Sun, 10 Feb 2002, M. Warner Losh wrote: : If this fix is solid, should it be applied now to the ep driver? Should : we wait until the driver merge is complete? I don't own any cards that : use the ep chipset, but if that change fixes bugs for multiple ep users I : wouldn't be opposed to committing it for you. I have ep ISA and PC Card devices. I can take the point on testing it. I figure that at least the PC Card should be tested. Also, Matt Dodd should also be contacted about the ep driver. He was the maintainer of the ep driver for a long time. Warner Ah, good. I wasn't sure that any committers still used those cards. /me passes the ball to Warner. Mike Silby Silbersack To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
In message: [EMAIL PROTECTED] Mike Silbersack [EMAIL PROTECTED] writes: : Ah, good. I wasn't sure that any committers still used those cards. You'd be surprised how many cards I have... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
On 11-Feb-02 M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Mike Silbersack [EMAIL PROTECTED] writes:
:
: On Sat, 9 Feb 2002, Jonathan Hanna wrote:
:
:
: This looks like the bug in the ep driver. When the interrupt routine
: gets both TX and RX interrupts it acknowledges both but only services
: the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
: but my quick fix is to take out the continue after the epread() in
: ep_intr(). The buffer talked about is actually the ep queue being full.
:
: --- if_ep.c Fri Feb 1 19:51:43 2002
: +++ if_ep.c.fix Sat Feb 9 12:49:31 2002
: @@ -571,7 +571,6 @@
:
: if (status (S_RX_COMPLETE | S_RX_EARLY)) {
: epread(sc);
: - continue;
: }
: if (status S_TX_AVAIL) {
: /* we need ACK */
:
: If this fix is solid, should it be applied now to the ep driver? Should
: we wait until the driver merge is complete? I don't own any cards that
: use the ep chipset, but if that change fixes bugs for multiple ep users I
: wouldn't be opposed to committing it for you.
I have ep ISA and PC Card devices. I can take the point on testing
it. I figure that at least the PC Card should be tested.
Also, Matt Dodd should also be contacted about the ep driver. He was
the maintainer of the ep driver for a long time.
I did send the original message to Matt a couple of days before I mailed
-stable and -hackers. No idea if he got it.
I have not tested extensively, but it has not failed for a period that would
normally see 2-3 lockups.
From my look at the driver the issues I know of are the interrupt problem as above
and a lack of splx(x) if sc-gone in ep_intr(). From Karl: possible impending merge
with the vx driver.
Jonathan Hanna [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
User Seva wrote: I commented out continue in if_ep.c. There is no any No buffer space available any more. If you are missing it, then you can set up a PPP connection, and then unplug your modem and start a ping. (it's still a routing problem). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: ping: sendto: No buffer space available
In message: [EMAIL PROTECTED] Jonathan Hanna [EMAIL PROTECTED] writes: : From my look at the driver the issues I know of are the interrupt : problem as above and a lack of splx(x) if sc-gone in : ep_intr(). From Karl: possible impending merge with the vx driver. That's right. I don't know why it does splbio() inside of the interrupt handler. That makes no sense to me at all as far as I can tell. Matt Dodd has often said that there should be an if_ep_pci and the vx driver can go away at that point Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
ping: sendto: No buffer space available
Some times connections to my host freeze. What buffer ping talks about? ~:# ping p109 ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes --- p109.f434.n5020.z2.fidonet.org ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss ~:# pstat -T 236/1064 files 0M/255M swap space ~:# netstat -m 97/128/4096 mbufs in use (current/peak/max): 49 mbufs allocated to data 48 mbufs allocated to packet headers 17/28/1024 mbuf clusters in use (current/peak/max) 88 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines ~:# ifconfig ep0: flags=8c43UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST mtu 1500 inet 192.168.44.41 netmask 0xff00 broadcast 192.168.44.255 inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 inet 192.168.44.42 netmask 0x broadcast 192.168.44.42 ether 00:a0:24:46:b8:23 media: Ethernet 10baseT/UTP faith0: flags=8000MULTICAST mtu 1500 stf0: flags=0 mtu 1280 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500 inet 192.168.10.202 -- 192.168.3.3 netmask 0xff00 ppp1: flags=8010POINTOPOINT,MULTICAST mtu 1500 ~:# uname -a FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/PP i386 ~:# Seva. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: ping: sendto: No buffer space available
Try increasing your maxsockbuf: kern.ipc.maxsockbuf: 262144 is the default setting, try: sysctl -w kern.ipc.maxsockbuf=384000 [or higher, depending on your RAM and your network usage] There are a bunch of other network buffers you might want to tune as I am sure others will mention. Deepak Jain AiNET -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Saturday, February 09, 2002 2:58 PM To: [EMAIL PROTECTED] Subject: ping: sendto: No buffer space available Some times connections to my host freeze. What buffer ping talks about? ~:# ping p109 ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available ping: sendto: No buffer space available PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes --- p109.f434.n5020.z2.fidonet.org ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss ~:# pstat -T 236/1064 files 0M/255M swap space ~:# netstat -m 97/128/4096 mbufs in use (current/peak/max): 49 mbufs allocated to data 48 mbufs allocated to packet headers 17/28/1024 mbuf clusters in use (current/peak/max) 88 Kbytes allocated to network (2% of mb_map in use) 0 requests for memory denied 0 requests for memory delayed 0 calls to protocol drain routines ~:# ifconfig ep0: flags=8c43UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST mtu 1500 inet 192.168.44.41 netmask 0xff00 broadcast 192.168.44.255 inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1 inet 192.168.44.42 netmask 0x broadcast 192.168.44.42 ether 00:a0:24:46:b8:23 media: Ethernet 10baseT/UTP faith0: flags=8000MULTICAST mtu 1500 stf0: flags=0 mtu 1280 lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4 inet 127.0.0.1 netmask 0xff00 ppp0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500 inet 192.168.10.202 -- 192.168.3.3 netmask 0xff00 ppp1: flags=8010POINTOPOINT,MULTICAST mtu 1500 ~:# uname -a FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26 22:47:45 MSK 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/PP i386 ~:# Seva. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
RE: ping: sendto: No buffer space available
This looks like the bug in the ep driver. When the interrupt routine
gets both TX and RX interrupts it acknowledges both but only services
the read. Karl Dietz, [EMAIL PROTECTED] is working on an overhaul
but my quick fix is to take out the continue after the epread() in
ep_intr(). The buffer talked about is actually the ep queue being full.
--- if_ep.c Fri Feb 1 19:51:43 2002
+++ if_ep.c.fix Sat Feb 9 12:49:31 2002
@@ -571,7 +571,6 @@
if (status (S_RX_COMPLETE | S_RX_EARLY)) {
epread(sc);
- continue;
}
if (status S_TX_AVAIL) {
/* we need ACK */
Karl Dietz [EMAIL PROTECTED]
On 09-Feb-02 [EMAIL PROTECTED] wrote:
Some times connections to my host freeze.
What buffer ping talks about?
~:# ping p109
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
ping: sendto: No buffer space available
PING p109.f434.n5020.z2.fidonet.org (192.168.44.109): 56 data bytes
--- p109.f434.n5020.z2.fidonet.org ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
~:# pstat -T
236/1064 files
0M/255M swap space
~:# netstat -m
97/128/4096 mbufs in use (current/peak/max):
49 mbufs allocated to data
48 mbufs allocated to packet headers
17/28/1024 mbuf clusters in use (current/peak/max)
88 Kbytes allocated to network (2% of mb_map in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
~:# ifconfig
ep0: flags=8c43UP,BROADCAST,RUNNING,OACTIVE,SIMPLEX,MULTICAST mtu 1500
inet 192.168.44.41 netmask 0xff00 broadcast 192.168.44.255
inet6 fe80::2a0:24ff:fe46:b823%ep0 prefixlen 64 scopeid 0x1
inet 192.168.44.42 netmask 0x broadcast 192.168.44.42
ether 00:a0:24:46:b8:23
media: Ethernet 10baseT/UTP
faith0: flags=8000MULTICAST mtu 1500
stf0: flags=0 mtu 1280
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
inet 127.0.0.1 netmask 0xff00
ppp0: flags=8051UP,POINTOPOINT,RUNNING,MULTICAST mtu 1500
inet 192.168.10.202 -- 192.168.3.3 netmask 0xff00
ppp1: flags=8010POINTOPOINT,MULTICAST mtu 1500
~:# uname -a
FreeBSD f434.n5020.z2.fidonet.org 4.4-STABLE FreeBSD 4.4-STABLE #1: Wed Dec 26
22:47:45 MSK 2001 [EMAIL PROTECTED]
et.org:/usr/src/sys/compile/PP i386
~:#
Seva.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
Jonathan Hanna [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-hackers in the body of the message
