Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Aug 2015 08:56:30 -0400
From:      Kim Culhan <w8hdkim@gmail.com>
To:        pyunyh@gmail.com
Cc:        Sean Bruno <sbruno@freebsd.org>, freebsd-net@freebsd.org
Subject:   Re: RE not working on 10.2-RELEASE #0 r286731M
Message-ID:  <CAKZxVQXDrkfFOX0QW9=BVZJH0J0zSaet5k4Bp1aXSQR0O41%2BSA@mail.gmail.com>
In-Reply-To: <20150816115623.GA1288@michelle.fasterthan.com>
References:  <CAKZxVQU1_g%2BYf71Z%2BkoGnVW8anH%2Bh3dYhUOducTVP5_p%2Brq0_A@mail.gmail.com> <20150816115623.GA1288@michelle.fasterthan.com>

next in thread | previous in thread | raw e-mail | index | archive | help
The dmesg output:

pci4: <ACPI PCI bus> on pcib3
em0: <Intel(R) PRO/1000 Network Connection 7.4.2> port 0xdc00-0xdc1f mem
0xfe9e0000-0xfe9fffff,0xfe900000-0xfe97ffff,0xfe9dc000-0xfe9dffff irq 17 at
device 0.0 on pci4
em0: Using MSIX interrupts with 3 vectors
em0: Ethernet address: 68:05:ca:12:91:cd
[snip]
pcib5: <ACPI PCI-PCI bridge> irq 16 at device 28.5 on pci0
pci2: <ACPI PCI bus> on pcib5
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port
0xb800-0xb8ff mem 0xf8fff000-0xf8ffffff,0xf8fe0000-0xf8feffff irq 17 at
device 0.0 on pci2
re0: Using 1 MSI-X message
re0: Chip rev. 0x3c000000
re0: MAC rev. 0x00400000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 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: Using defaults for TSO: 65518/35/2048
re0: Ethernet address: 90:e6:ba:c8:52:df
[snip]
pcib6: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci6: <ACPI PCI bus> on pcib6
re1: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet> port
0xe800-0xe8ff mem 0xfebffc00-0xfebffcff irq 16 at device 0.0 on pci6
re1: Chip rev. 0x10000000
re1: MAC rev. 0x00000000
miibus1: <MII bus> on re1
rgephy1: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus1
rgephy1:  none, 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: Using defaults for TSO: 65518/35/2048
re1: Ethernet address: d8:eb:97:91:12:d7
re2: <D-Link DGE-528(T) Gigabit Ethernet Adapter> port 0xe400-0xe4ff mem
0xfebff800-0xfebff8ff irq 17 at device 1.0 on pci6
re2: Chip rev. 0x10000000
re2: MAC rev. 0x00000000
miibus2: <MII bus> on re2
rgephy2: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus2
rgephy2:  none, 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
re2: Using defaults for TSO: 65518/35/2048
re2: Ethernet address: c4:12:f5:32:57:76

I will need to try the patch tomorrow when i am located with the machine,

thanks
-kim


On Sun, Aug 16, 2015 at 7:56 AM, Yonghyeon PYUN <pyunyh@gmail.com> wrote:

> On Fri, Aug 14, 2015 at 06:29:08PM -0400, Kim Culhan wrote:
>
> [...]
>
> > > On 08/14/15 13:34, Kim Culhan wrote:
> > >> RE on 10.2-RELEASE #0 r286731M appears to pass only arp traffic.
> > >>
> > >> Replaced if_re.c with version from 273757, appears to work
> > >> normally.
> > >>
> > >> The diff:
> > >>
> > >> 34c34 < __FBSDID("$FreeBSD: stable/10/sys/dev/re/if_re.c 273757
> > >> 2014-10-28 00:43:00Z yongari $"); ---
> > >>> __FBSDID("$FreeBSD: releng/10.2/sys/dev/re/if_re.c 285177
> > >>> 2015-07-05
> > >> 20:16:38Z marius $"); 3198,3202d3197 <        * Enable transmit and
> > >> receive. <        */ <       CSR_WRITE_1(sc, RL_COMMAND,
> > >> RL_CMD_TX_ENB|RL_CMD_RX_ENB); < <       /* 3227a3223,3227
> > >>> /* * Enable transmit and receive. */ CSR_WRITE_1(sc, RL_COMMAND,
> > >>> RL_CMD_TX_ENB | RL_CMD_RX_ENB);
> > >>>
> > >> 3251,3254d3250 < #ifdef notdef <       /* Enable receiver and
> > >> transmitter. */ <       CSR_WRITE_1(sc, RL_COMMAND,
> > >> RL_CMD_TX_ENB|RL_CMD_RX_ENB); < #endif
> > >>
> > >> Let me know what additional info I can provide.
>
> [...]
>
> > > I'm running -current with all changes in place, I'm not seeing the
> > > issues noted here with my hardware.  Can you post your hardware from
> > > pciconf -lv?
> > >
> > > re0@pci0:3:0:0: class=0x020000 card=0x84321043 chip=0x816810ec
> > > rev=0x06 hdr=0x00
> > >     vendor     = 'Realtek Semiconductor Co., Ltd.'
> > >     device     = 'RTL8111/8168B PCI Express Gigabit Ethernet
> controller'
> > >     class      = network
> > >     subclass   = ethernet
> > > re1@pci0:4:5:0: class=0x020000 card=0x43021186 chip=0x43021186
> > > rev=0x10 hdr=0x00
> > >     vendor     = 'D-Link System Inc'
> > >     device     = 'DGE-530T Gigabit Ethernet Adapter (rev.C1) [Realtek
> > > RTL8169]'
> > >     class      = network
> > >     subclass   = ethernet
> > >
> > >
> > > sean
> >
> > pciconf -lv
> >
> > re0@pci0:2:0:0: class=0x020000 card=0x83671043 chip=0x816810ec rev=0x02
> > hdr=0x00
> >     vendor     = 'Realtek Semiconductor Co., Ltd.'
> >     device     = 'RTL8111/8168B PCI Express Gigabit Ethernet controller'
> >     class      = network
> >     subclass   = ethernet
> > re1@pci0:6:0:0: class=0x020000 card=0x816910ec chip=0x816910ec rev=0x10
> > hdr=0x00
> >     vendor     = 'Realtek Semiconductor Co., Ltd.'
> >     device     = 'RTL8169 PCI Gigabit Ethernet Controller'
> >     class      = network
> >     subclass   = ethernet
> > re2@pci0:6:1:0: class=0x020000 card=0x4c001186 chip=0x43001186 rev=0x10
> > hdr=0x00
> >     vendor     = 'D-Link System Inc'
> >     device     = 'DGE-528T Gigabit Ethernet Adapter'
> >     class      = network
> >     subclass   = ethernet
> >
> > The problem was noted on re2, re0 and re1 appeared to be working
> normally.
> >
>
> Hmm, it seems your PCI controller does not work.
> I can't explain why Sean's re1 still works though.
> Would you try attached patch?
>
> BTW, it would be better to see the re(4) related dmesg output.
> Driver will show Chip/MAC revision and that is the only way to
> identify each MAC revision.
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKZxVQXDrkfFOX0QW9=BVZJH0J0zSaet5k4Bp1aXSQR0O41%2BSA>