Date: Tue, 7 Dec 1999 10:22:19 -0500 From: Greg Lehey <grog@mojave.sitaranetworks.com> To: "Niels Chr. Bank-Pedersen" <ncbp@bank-pedersen.dk>, FreeBSD mobile Mailing List <freebsd-mobile@FreeBSD.ORG> Subject: Re: 3c589d w/ freebsd 3.3 works badly. Message-ID: <19991207102219.22780@mojave.sitaranetworks.com> In-Reply-To: <19991207160848.A27105@bank-pedersen.dk>; from Niels Chr. Bank-Pedersen on Tue, Dec 07, 1999 at 04:08:49PM %2B0100 References: <199912060251.NAA16461@cairo.anu.edu.au> <199912062312.QAA37583@harmony.village.org> <19991206210033.19522@mojave.sitaranetworks.com> <19991207160848.A27105@bank-pedersen.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday, 7 December 1999 at 16:08:49 +0100, Niels Chr. Bank-Pedersen wrote: > On Mon, Dec 06, 1999 at 09:00:33PM -0500, Greg Lehey wrote: >> [Moved to FreeBSD-mobile] >> >> On Monday, 6 December 1999 at 16:12:49 -0700, Warner Losh wrote: >>> In message <199912060251.NAA16461@cairo.anu.edu.au> Darren Reed writes: >>> : How reliable should the ep0 driver be with 3c389d pcmcia cards ? >>> >>> I had no problems using 3.3 and my 3C589D, but I've only done minor >>> stuff with that. I've done most of my work on -current, however. The >>> most likely problem is that you're using the wrong IRQ for the card. >>> You'll want to check /etc/rc.conf to make sure that you are using the >>> /etc/pccard.conf file. Also, you'll want to make sure that the irq >>> line is correct. >> >> I don't know if this is the same issue, but I've seen terrible write >> performance on my 3C589C under -CURRENT, and so has phk. Read >> performance is OK. Looking at the hub, I see a short burst of >> activity and then nothing for the rest of a second. This repeats >> itself in this manner. No errors, but a write throughput of less than >> 50 kB/s. I've seen this before recent changes in -CURRENT, but it >> seems worse now (or maybe I've just paid more attention to it now :-). > > I've seen something similar - turned out to be changes in the pcm > detection that resulted in irq conflicts (as mentioned above). > After I hardwired irg/drq in my kernel, the problem was gone... Did this result in this one-second delay only on writes? I would expect that the behaviour in the case of interrupt conflicts would be the same for reads and writes, and it would occur on just about every packet, not allowing 30 or 50 out and then delaying for a significant period of time. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991207102219.22780>