Re: nve0: device timeout (1)
- From: "Kevin Oberman" <oberman@xxxxxx>
- Date: Mon, 27 Mar 2006 20:44:32 -0800
Turning off the watchdog timer in the source may work around the
problem. It's probably not a real fix, but, if it works...
*** if_nve.c 25 Dec 2005 21:57:03 -0000 1.7.2.8
--- if_nve.c 5 Jan 2006 00:12:45 -0000
***************
*** 943,949 ****
return;
}
/* Set watchdog timer. */
! ifp->if_timer = 8;
/* Copy packet to BPF tap */
BPF_MTAP(ifp, m0);
--- 943,949 ----
return;
}
/* Set watchdog timer. */
! ifp->if_timer = 0;
/* Copy packet to BPF tap */
BPF_MTAP(ifp, m0);
I must apologize. This patch is from David G. Lawrence of Download
Technologies. He posted Saturday in a thread titled "nve timeout (and
down) regression?"
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@xxxxxx Phone: +1 510 486-8634
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: nve0: device timeout (1)
- From: Sergey Matveychuk
- Re: nve0: device timeout (1)
- From: Bachilo Dmitry
- Re: nve0: device timeout (1)
- References:
- Re: nve0: device timeout (1)
- From: Kevin Oberman
- Re: nve0: device timeout (1)
- Prev by Date: Re: nve0: device timeout (1)
- Next by Date: Re: nve0: device timeout (1)
- Previous by thread: Re: nve0: device timeout (1)
- Next by thread: Re: nve0: device timeout (1)
- Index(es):
Relevant Pages
|
|