realtek interface not working

[Gary Palmer]

On Fri, Sep 11, 2015 at 10:57:36PM -0700, Sreenath Battalahalli wrote:
> Hi Marius,
> 
> Thanks for the patch. I manually made changes to the two files, and after building the kernel and installing it,
> I can see the re0 interface. I am now sending this email using the new laptop.
> 
> However, I am a bit confused by the dmesg output. I see two sets of lines pertaining to the re0 device.
> 
> $dmesg | grep -i re0
> 
> re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0x3000-0x30ff mem 0xb0604000-0xb0604fff,0xb0600000-0xb0603fff irq 18 at device 0.0 on pci2
> re0: Using 1 MSI-X message
> re0: turning off MSI enable bit.
> re0: ASPM disabled
> re0: Chip rev. 0x54000000
> re0: MAC rev. 0x00100000
> re0: Unknown H/W revision: 0x54000000
> device_attach: re0 attach returned 6
> re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0x3000-0x30ff mem 0xb0604000-0xb0604fff,0xb0600000-0xb0603fff irq 18 at device 0.0 on pci2
> re0: Using 1 MSI-X message
> re0: ASPM disabled
> re0: Chip rev. 0x54000000
> re0: MAC rev. 0x00100000
> miibus0: <MII bus> on re0
> re0: Using defaults for TSO: 65518/35/2048
> re0: Ethernet address: 2c:60:0c:92:0f:c2
> 
> seems the driver attempted to initialize the device twice?
> 
> Anyway, it is working now.

The kernel dmesg buffer can be preserved over a reboot, so it's possible
the lines up to and including "device_attach: re0 attach returned 6" are
from the reboot before you installed the patch.  Rather than just grep for
re0, do "dmesg | less" or "dmesg | more" and check the context of the 
"device_attach: re0 attach returned 6" error and see if there are any 
indications of a reboot between that line and the next re0 probe lines, e.g.
"Copyright (c) 1992-2015 The FreeBSD Project"

Regards,

Gary