Date: Wed, 10 Jun 2015 22:06:25 +0100 From: Karl Pielorz <kpielorz_lst@tdx.co.uk> To: freebsd-net@FreeBSD.org Subject: Re: Realtek Issues (re) on PC Engines APU1 Board... Message-ID: <066F0471D6AE7795BFB049A3@Karls-Mac-mini.local> In-Reply-To: <D6F0FF009BD7A0E3B0423C22@Karls-Mac-mini.local> References: <D6F0FF009BD7A0E3B0423C22@Karls-Mac-mini.local>
next in thread | previous in thread | raw e-mail | index | archive | help
Ok, I moved the traffic off of re1 (should have tried this before) to re2 - and it seems (so far) stable, so maybe just re1 is having issues... dmesg for re1 is: " pcib2: <ACPI PCI-PCI bridge> irq 17 at device 5.0 on pci0 pci2: <ACPI PCI bus> on pcib2 re1: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port 0x2000-0x20ff mem 0xf7c00000-0xf7c00fff,0xf7b00000-0xf7b03fff irq 17 at device 0.0 on pci2 re1: Using 1 MSI-X message re1: ASPM disabled re1: Chip rev. 0x2c000000 re1: MAC rev. 0x00200000 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: Ethernet address: 00:0d:xx:xx:xx:xx " I'll leave it running on that for now, and try to crash the box a few times (i.e. sling a lot of traffic through it repeatedly). Unfortunately we need all 3 interfaces working when these boxes are deployed - so longer term, avoiding re1 isn't really an option :( Since moving from re1 to re2 (and rebooting) - I've not seen any watchdog timeout errors for any re interface. -Karl --On 10 June 2015 21:44:50 +0100 Karl Pielorz <kpielorz_lst@tdx.co.uk> wrote: > > Hi, > > I've recently bought an APU1 (by PC Engines) - this was to start to > replace a number of ALIX boards we use from them with FreeBSD. > > However - I'm having issues with the onboard (Realtek) interfaces on it. > These show up in dmesg as: > > " > Event timer "HPET" frequency 14318180 Hz quality 550 > Event timer "HPET1" frequency 14318180 Hz quality 450 > pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 > pci0: <ACPI PCI bus> on pcib0 > pcib1: <ACPI PCI-PCI bridge> irq 16 at device 4.0 on pci0 > pci1: <ACPI PCI bus> on pcib1 > re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port > 0x1000-0x10ff mem 0xf7a00000-0xf7a00fff,0xf7900000-0xf7903fff irq 16 at > device 0.0 on pci1 > re0: Using 1 MSI-X message > re0: ASPM disabled > re0: Chip rev. 0x2c000000 > re0: MAC rev. 0x00200000 > 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: Ethernet address: 00:0d:xx:xx:xx:xx > " > > Ditto for re1, and re2 > > The box works OK - but if you throw a lot of traffic at it (e.g. > >50Mbits) it just "stops". > > No messages on console (it's a serial console) - nothing logged, no > kernel panic - it just grinds to a halt (my serial console dies as well) > - and I have to reboot it. > > The box at the moment is running natd (using re1 to nat for traffic seen > on re0). > > It's running FreeBSD 10.1-RELEASE-p10 > > The only stuff I see logged (occasionally) is: > > " > re1: watchdog timeout > re1: link state changed to DOWN > re1: link state changed to UP > re1: watchdog timeout > re1: link state changed to DOWN > re1: link state changed to UP > re1: watchdog timeout > re1: link state changed to DOWN > re1: link state changed to UP > " > > Any suggestions? > > Cheers, > > -Karl > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?066F0471D6AE7795BFB049A3>