who do I report this to?
pyunyh at gmail.com
Tue Nov 20 20:32:48 PST 2007
On Tue, Nov 20, 2007 at 10:57:08PM -0500, Aryeh M. Friedman wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Aryeh M. Friedman wrote:
> > Pyun YongHyeon wrote:
> >> On Tue, Nov 20, 2007 at 02:11:42AM -0500, Aryeh M. Friedman
> >> wrote:
> >>> Who do I report the following issue to (it falls into at least
> >>> 3 camps)?
> >>> If I am downloading a torrent in deluge 0.5.6.2_1 *AND* am
> >>> logged into gmail (*WITH* a chat open) my network connection
> >>> looses about 90% of it's capacity (for all applications), re(4)
> >>> with the following:
> >>> rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on
> >>> miibus0 rgephy0: 10baseT, 10baseT-FDX, 100baseTX,
> >>> 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> >>> After some experimenting this problem *only* occurs under the
> >>> above conditions.
> >>> Addtional info:
> >>> gnome 2.20.1 nv driver (latest) Xorg 7.3
> >> Would you show me more details(network configuration)? Since
> >> re(4) is involved here I'd like to know what caused the issue. If
> >> you disable checksum offload does it get better
> >> performance?(#ifconfig re0 -txcsum)
> I am going to reboot to see if this clears but I noticed this
You don't need to reboot at all after chainging checksum offload
configuration. Does re(4) spit some messages like watchdog timeout?
If not I have no clue yet.
> happening also:
> monster# !!
> cvsup -h cvsup10.us.freebsd.org /usr/share/examples/cvsup/cvs-supfile
> Connected to cvsup10.us.freebsd.org
> Updating collection src-all/cvs
> Edit src/lib/libc/rpc/key_prot_xdr.c,v
> Edit src/lib/libc/rpc/rpc_callmsg.c,v
> Edit src/lib/libc/rpc/rpc_prot.c,v
> Edit src/lib/libc/rpc/rpcb_prot.c,v
> Edit src/lib/libc/rpc/rpcb_st_xdr.c,v
> Edit src/lib/libdisk/libdisk.h,v
> Edit src/lib/libgssapi/Makefile,v
> Edit src/lib/libkse/Makefile,v
> TreeList failed: Network write failure: Connection closed
Sorry, I don't know Modular3 language, so I don't know what socket
operation was failed. If remote end closed the connection it wouldn't
be fault of re(4). You can check it with tcpdump.
> Will retry at 23:00:29
More information about the freebsd-current