Re: connect() returns EADDRINUSE during massive host->host conn rate
On Tue, Dec 25, 2007 at 01:30:36PM +0300, Maxim Konovalov wrote: > On Fri, 30 Nov 2007, 19:26+0900, Adrian Chadd wrote: > > > Finding out more about the socket thats been created and what its > > clashing with might help. I'd do it myself but I'm not sure how to > > duplicate the issue. > > > Have you tried to turn net.inet.ip.portrange.randomized off? Yes, it didn't change anything. -- Jan Srzednicki :: http://wrzask.pl/ "Remember, remember, the fifth of November" -- V for Vendetta ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: connect() returns EADDRINUSE during massive host->host conn rate
On Fri, 30 Nov 2007, 19:26+0900, Adrian Chadd wrote: > On 30/11/2007, Jan Srzednicki <[EMAIL PROTECTED]> wrote: > > > Most of the relevant sockets (that is, between the two host > > mentioned) are in the ESTABLISHED state (200-400 of those). Only > > 20-40 are in TIME_WAIT state (these tend to be from a more > > ephemeric POP3 service). Most of the EADDRINUSE happen for the > > IMAP4 service. > > I'd probably start by patching the places in the tcp code > (src/sys/netinet/tcp_usrreq.c) which returns this error > (Its returned in other places but that seems to me to be the most > likely from your description.) > > Insert some code to print out information about the current socket and > the "oinp" value returned from in_pcbconnect_setup() (if this is the > place where the error occured.) > > Finding out more about the socket thats been created and what its > clashing with might help. I'd do it myself but I'm not sure how to > duplicate the issue. > Have you tried to turn net.inet.ip.portrange.randomized off? -- Maxim Konovalov ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Maximum NIC interrupts
Hi all, I know how to monitoring the NIC IRQ's consume, with tools as vmstat (-i flag), systat (-vm 1) or netstat (-m, -i), but I don't know how to determine the maximum interrupts that these NICs can give. I've several SuperMicro servers with Intel Pro 1000 PT NICs, which are controlled by em(4) driver. I've done some performance tests (with tools as iperf or netperf) with great results, but I don't know exactly the hardware limits, because I don't know the maximum IRQ rate. Obviously, before post this present message I've read a lot of documentation provided by vendor (Intel in this case) but I've not found it. -- Thanks, Jordi Espasa Clofent ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/118879: [bge] [patch] bge has checksum problems on the 5703 chipset
Synopsis: [bge] [patch] bge has checksum problems on the 5703 chipset State-Changed-From-To: open->analyzed State-Changed-By: kris State-Changed-When: Tue Dec 25 14:11:09 UTC 2007 State-Changed-Why: This is most likely not a bug unless you can confirm the bad checksums from *ANOTHER* machine on the same link. When hardware checksum offload is in use, the OS does not compute the checksum (it happens in the NIC as the packet is transmitted) so tcpdump sees a "wrong" checksum. See the tcpdump manpage. http://www.freebsd.org/cgi/query-pr.cgi?pr=118879 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/117717: [panic] Kernel panic with Bittorrent client.
Synopsis: [panic] Kernel panic with Bittorrent client. Responsible-Changed-From-To: freebsd-net->rwatson Responsible-Changed-By: kris Responsible-Changed-When: Tue Dec 25 14:15:45 UTC 2007 Responsible-Changed-Why: Assign to rwatson at his request http://www.freebsd.org/cgi/query-pr.cgi?pr=117717 ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/117717: [panic] Kernel panic with Bittorrent client.
On Tue, 25 Dec 2007, [EMAIL PROTECTED] wrote: Synopsis: [panic] Kernel panic with Bittorrent client. Responsible-Changed-From-To: freebsd-net->rwatson Responsible-Changed-By: kris Responsible-Changed-When: Tue Dec 25 14:15:45 UTC 2007 Responsible-Changed-Why: Assign to rwatson at his request http://www.freebsd.org/cgi/query-pr.cgi?pr=117717 I'm happy to take a look at this PR, and have installed a 6.3 box with X11 and Deluge, from the RC2 ISOs, for this purpose. However, I've never used Deluge, so sample command lines and configuration files I could use would be very helpfull: [EMAIL PROTECTED]:~> deluge no existing Deluge session Traceback (most recent call last): File "/usr/local/bin/deluge", line 119, in deluge.wizard.WizardGTK() File "/usr/local/lib/python2.5/site-packages/deluge/wizard.py", line 53, in __init__ pixmap = deluge.common.get_logo(48) File "/usr/local/lib/python2.5/site-packages/deluge/common.py", line 156, in get_logo size, size) gobject.GError: Unrecognized image file format Thanks, Robert N M Watson Computer Laboratory University of Cambridge ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: kern/117717: [panic] Kernel panic with Bittorrent client.
Hi Robert, On Tue, Dec 25, 2007 at 11:53:38PM +, Robert Watson wrote: > > On Tue, 25 Dec 2007, [EMAIL PROTECTED] wrote: > > >Synopsis: [panic] Kernel panic with Bittorrent client. > > > >Responsible-Changed-From-To: freebsd-net->rwatson > >Responsible-Changed-By: kris > >Responsible-Changed-When: Tue Dec 25 14:15:45 UTC 2007 > >Responsible-Changed-Why: > >Assign to rwatson at his request > > > >http://www.freebsd.org/cgi/query-pr.cgi?pr=117717 > > I'm happy to take a look at this PR, and have installed a 6.3 box with X11 > and Deluge, from the RC2 ISOs, for this purpose. However, I've never used > Deluge, so sample command lines and configuration files I could use would > be very helpfull: > > [EMAIL PROTECTED]:~> deluge > no existing Deluge session > Traceback (most recent call last): > File "/usr/local/bin/deluge", line 119, in > deluge.wizard.WizardGTK() > File "/usr/local/lib/python2.5/site-packages/deluge/wizard.py", line 53, > in __init__ > pixmap = deluge.common.get_logo(48) > File "/usr/local/lib/python2.5/site-packages/deluge/common.py", line 156, > in get_logo > size, size) > gobject.GError: Unrecognized image file format Thanks for taking a look at this. I've never seen this particular error before; my installation of deluge didn't require any specific configuration, it just started up, presenting me with a dialog-wizard. Is it possible that your deluge installation is corrupt? I would give you a package if I could, but I've moved onto 7-STABLE so that I could use the client. Cheers. -- Jonathan Chen <[EMAIL PROTECTED]> ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "[EMAIL PROTECTED]"
