re interface broken

[Pyun YongHyeon]

On Thu, Aug 03, 2006 at 10:58:50AM +0200, Gerrit K?hn wrote:
 > On Thu, 3 Aug 2006 09:26:15 +0900 Pyun YongHyeon <pyunyh at gmail.com> wrote
 > about Re: re interface broken:
 > 
 > >  > today, the interface still doesn't work. Is there work going on to
 > >  > fix this, can I provide further information to track this problem
 > 
 > > I think you should show 'dmesg' and 'pciconf -lv' output first.
 > 
 > Here they are:
 > 

[...]

 > re0 at pci2:1:0:	class=0x020000 card=0x08600e11 chip=0x813910ec
 > rev=0x20 hdr=0x00 vendor   = 'Realtek Semiconductor'
 >     device   = 'RT8139 (A/B/C/810x/813x/C+) Fast Ethernet Adapter'
 >     class    = network
 >     subclass = ethernet

[...]
 > re0: Reserved 0x100 bytes for rid 0x10 type 4 at 0x2000
 > pcib2: re0 requested I/O range 0x2000-0x20ff: in range
 > re0: <RealTek 8139C+ 10/100BaseTX> port 0x2000-0x20ff mem
 > 0x90300000-0x903000ff irq 10 at device 1.0 on pci2 pcib2: re0 requested
 > I/O range 0x2000-0x20ff: in range miibus0: <MII bus> on re0
 > rlphy0: <RealTek internal media interface> on miibus0
 > rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 > re0: bpf attached
 > re0: Ethernet address: 00:0f:b0:6c:55:ec
 > re0: [MPSAFE]
 > re0: [FAST]


Would you let me know a if_re.c revison number used to work on your
system?
Does Tx/Rx routine on your system work? In order to test it, you
need a known working system and run tcpdump on the system.
Can you see frames sent from your system on good system?
If you know re(4) can send frame without problems, run tcpdump on
your notebook and check whether re(4) can see incoming packets sent
from good packet.

-- 
Regards,
Pyun YongHyeon