Re: em(4) watchdog timeouts

Hi Gregor, I use the same revision than yours : - "Intel 82583V" rev 0x00: msi Regards, Alexis VACHETTE.* * On 16/11/2015 10:12, Alexis VACHETTE wrote: Hi Gregor, Thank you for your feedback. Did you have some timeout on 5.6 ? On amd64 version, I experienced some on heavy network load. Is

Re: em(4) watchdog timeouts

Hi Gregor, Thank you for your feedback. Did you have some timeout on 5.6 ? On amd64 version, I experienced some on heavy network load. Is it related ? Regards, Alexis VACHETTE. On 11/11/2015 21:19, Gregor Best wrote: Hi Alexis, On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE

Re: em(4) watchdog timeouts

On Fri, Nov 13, 2015 at 10:18:51AM -0500, Sonic wrote: > On Wed, Nov 11, 2015 at 9:20 AM, Gregor Best wrote: > > I've done some further testing and I think I've narrowed it down to the > > "Unlocking em(4) a bit further"-patch [0]. could you try this? its not written with the

Re: em(4) watchdog timeouts

On Mon, Nov 16, 2015 at 12:05:12AM +1000, David Gwynne wrote: > On Fri, Nov 13, 2015 at 10:18:51AM -0500, Sonic wrote: > > On Wed, Nov 11, 2015 at 9:20 AM, Gregor Best wrote: > > > I've done some further testing and I think I've narrowed it down to the > > > "Unlocking em(4) a

Re: em(4) watchdog timeouts

On Wed, Nov 11, 2015 at 9:20 AM, Gregor Best wrote: > I've done some further testing and I think I've narrowed it down to the > "Unlocking em(4) a bit further"-patch [0]. That was the start of it for me. When I could revert to rev 1.305 for if_em.c and rev 1.57 for if_em.h

Re: em(4) watchdog timeouts

I've done some further testing and I think I've narrowed it down to the "Unlocking em(4) a bit further"-patch [0]. With the patch reverted, I haven't seen any watchdog timeouts yet. I'm currently running the router with the patch reverted to make sure the timeouts don't happen again. [0]:

Re: em(4) watchdog timeouts

Hi Alexis, On Wed, Nov 11, 2015 at 08:11:15PM +, Alexis VACHETTE wrote: > [...] > Even with heavy network load ? > [...] So far, yes. I've saturated the device for about 45 Minutes with something like this (the other end is my laptop): ## on the router $ dd if=/dev/zero

Re: em(4) watchdog timeouts

enbsd.org; m...@openbsd.org Objet : Re: em(4) watchdog timeouts I've done some further testing and I think I've narrowed it down to the "Unlocking em(4) a bit further"-patch [0]. With the patch reverted, I haven't seen any watchdog timeouts yet. I'm currently running the router with the patch

Re: em(4) watchdog timeouts

On Mon, Nov 02, 2015 at 09:29:20PM +0100, Gregor Best wrote: > [...] > Looks good so far. I've run a few light tests and the usual load that > caused the timeouts before, haven't seen any yet. > [...] I just checked back on the router and it seems that the patch doesn't help after all :( The

Re: em(4) watchdog timeouts

On Sun, Nov 08, 2015 at 06:57:23PM +0100, Gregor Best wrote: > [...] > If it helps debugging this, I can give SSH access to the router, > provided that reboots don't happen between 18:00 and 02:00 German time > too often, since that's when we have larger amounts of visitors in our > hackerspace. >

Re: em(4) watchdog timeouts

On Wed, Nov 4, 2015 at 2:51 PM, Sonic wrote: > Is there anything else I can provide to assist in finding a cure for this > issue? Not sure this helps at all but the specific error I get is "em0: watchdog timeout -- resetting". In this case em0 is the nic on the internal

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 11:19 PM, Sonic wrote: > Sorry to report that the diff does not solve the timeout problem here. > > All was working fine with the if_em* versions from 2015/09/29 (I > downgraded to this version per Stuarts post on 10-14): > "try backing out the last

em(4) watchdog timeouts

Can those that are experiencing watchdog timeouts check if the diff below gets rid of them? Index: if_em.h === RCS file: /home/cvs/src/sys/dev/pci/if_em.h,v retrieving revision 1.58 diff -u -p -r1.58 if_em.h --- if_em.h 30 Sep

Re: em(4) watchdog timeouts

On Mon, Nov 02, 2015 at 08:11:30PM +0100, Mark Kettenis wrote: > Can those that are experiencing watchdog timeouts check if the diff > below gets rid of them? > [...] Looks good so far. I've run a few light tests and the usual load that caused the timeouts before, haven't seen any yet. For the

Re: em(4) watchdog timeouts

On Mon, Nov 2, 2015 at 2:11 PM, Mark Kettenis wrote: > Can those that are experiencing watchdog timeouts check if the diff > below gets rid of them? Sorry to report that the diff does not solve the timeout problem here. All was working fine with the if_em* versions from