On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote:
> During this time the OACTIVE flag stays there all the time?
Yes.
>
> Which FreeBSD version?
>
This is 4.1.1-RELEASE.
> What is the dmesg line for the ep card you have? [grep ep0
> /var/run/dmesg.boot]
ep0: <3Com 3C509-TP EtherLink III> at
[Bill Paul and Matthew Dodd cc:'d.
Sorry for this intrusion guys, but I just want you opinions on some of
the blabbering I exclaim]
-On [20010218 21:37], Dan Debertin ([EMAIL PROTECTED]) wrote:
>On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote:
>
>> -On [20010216 16:00], Dan Debertin ([EMAIL P
On Sun, 18 Feb 2001, Jeroen Ruigrok/Asmodai wrote:
> -On [20010216 16:00], Dan Debertin ([EMAIL PROTECTED]) wrote:
> >flags=8c43 mtu 1500
>
> OK, so it is setting the output active flag and quite possibly never
> returns from that state.
Quite so.
>
> Hmmm, if you don't do an ifconfig down/up
-On [20010216 16:00], Dan Debertin ([EMAIL PROTECTED]) wrote:
>flags=8c43 mtu 1500
OK, so it is setting the output active flag and quite possibly never
returns from that state.
Hmmm, if you don't do an ifconfig down/up or just up it won't come back,
right? I mean, you can sit it there for days
On Sat, 17 Feb 2001, Bosko Milekic wrote:
> If you have one of these cards, let me know and I'll send you a diff
> off-list.
No, it's none of those; It's a 3c509 isa card. FWIW, I have six of them
laying about, and they all display the same behavior.
~Dan D.
--
++ Dan Debertin
++ Senior System
What type of card is this, exactly? (i.e. name, model number, etc.)
There is some trickery in the NetBSD driver that involves
"Vortex-based (3c59x pci, eisa) and Boomerang (3c900)" which allow
FDDI-sized 4500 byte packets. According to the NetBSD driver's
comments, these cards commands dealing wi
Okay, one more clue. When it's working, the interface flags are as
follows:
flags=8843 mtu 1500
And when it stops, the OACTIVE flag is added:
flags=8c43 mtu 1500
Dan Debertin
--
++ Unix is the worst operating system, except for all others.
++ Dan Debertin
++ Senior Systems Administrator
++ Bi
On Thu, 15 Feb 2001, Dan Debertin wrote:
> Sure thing. Here's what I get when I add that #define:
>
> ../../dev/ep/if_ep.c: In function `ep_attach':
> ../../dev/ep/if_ep.c:325: structure has no member named `rx_bpf_disc'
> ../../dev/ep/if_ep.c: In function `ep_intr':
> ../../dev/ep/if_ep.c:591: w
On Fri, 16 Feb 2001, Bosko Milekic wrote:
> Can you try placing a "#define EP_LOCAL_STATS" at the _top_ of
> if_epvar.h and rebuilding+reinstalling the ep driver? See if you get
> anything printed to the console from the ep driver. If you get
> something that begins with "Status:" then look u
Dan Debertin wrote:
> I have a busy 4.1.1-RELEASE nfs server that stops responding at its
ep
> interface every hour or so. Pings to hosts on that network respond
with
> "sendto: no buffer space available". I've recompiled with MAXUSERS
up at
> 128 and NMBCLUSTERS at 32768, both of which seem ple
I have a busy 4.1.1-RELEASE nfs server that stops responding at its ep
interface every hour or so. Pings to hosts on that network respond with
"sendto: no buffer space available". I've recompiled with MAXUSERS up at
128 and NMBCLUSTERS at 32768, both of which seem plenty high. The problem
goes awa
11 matches
Mail list logo