Hi, I happen to own a D-Link DFE-690TXD cardbus network adapter for my laptop. After reading the comments if_rl.c, I regret to have bought it this "redefinition of low end" :-) With 5.2.1-RELEASE and this card, if_rl hangs in rl_probe() at hwrev = CSR_READ_4(sc, RL_TXCFG) & RL_TXCFG_HWREV; I saw quite some modifications in current for if_rl, so I upgraded last night to current. The good news is that the card now just works: > rl0: <D-Link DFE-690TXD 10/100BaseTX> port 0x1100-0x11ff mem 0x88000000-0x880001ff irq 10 at device 0.0 on cardbus0 > miibus1: <MII bus> on rl0 > rlphy0: <RealTek internal media interface> on miibus1 > rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > rl0: Ethernet address: 00:0d:88:2c:a3:f7 > rl0: [GIANT-LOCKED] Running ttcp over this card showed about 8.5MB/s at the expense of quite some CPU cycles. However, while doing this, I noticed these messages > rl0: discard oversize frame (ether type 800 flags 3 len 21569 > max 1514) > rl0: discard oversize frame (ether type 8001 flags 3 len 4520 > max 1514) > rl0: discard oversize frame (ether type ef27 flags 3 len 32684 > max 1514) > rl0: discard oversize frame (ether type 2f1a flags 3 len 49420 > max 1514) So, if_rl is receiving bogus frames. I'm happy to track this one down but have no clue where to start :-) * is it switch/cable? (it it is fine with the builtin fxp nic or is fxp just ignoring bogus frames without logging?) * is it cardbus or if_rl Any pointers appreciated, Joost -- j_at_joostm.nlReceived on Sun Aug 08 2004 - 09:55:51 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:05 UTC