From owner-freebsd-mobile Sat Oct 14 17:26: 1 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from sianna.shopkeeper.de (sianna.shopkeeper.de [195.27.246.228]) by hub.freebsd.org (Postfix) with ESMTP id 5C58237B66D for ; Sat, 14 Oct 2000 17:25:58 -0700 (PDT) Received: from avalon.ibd-web.de (dialin.shopkeeper.de [195.27.246.233]) by sianna.shopkeeper.de (8.11.0/8.11.0) with ESMTP id e9F0Poi57177; Sun, 15 Oct 2000 02:25:54 +0200 (CEST) (envelope-from sklauder@ibd-web.de) Received: (from sklauder@localhost) by avalon.ibd-web.de (8.11.0/8.11.0) id e9F0G9L00742; Sun, 15 Oct 2000 02:16:09 +0200 (CEST) (envelope-from sklauder) From: Sascha Klauder Message-Id: <200010150016.e9F0G9L00742@avalon.ibd-web.de> Subject: Re: "device timeout" with DFE-650 To: kkonstan@duth.gr Date: Sun, 15 Oct 2000 02:16:09 +0200 (CEST) Cc: freebsd-mobile@FreeBSD.ORG In-Reply-To: <39E8C70A.4E5F8160@webdaemon.net> from "Konstantinos Konstantinidis" at Okt 14, 2000 11:50:18 pm X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org +-- on Sat Oct 14 22:50:18 2000, Konstantinos Konstantinidis wrote: --- | I have exactly the same symptoms with my xircom. it was working perfectly | for several months with 4.0-STABLE, but when I upgraded to 4.1.1 it | started behaving this way. Needless to say, I'm pissed :) Well, with some help from Sean O'Connell I solved my problem recently. It is/was some problem with media sense and/or duplex mismatches. The card now runs perfectly smooth, but only on one of the three hubs I have access to and only at 100Mbps/half duplex. Most notably, this is not a D-Link hub (the two others are made by D-Link). | I am relieved to find out that it doesn't only affect the xircoms, since | nothing relevant chagned on the xircom driver since 4.0 and I was really | lost trying to figure out where the breakage was - I am now convinced that | something somewhere else is really, really broken. I'm sorry to hear that your card does no longer work, but beforehand, I had tried 3.4-STABLE, 4.0-RELEASE and 4.1-STABLE and I had the same problems with any of these so I don't think it's necessarily a problem with FreeBSD. Although, AFAIK the ed(4) driver is quite monolithic and has no MII bus code (yet?). | Consider giving 4.0 a try - see if that works - it's not the card that's I'm happily running 4.1.1-STABLE, now that cvsup works (ever copied a FreeBSD source tree tarball over a serial cable at 12Kbps? :) | I made a post regarding this on freebsd-mail last week but it seems to | have been ignored - since then I've been spending all my free time debugging | and can't honestly figure out why for some reason when large flows build | up (so to say) the kernel stops sending packets to the card. If you're really sure that you don't changed anything in your configuration besides updating to 4.1 it is likely to be a software problem. Cheers, -sascha To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message