Problem on re0

[Sami Halabi]

Hi,

the patch failed, As i see /usr/src/dev/re/if_re.c has the following  at
line 1943:
               if (rxstat & RL_RDESC_STAT_RXERRSUM && !(total_len > 8191 &&
                    (rxstat & RL_RDESC_STAT_ERRS) == RL_RDESC_STAT_GIANT)) {
                        ifp->if_ierrors++;
                        /*
                         * If this is part of a multi-fragment packet,
                         * discard all the pieces.
                         */
                        if (sc->rl_head != NULL) {
                                m_freem(sc->rl_head);
                                sc->rl_head = sc->rl_tail = NULL;
                        }
                        re_discard_rxbuf(sc, i);
                        continue;
                }

these are sources for 8.2-R+p4

Sami

On Wed, Dec 7, 2011 at 2:59 AM, YongHyeon PYUN <pyunyh at gmail.com> wrote:

> On Mon, Dec 05, 2011 at 01:53:03PM +0200, Sami Halabi wrote:
> > Hi,
> > Dmesg:
> >
> > re0: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port
> > 0x9000-0x90ff mem 0xf4000000-0xf40000ff irq 16 at device 6.0 on pci1
> > re0: Chip rev. 0x10000000
> > re0: MAC rev. 0x00000000
> > miibus0: <MII bus> on re0
> > rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
> > rgephy0:  10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX,
> > 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX,
> > 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master,
> auto,
> > auto-flow
> > re0: Ethernet address: 00:a1:b0:69:15:5d
> > re0: [FILTER]
> > re1: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port
> > 0x9400-0x94ff mem 0xf4001000-0xf40010ff irq 17 at device 7.0 on pci1
> > re1: Chip rev. 0x10000000
> > re1: MAC rev. 0x00000000
> > miibus1: <MII bus> on re1
> > rgephy1: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus1
> > rgephy1:  10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
> 100baseTX-FDX,
> > 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX,
> > 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master,
> auto,
> > auto-flow
> > re1: Ethernet address: 00:a1:b0:69:76:28
> > re1: [FILTER]
> >
>
> Thanks for the info.
>
> > ------------------------------------------------
> > here is "sysctl dev.re.0.stats=1" output:
> > Dec  5 14:58:27 mpd kernel: re0 statistics:
> > Dec  5 14:58:27 mpd kernel: Tx frames : 15790052
> > Dec  5 14:58:27 mpd kernel: Rx frames : 11847483
> > Dec  5 14:58:27 mpd kernel: Tx errors : 0
> > Dec  5 14:58:27 mpd kernel: Rx errors : 10378
> > Dec  5 14:58:27 mpd kernel: Rx missed frames : 0
> > Dec  5 14:58:27 mpd kernel: Rx frame alignment errs : 0
> > Dec  5 14:58:27 mpd kernel: Tx single collisions : 0
> > Dec  5 14:58:27 mpd kernel: Tx multiple collisions : 0
> > Dec  5 14:58:27 mpd kernel: Rx unicast frames : 11847483
> > Dec  5 14:58:27 mpd kernel: Rx broadcast frames : 0
> > Dec  5 14:58:27 mpd kernel: Rx multicast frames : 0
> > Dec  5 14:58:27 mpd kernel: Tx aborts : 0
> > Dec  5 14:58:27 mpd kernel: Tx underruns : 0
>
> The MAC statistics do not show detailed information for RX errors.
> :-(
>
> >
> > here is current netstat:
> > Name    Mtu Network       Address              Ipkts Ierrs Idrop
> Ibytes
> >    Opkts Oerrs     Obytes  Coll
> > re0    1500 <Link#1>      00:a1:b0:69:15:5d 294056550   280     0
> > 86154803011 420449814     0 350472123744     0
>
> Because driver updated if_ierrors counter, could you apply attached
> patch and let me know what values can you see on your console?
>
> >                           01:00:5e:00:00:01      261
> >   0
> > re0    1500 188.64.96.4/3 5.1886496.royalsh      435     -     -
>  35076
> > 420439431     - 344585787536     -
> > re1*   1500 <Link#2>      00:a1:b0:69:76:28        0     0     0
>  0
> >        0     0          0     0
> >
> > i had in the last 36 hours 7 time card stuck and ifconfig down/up...
> >
> > >When you notice the controller is in stuck condition, could you
> > >check which part(either TX or RX or both) of controller does not
> > >work?
> > how i can output that?
> >
>
> There is no knob to know that.  You should be able to send some
> packets from the box when you know the controller is in stuck
> condition which may not be available option if the box is not on
> your desk.
>
> If you can access the box when its network is in stuck condition,
> try sending ICMP ECHO requests from re(4) host to other box in the
> LAN. And use tcpdum on the other box to know whether it can see the
> packets.  If you can see ICMP ECHO requests, this means TX still
> works. For RX, send some packets to re(4) host and see whether re(4)
> can see these packets.
>



-- 
Sami Halabi
Information Systems Engineer
NMS Projects Expert