On 11 maj 2012, at 11:16, Stuart Henderson wrote: > On 2012/05/11 01:15, Garry Dolley wrote: >> On Thu, May 10, 2012 at 03:31:27PM +0100, Stuart Henderson wrote: >>> In gmane.os.openbsd.misc, Garry Dolley wrote: >>>> On Tue, May 08, 2012 at 07:58:30PM -0400, Simon Perreault wrote: >>>>> On 2012-05-08 19:08, Per-Olov Sjvholm wrote: >>>>>> It says "em1: watchdog timeout -- resetting" >>>>> >>>>> <aol> >>>>> I saw the same on an amd64 VPS from arpnetworks.com. Network was not >>>>> functional. Backed out. Did not investigate further. >>>>> </aol> >>>>> >>>>> Simon >>>> >>>> I had another customer on amd64 report this problem today. Not sure >>>> what the solution is. I'm recommending either downgrade to 5.0 or >>>> use i386 arch for now. >>> >>> If possible, tracking down the commit which broke it, or at least >>> narrow it to a reasonably small date range, would help. I have >>> an archive of snapshot kernels if you want to work through them >>> rather than cvs checkouts, contact me if you'd like access to them. >> >> Guys, >> >> I now have an amd64 test VM set up, where I installed stock 5.0. >> >> I ran a lot of traffic over em0 without any timeouts. >> >> I also have been trying several -current kernels. >> >> As of: >> >> OpenBSD 5.1-current (GENERIC) #205: Wed Mar 28 21:40:45 MDT 2012 >> >> I don't see any em0 timeouts. >> >> I will continue to try newer ones and report back here... > > Hmm - Mar 28 is already after 5.1 was released. > > Could somebody seeing the problem (sperreault?) please send a > dmesg from a kernel showing the problem? >
Hi Stuart Here is a dmesg on 4.9 where it's working and on 5.1 when it's not working. http://www.incedo.eu/~sjoholmp/misc_internet_links/timer_problem_openbsd/ Note that both are virtual OpenBSDs running on the exact same KVM host version and use the same bios etc. Regards P-O -- GPG keyID: 5231C0C4 GPG fingerprint: B232 3E1A F5AB 5E10 7561 6739 766E D29D 5231 C0C4
