On 08/12/15 19:39, Chris Cappuccio wrote:
Kapetanakis Giannis [bil...@edu.physics.uoc.gr] wrote:
On 20/11/15 15:12, Martin Pieuchot wrote:
I just committed a revert to 1.305 keeping the API changes needed for
the driver to build.
This should bring your stability back, please let us know if that's not
the case.
I'm sorry for your troubles.
Hi,
I've upgraded yesterday to Dec 6 snapshot and today I got my first
em0: watchdog timeout -- resetting
em0 at pci1 dev 10 function 0 "Intel 82541EI" rev 0x00: apic 2 int 22, address
00:30:48:72:28:58
em1 at pci1 dev 11 function 0 "Intel 82541EI" rev 0x00: apic 2 int 23, address
00:30:48:72:28:59
Can you try to pinpoint when it started?
You mean what type of traffic caused it? Don't know.
The server is a ~ busy internal-only recursive DNS server (bind).
Other than that I was playing in it's shell when the event occurred,
nothing special.
If you mean time since boot, it was after ~ 22hours
Dec 7 15:53:20 /bsd: OpenBSD 5.8-current (GENERIC.MP) #1468: Sun Dec
6 11:27:59 MST 2015
Dec 8 16:06:59 /bsd: em0: watchdog timeout -- resetting
Dec 8 16:07:00 named[10537]: client: warning: client xx.xx.xx.xx#30399
(mail.expressionclones.com): error sending response: host unreachable
Dec 8 16:07:00 named[10537]: client: warning: client yy.yy.yy.yy#52263
(85.151.91.139.sa-accredit.habeas.com): error sending response: host
unreachable
The event happened only once and it's network recovered after a few
seconds. no reboot.
G
