Date: Fri, 2 Oct 2009 12:37:25 -0700 From: Jack Vogel <jfvogel@gmail.com> To: Rudy <crapsh@monkeybrains.net> Cc: freebsdnic@mailbox.cps.intel.com, freebsd-stable@freebsd.org Subject: Re: em0 watchdog timeouts Message-ID: <2a41acea0910021237w415efa2cs4354a0f99aef8f6@mail.gmail.com> In-Reply-To: <4AC64835.3060107@monkeybrains.net> References: <4AB9638B.8040607@monkeybrains.net> <4AC318E2.70306@monkeybrains.net> <4AC3DB8F.7010602@monkeybrains.net> <2a41acea0909301556g1df7dbafv813f5924553c8bfb@mail.gmail.com> <4AC5198E.7030609@monkeybrains.net> <4AC51B4C.7080905@monkeybrains.net> <2a41acea0910011450v41590f3dn112f367f26faed2d@mail.gmail.com> <4AC64835.3060107@monkeybrains.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Watchdog resets the adapter. Messing with these values is of dubious value anyway. Jack On Fri, Oct 2, 2009 at 11:36 AM, Rudy <crapsh@monkeybrains.net> wrote: > > I noticed something interesting. > > I set the rc_int_delay to 0: > sysctl dev.em.5.rx_int_delay=0 > > Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0: > Oct 1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66 > > After a watchdog event, sysctl dev.em.5.debug=1 shows ex_int_delay is > now 32: > Oct 2 11:29:49 mango kernel: em5: rx_int_delay = 32, rx_abs_int_delay = > 66 > > However, running sysctl dev.em.5 shows it as 0: > dev.em.5.rx_int_delay: 0 > dev.em.5.tx_int_delay: 66 > > Seems like the adapter and the kernel don't agree on the rx_int_delay > value. > > Rudy >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0910021237w415efa2cs4354a0f99aef8f6>