Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 08:51, Hans Petter Selasky wrote: > > On 08/08/17 01:52, Ben RUBSON wrote: >>> On 07 Aug 2017, at 19:57, Hans Petter Selasky wrote: >>> >>> On 08/07/17 19:19, Ben RUBSON wrote: > On 07 Aug 2017, at 18:19, Matt Joras wrote: > > On 08/07/2017 09:11, Hans Petter

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 09:04, Ben RUBSON wrote: "print V_twq_2msl" returns the following : No symbol "V_twq_2msl" in current context. Are you using VIMAGE ? --HPS ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 09:04, Ben RUBSON wrote: Here is vmstat -z : https://benrubson.github.io/vmstatz.log From what I can see there are not TCP allocation failures. This rules out one class of bugs: socket: 864, 2092652, 105, 371, 2318298, 0, 0 unpcb: 24

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 09:33, Hans Petter Selasky wrote: > > On 08/08/17 09:04, Ben RUBSON wrote: >> "print V_twq_2msl" returns the following : >> No symbol "V_twq_2msl" in current context. > > Are you using VIMAGE ? No, GENERIC FreeBSD 11.0 on a physical server.

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 09:37, Ben RUBSON wrote: On 08 Aug 2017, at 09:33, Hans Petter Selasky wrote: On 08/08/17 09:04, Ben RUBSON wrote: "print V_twq_2msl" returns the following : No symbol "V_twq_2msl" in current context. Are you using VIMAGE ? No, GENERIC FreeBSD 11.0 on a physical server. Can

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 09:38, Hans Petter Selasky wrote: > > On 08/08/17 09:37, Ben RUBSON wrote: >>> On 08 Aug 2017, at 09:33, Hans Petter Selasky wrote: >>> >>> On 08/08/17 09:04, Ben RUBSON wrote: "print V_twq_2msl" returns the following : No symbol "V_twq_2msl" in current context.

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 09:38, Hans Petter Selasky wrote: > > On 08/08/17 09:37, Ben RUBSON wrote: >>> On 08 Aug 2017, at 09:33, Hans Petter Selasky wrote: >>> >>> On 08/08/17 09:04, Ben RUBSON wrote: "print V_twq_2msl" returns the following : No symbol "V_twq_2msl" in current context.

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 09:43, Ben RUBSON wrote: OK. I'm quite (well, absolutely) new to kgdb, some clue on how I should proceed ? Thank you ! Ben print twq_2msl print *twq_2msl.tqh_first --HPS ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 09:54, Hans Petter Selasky wrote: > > On 08/08/17 09:43, Ben RUBSON wrote: >> OK. >> I'm quite (well, absolutely) new to kgdb, some clue on how I should proceed ? >> Thank you ! >> Ben > > print twq_2msl > print *twq_2msl.tqh_first (kgdb) set print pretty on (kgdb) print t

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 10:00, Ben RUBSON wrote: kgdb) print *twq_2msl.tqh_first $2 = { tw_inpcb = 0xf8031c570740, print *twq_2msl.tqh_first->tw_inpcb --HPS ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To

Re: mlx4en, timer irq @100%...

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 10:02, Hans Petter Selasky wrote: > > On 08/08/17 10:00, Ben RUBSON wrote: >> kgdb) print *twq_2msl.tqh_first >> $2 = { >> tw_inpcb = 0xf8031c570740, > > print *twq_2msl.tqh_first->tw_inpcb (kgdb) print *twq_2msl.tqh_first->tw_inpcb $3 = { inp_hash = { le_next =

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 10:06, Ben RUBSON wrote: On 08 Aug 2017, at 10:02, Hans Petter Selasky wrote: On 08/08/17 10:00, Ben RUBSON wrote: kgdb) print *twq_2msl.tqh_first $2 = { tw_inpcb = 0xf8031c570740, print *twq_2msl.tqh_first->tw_inpcb (kgdb) print *twq_2msl.tqh_first->tw_inpcb $3 = { i

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Ben RUBSON
> On 08 Aug 2017, at 10:31, Hans Petter Selasky wrote: > > On 08/08/17 10:06, Ben RUBSON wrote: >>> On 08 Aug 2017, at 10:02, Hans Petter Selasky wrote: >>> >>> On 08/08/17 10:00, Ben RUBSON wrote: kgdb) print *twq_2msl.tqh_first $2 = { tw_inpcb = 0xf8031c570740, >>> >>>

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Slawa Olhovchenkov
On Tue, Aug 08, 2017 at 10:31:33AM +0200, Hans Petter Selasky wrote: > Here is the conclusion: > > The following code is going in an infinite loop: > > > > for (;;) { > > TW_RLOCK(V_tw_lock); > > tw = TAILQ_FIRST(&V_twq_2msl); > > if (tw =

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 13:33, Slawa Olhovchenkov wrote: TW_RUNLOCK(V_tw_lock); and if (INP_INFO_TRY_WLOCK(&V_tcbinfo)) { `inp` can be invalidated, freed and this pointer may be invalid? If you look one line up there is a pcbref ?? --HPS ___ freebsd-net@freebsd

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Slawa Olhovchenkov
On Tue, Aug 08, 2017 at 01:49:08PM +0200, Hans Petter Selasky wrote: > On 08/08/17 13:33, Slawa Olhovchenkov wrote: > > TW_RUNLOCK(V_tw_lock); > > and > > if (INP_INFO_TRY_WLOCK(&V_tcbinfo)) { > > > > `inp` can be invalidated, freed and this pointer may be invalid? > > If you look one line up th

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Julien Charbon
Hi, On 8/8/17 10:31 AM, Hans Petter Selasky wrote: > On 08/08/17 10:06, Ben RUBSON wrote: >>> On 08 Aug 2017, at 10:02, Hans Petter Selasky wrote: >>> >>> On 08/08/17 10:00, Ben RUBSON wrote: kgdb) print *twq_2msl.tqh_first $2 = { tw_inpcb = 0xf8031c570740, >>> >>> print *

Re: mlx4en, timer irq @100%... (11.0 stuck on high network load ???)

2017-08-08 Thread Hans Petter Selasky
On 08/08/17 13:56, Slawa Olhovchenkov wrote: On Tue, Aug 08, 2017 at 01:49:08PM +0200, Hans Petter Selasky wrote: On 08/08/17 13:33, Slawa Olhovchenkov wrote: TW_RUNLOCK(V_tw_lock); and if (INP_INFO_TRY_WLOCK(&V_tcbinfo)) { `inp` can be invalidated, freed and this pointer may be invalid? If

[Bug 217637] One TCP connection accepted TWO times

2017-08-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637 Jonathan T. Looney changed: What|Removed |Added CC||j...@freebsd.org --- Comment

[Bug 217637] One TCP connection accepted TWO times

2017-08-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637 --- Comment #90 from Jonathan T. Looney --- (In reply to Jonathan T. Looney from comment #89) Forgot to include a link to the patch: https://reviews.freebsd.org/D11929 -- You are receiving this mail because: You are on the CC list for th

[Bug 217637] One TCP connection accepted TWO times

2017-08-08 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637 --- Comment #91 from Richard Russo --- For us, this may have limited effect, because our icmplim is much higher than the default (16k), because we do want to send closed port RSTs in high volumewhen our service ports are closed. This patch