TEST1: pfsync(vr2) moved to vr0, 15 min later:
May 9 11:58:13 backup /bsd: vr0: watchdog timeout TEST2(over 20 hours): SSH(unicast) traffic from the Master to the Backup through vr0(pfsync) with pfsync traffic(multicast). Everything works as should, lack of watchdog timeouts. TEST3: SSH connection stopped, 40min later: May 10 12:03:06 backup /bsd: vr0: watchdog timeout May 10 12:19:48 backup /bsd: vr0: watchdog timeout TEST4: Fresh, new install OpenBSD 5.9, pfsync is back to vr2. Six hours later: root@backup[~]grep timeout /var/log/messages May 14 09:21:41 backup /bsd: vr2: watchdog timeout May 14 09:28:51 backup /bsd: vr2: watchdog timeout May 14 09:34:32 backup /bsd: vr2: watchdog timeout May 14 09:34:42 backup /bsd: vr2: watchdog timeout May 14 09:52:43 backup /bsd: vr2: watchdog timeout May 14 10:32:36 backup /bsd: vr2: watchdog timeout May 14 10:44:57 backup /bsd: vr2: watchdog timeout May 14 11:01:08 backup /bsd: vr2: watchdog timeout May 14 11:19:59 backup /bsd: vr2: watchdog timeout May 14 11:28:25 backup /bsd: vr2: watchdog timeout May 14 11:44:25 backup /bsd: vr2: watchdog timeout May 14 11:57:02 backup /bsd: vr2: watchdog timeout May 14 12:15:18 backup /bsd: vr2: watchdog timeout May 14 12:26:54 backup /bsd: vr2: watchdog timeout May 14 12:36:25 backup /bsd: vr2: watchdog timeout May 14 13:11:42 backup /bsd: vr2: watchdog timeout May 14 13:21:44 backup /bsd: vr2: watchdog timeout May 14 13:27:44 backup /bsd: vr2: watchdog timeout May 14 13:39:15 backup /bsd: vr2: watchdog timeout TEST5: Back to OpenBSD 5.8-stable. Two days later: root@backup[~]grep timeout /var/log/messages root@backup[~] > On 08 May 2016, at 21:42, emigrant <emig...@gmail.com> wrote: > > Hi everyone > > PC Engines Alix 2D3 is my backup/slave machine(CARP+pfsync), OpenBSD 5.9-stable-patched(upgrade 5.8->5.9). > > vr0 -> WAN > vr1 -> LAN > vr2 -> pfsync > > Network cable is ok. Watchdog timeouts is mostly hardware related problem. Maybe IRQ or ACPI? I tried to disable ACPI in the kernel, but it didnât work. > > Everything works fine, but itâs frustrating, watchdog timeout messages. > > Hmm, interesting -> ( http://www.openbsd.org/plus59.html <http://www.openbsd.org/plus59.html> ) -> In em(4), fix the watchdog timeouts reported by various people > > > root@backup[/var/log]grep timeout messages > May 1 23:22:38 backup /bsd: vr2: watchdog timeout > May 1 23:56:00 backup /bsd: vr2: watchdog timeout > May 2 01:15:42 backup /bsd: vr2: watchdog timeout > May 2 03:46:27 backup /bsd: vr2: watchdog timeout > May 2 04:36:11 backup /bsd: vr2: watchdog timeout > May 2 05:26:14 backup /bsd: vr2: watchdog timeout > May 2 06:32:59 backup /bsd: vr2: watchdog timeout > May 2 08:21:01 backup /bsd: vr2: watchdog timeout > May 3 05:00:15 backup /bsd: vr2: watchdog timeout > May 3 08:20:00 backup /bsd: vr2: watchdog timeout > May 3 13:35:02 backup /bsd: vr2: watchdog timeout > May 3 14:41:47 backup /bsd: vr2: watchdog timeout > May 3 15:54:30 backup /bsd: vr2: watchdog timeout > May 3 16:05:57 backup /bsd: vr2: watchdog timeout > May 3 16:24:03 backup /bsd: vr2: watchdog timeout > May 3 17:08:46 backup /bsd: vr2: watchdog timeout > May 3 17:12:46 backup /bsd: vr2: watchdog timeout > May 3 17:14:56 backup /bsd: vr2: watchdog timeout > May 4 05:45:11 backup /bsd: vr2: watchdog timeout > May 4 06:01:52 backup /bsd: vr2: watchdog timeout > May 4 10:50:48 backup /bsd: vr2: watchdog timeout > May 4 19:42:46 backup /bsd: vr2: watchdog timeout > May 4 21:22:23 backup /bsd: vr2: watchdog timeout > May 5 06:00:46 backup /bsd: vr2: watchdog timeout > May 5 19:15:33 backup /bsd: vr2: watchdog timeout > May 6 09:05:49 backup /bsd: vr2: watchdog timeout > May 6 09:39:11 backup /bsd: vr2: watchdog timeout > May 6 18:04:26 backup /bsd: vr2: watchdog timeout > May 6 18:20:57 backup /bsd: vr2: watchdog timeout > May 6 18:37:38 backup /bsd: vr2: watchdog timeout > May 8 18:53:02 backup /bsd: vr2: watchdog timeout > root@backup[/var/log] > > > Watchdog timeout is also printed to the console. > > root@backup[~]dmesg > OpenBSD 5.9-stable (GENERIC) #1: Sun May 1 16:27:12 CEST 2016 > r...@backup.xxxxx.org <mailto:r...@backup.xxxxx.org>:/usr/src/sys/arch/i386/compile/GENERIC > cpu0: Geode(TM) Integrated Processor by AMD PCS ("AuthenticAMD" 586-class) 499 MHz > cpu0: FPU,DE,PSE,TSC,MSR,CX8,SEP,PGE,CMOV,CFLUSH,MMX,MMXX,3DNOW2,3DNOW > real mem = 267931648 (255MB) > avail mem = 250273792 (238MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: date 11/05/08, BIOS32 rev. 0 @ 0xfd088 > pcibios0 at bios0: rev 2.1 @ 0xf0000/0x10000 > pcibios0: pcibios_get_intr_routing - function not supported > pcibios0: PCI IRQ Routing information unavailable. > pcibios0: PCI bus #0 is the last bus > bios0: ROM list: 0xe0000/0xa800 > cpu0 at mainbus0: (uniprocessor) > mtrr: K6-family MTRR support (2 registers) > pci0 at mainbus0 bus 0: configuration mode 1 (bios) > pchb0 at pci0 dev 1 function 0 "AMD Geode LX" rev 0x33 > glxsb0 at pci0 dev 1 function 2 "AMD Geode LX Crypto" rev 0x00: RNG AES > vr0 at pci0 dev 9 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 10, address 00:0d:b9:18:c1:50 > ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 > vr1 at pci0 dev 10 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 11, address 00:0d:b9:18:c1:51 > ukphy1 at vr1 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 > vr2 at pci0 dev 11 function 0 "VIA VT6105M RhineIII" rev 0x96: irq 15, address 00:0d:b9:18:c1:52 > ukphy2 at vr2 phy 1: Generic IEEE 802.3u media interface, rev. 3: OUI 0x004063, model 0x0034 > glxpcib0 at pci0 dev 15 function 0 "AMD CS5536 ISA" rev 0x03: rev 3, 32-bit 3579545Hz timer, watchdog, gpio, i2c > gpio0 at glxpcib0: 32 pins > iic0 at glxpcib0 > maxtmp0 at iic0 addr 0x4c: lm86 > pciide0 at pci0 dev 15 function 2 "AMD CS5536 IDE" rev 0x01: DMA, channel 0 wired to compatibility, channel 1 wired to compatibility > wd0 at pciide0 channel 0 drive 0: <SanDisk SDCFX3-004G> > wd0: 4-sector PIO, LBA, 3919MB, 8027712 sectors > wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 > pciide0: channel 1 ignored (disabled) > ohci0 at pci0 dev 15 function 4 "AMD CS5536 USB" rev 0x02: irq 12, version 1.0, legacy support > ehci0 at pci0 dev 15 function 5 "AMD CS5536 USB" rev 0x02: irq 12 > usb0 at ehci0: USB revision 2.0 > uhub0 at usb0 "AMD EHCI root hub" rev 2.00/1.00 addr 1 > isa0 at glxpcib0 > isadma0 at isa0 > com0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo > com0: console > com1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo > pcppi0 at isa0 port 0x61 > spkr0 at pcppi0 > npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 > usb1 at ohci0: USB revision 1.0 > uhub1 at usb1 "AMD OHCI root hub" rev 1.00/1.00 addr 1 > nvram: invalid checksum > vscsi0 at root > scsibus1 at vscsi0: 256 targets > softraid0 at root > scsibus2 at softraid0: 256 targets > root on wd0a (f92426837899c790.a) swap on wd0b dump on wd0b > clock: unknown CMOS layout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > vr2: watchdog timeout > > > root@backup[~]ifconfig vr2 > vr2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > lladdr 00:0d:b9:18:c1:52 > priority: 0 > media: Ethernet autoselect (100baseTX full-duplex) > status: active > root@backup[~]
