From owner-freebsd-stable Wed Jan 29 9:54:52 2003 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6938037B405 for ; Wed, 29 Jan 2003 09:54:50 -0800 (PST) Received: from jellema.erje.net (cust.8.147.adsl.cistron.nl [62.216.8.147]) by mx1.FreeBSD.org (Postfix) with ESMTP id 258B543F75 for ; Wed, 29 Jan 2003 09:54:35 -0800 (PST) (envelope-from robertj@wirehub.nl) Received: from susie.erje.net (susie.erje.net [192.168.1.66]) by jellema.erje.net (Postfix Version 2.0 Patchlevel 0.3) with ESMTP id A90212D0C09 for ; Wed, 29 Jan 2003 18:54:33 +0100 (CET) Received: from chelsea.basta-matic.org (chelsea.basta-matic.org [172.16.1.63]) by susie.erje.net (8.12.7/8.12.7) with SMTP id h0THsQZZ070555 for ; Wed, 29 Jan 2003 18:54:26 +0100 (CET) Received: (qmail 82571 invoked from network); 29 Jan 2003 17:54:25 -0000 Received: from chelsea.basta-matic.org (172.16.1.63) by chelsea.basta-matic.org with SMTP; 29 Jan 2003 17:54:25 -0000 Date: Wed, 29 Jan 2003 18:54:25 +0100 (CET) From: Robert Joosten X-X-Sender: robert@chelsea.basta-matic.org To: "Peter N. M. Hansteen" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: bizarre ep (3c509-Combo) behavior: one and a half init, minimal throughput In-Reply-To: <87fzrc3tly.fsf@tosh.datadok.no> Message-ID: References: <87fzrc3tly.fsf@tosh.datadok.no> X-message-flag: Faultlook: This message generated an unprotected fpu re-allocation at 0x323 diagnoses is dumped to %WINDIR/%APPLOG MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-erje.net-MailScanner: OK, found to be clean Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, > ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 5 on isa0 > ep0: Ethernet address 00:a0:24:ca:7c:b0 > then once more as > ep1: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 5 on isa0 > ep1: No I/O space?! > ep1: ep_alloc() failed! (6) > There is only one network card in the machine, I promise! I know these ep's, they're supported but only work so-so. I found out you must keep the order your kernel-config lists them intact (that's ed0, then ex, and then ep, followed by fe0) and also man keep that fe0 following the ep device. I experimented with this (read: wasted a lot of time) to figure out what and how. I'm running a old '486 running 4.7R with two ep's: Jan 29 13:01:42 t2ja /kernel: ep0: <3Com 3C509-TPO EtherLink III> at port 0x300-0x30f irq 10 on isa0 Jan 29 13:01:42 t2ja /kernel: ep0: Ethernet address 00:20:af:b8:96:8c Jan 29 13:01:42 t2ja /kernel: ep1: <3Com 3C509-TPO EtherLink III> at port 0x310-0x31f irq 11 on isa0 Jan 29 13:01:42 t2ja /kernel: ep1: Ethernet address 00:60:08:c6:a2:77 with only some minor issues: blasting a lot of traffiq through it causes some mbuff trouble which degardes performace to nearly zero, I always shut the interface down, wait a few seconds and the throw it up again. As long as the interface's not threated, performance keeps suffering lasting for hours and maybe days...! A precursor is the appearance of OACTIVE in the ifconfig output regarding that interface. One sysadmin I know told me 3com released various series of these cards. The most recent models suppose to run flawlessly under *nix. The earliest models should be avoided. Windows doesn't care at all. And yes: I know from 1st hand experience Linux supports these cards very well (They did a wonderfull job on my 386xs/25 running Slackware 3.9 (kernel 2.0.37). Rj To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message