Re: panic with tcp timers

2016-07-21 Thread Julien Charbon
Hi, On 7/14/16 11:02 PM, Larry Rosenman wrote: > On 2016-07-14 12:01, Julien Charbon wrote: >> On 6/20/16 11:55 AM, Julien Charbon wrote: >>> On 6/20/16 9:39 AM, Gleb Smirnoff wrote: >>>> On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: >>>

Re: panic with tcp timers

2016-07-14 Thread Julien Charbon
Hi, On 6/20/16 11:55 AM, Julien Charbon wrote: > On 6/20/16 9:39 AM, Gleb Smirnoff wrote: >> On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: >> J> > Comparing stable/10 and head, I see two changes that could >> J> > affect that: >> J

Re: panic with tcp timers

2016-06-28 Thread Julien Charbon
Hi Randall, On 6/25/16 4:41 PM, Randall Stewart via freebsd-net wrote: > Ok > > Lets try this again with my source changed to my @freebsd.net :-) > > Now I am also attaching a patch for you Gleb, this will take some poking to > get in to your NF-head since it incorporates some changes we made

Re: panic with tcp timers

2016-06-20 Thread Julien Charbon
Hi, On 6/20/16 11:58 AM, Gleb Smirnoff wrote: > On Mon, Jun 20, 2016 at 11:55:55AM +0200, Julien Charbon wrote: > J> > On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: > J> > J> > Comparing stable/10 and head, I see two changes that could > J> >

Re: panic with tcp timers

2016-06-20 Thread Julien Charbon
Hi, On 6/20/16 12:30 PM, Gleb Smirnoff wrote: > On Mon, Jun 20, 2016 at 12:14:18PM +0200, Hans Petter Selasky wrote: > H> On 06/20/16 11:58, Gleb Smirnoff wrote: > H> > The fix I am working on now is doing exactly that. callout_reset must > H> > return 0 if the callout is currently running. > H>

Re: panic with tcp timers

2016-06-20 Thread Julien Charbon
Hi, On 6/20/16 9:39 AM, Gleb Smirnoff wrote: > On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: > J> > Comparing stable/10 and head, I see two changes that could > J> > affect that: > J> > > J> > - callout_async_drain > J> > - sw

Re: panic with tcp timers

2016-06-17 Thread Julien Charbon
Hi Gleb, On 6/17/16 6:53 AM, Gleb Smirnoff wrote: > At Netflix we are observing a race in TCP timers with head. > The problem is a regression, that doesn't happen on stable/10. > The panic usually happens after several hours at 55 Gbit/s of > traffic. > > What happens is that tcp_timer_keep f

Re: traceroute6: panic: pcb not read locked

2015-08-08 Thread Julien Charbon
On Aug 8, 2015 07:49, "Julien Charbon" wrote: > > On 08/08/15 05:25, Mark Johnston wrote: > > On Fri, Aug 07, 2015 at 08:04:01PM -0500, Larry Rosenman wrote: > >> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running traceroute6, > >> got the fo

Re: traceroute6: panic: pcb not read locked

2015-08-08 Thread Julien Charbon
On 08/08/15 07:49, Julien Charbon wrote: > On 08/08/15 05:25, Mark Johnston wrote: >> On Fri, Aug 07, 2015 at 08:04:01PM -0500, Larry Rosenman wrote: >>> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running >>> traceroute6, >>> got the following p

Re: traceroute6: panic: pcb not read locked

2015-08-07 Thread Julien Charbon
On 08/08/15 05:25, Mark Johnston wrote: > On Fri, Aug 07, 2015 at 08:04:01PM -0500, Larry Rosenman wrote: >> Trying to debug TimeWarner IPV6 to my HE.NET tunnel, and running >> traceroute6, >> got the following panic: >> >> borg.lerctr.org dumped core - see /var/crash/vmcore.0 >> >> Fri Aug 7 19