Date: Mon, 24 Oct 2005 19:30:40 +0200 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@FreeBSD.org> To: Matthias Andree <matthias.andree@gmx.de> Cc: freebsd-current@FreeBSD.org Subject: Re: 6.0-RC1: ral(4) driver broken? network interruptions Message-ID: <681F27CD-851B-4901-AE65-C2AF4C1960CB@FreeBSD.org> In-Reply-To: <m34q764yxl.fsf@merlin.emma.line.org> References: <m34q764yxl.fsf@merlin.emma.line.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 24/10/2005, at 19:17, Matthias Andree wrote: > Greetings, > > I have an oldish computer VIA KT333/Athlon XP board (i386) that I > recently upgraded from FreeBSD 5.4 (was rock solid) to 6.0-BETA3 and > today to 6.0-RC1 (I rebuilt everything from scratch). > > I had to upgrade because there was no ral(4) driver for FreeBSD 5.4 =20= > but > only for 6.0, which I needed after I had switched from 3C900 Combo > (802.3 whatever 10Base2) to Edimax EW-7128g (802.11b/g). The latter =20= > card > is based on RT2525 and RT2560 chips/modules. I'm using WPA-TKIP to > connect it to an AVM Fritz!Box Fon WLAN. > > The computer is dual boot with SUSE Linux 9.3, where RA card is > absolutely stable and does 48 Mbps without trouble. > > Booting FreeBSD 6.0-BETA3 or -RC1, I constantly see lines like these > from cvsup running on FreeBSD: > > Parsing supfile "/usr/share/examples/cvsup/ports-supfile" > Connecting to cvsup7.de.FreeBSD.org > Connected to cvsup7.de.FreeBSD.org > Server software version: SNAP_16_1g > Negotiating file attribute support > Exchanging collection information > Establishing multiplexed-mode data connection > Running > TreeList failed: Network write failure: Connection closed > Will retry at 19:10:59 > > and in my ssh client (running on Linux, logging in to that FreeBSD > machine), with varying numbers: > > Disconnecting: Bad packet length 3626208547. > > Something in TKIP, WLAN or ral appears to be hosed. Anyone else =20 > seeing this? Yes I see the same thing with iwi, it looses connection now and then. =20= Heavy traffic alone doesn't do it, but starting VNCviewer kills it =20 every time. A killall -1 wpa_supplicant gets the connection back on =20 track... Other end here is a Dlink DI624+ so the mix is totally different from =20= yours... S=F8ren Schmidt sos@FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?681F27CD-851B-4901-AE65-C2AF4C1960CB>