; > Can you try "sysctl kern.splassert=2" to obtain a backtrace?
> > > >
> > > > (This isn't on by default as there's a small risk of problems,
> > > > though I run this on almost all my routers/firewalls and never
> > > > had
gt; > >
> > > (This isn't on by default as there's a small risk of problems,
> > > though I run this on almost all my routers/firewalls and never
> > > had trouble from it).
> >
> > Here's the backtrace:
> >
> > Jun 14 16:52:05
roblems,
> > though I run this on almost all my routers/firewalls and never
> > had trouble from it).
>
> Here's the backtrace:
>
> Jun 14 16:52:05 nat2 /bsd: splassert: pool_put: want 0 have 4
> Jun 14 16:52:05 nat2 /bsd: Starting stack trace...
>
; had trouble from it).
Here's the backtrace:
Jun 14 16:52:05 nat2 /bsd: splassert: pool_put: want 0 have 4
Jun 14 16:52:05 nat2 /bsd: Starting stack trace...
Jun 14 16:52:05 nat2 /bsd: pool_put() at pool_put+0x6b
Jun 14 16:52:05 nat2 /bsd: pipex_destroy_session() at pipex_destroy_session+0xe
On Tue, 13 Jun 2017 11:38:46 + (UTC)
Stuart Henderson wrote:
> On 2017-06-13, Marko Cupać wrote:
> > Hi,
> >
> > I see these in my console log:
> > Jun 6 16:14:25 nat2 /bsd: splassert: pool_put: want 0 have 4
> >
> > I don't observe any negative
On 2017-06-13, Marko Cupać wrote:
> Hi,
>
> I see these in my console log:
> Jun 6 16:14:25 nat2 /bsd: splassert: pool_put: want 0 have 4
>
> I don't observe any negative effects. Should I be worried? :)
Can you try "sysctl kern.splassert=2" to obtain a backtra
Hi,
I see these in my console log:
Jun 6 16:14:25 nat2 /bsd: splassert: pool_put: want 0 have 4
I don't observe any negative effects. Should I be worried? :)
Here's dmesg:
OpenBSD 6.1 (GENERIC.MP) #6: Mon May 22 20:34:30 CEST 2017
rob...@syspatch-61-amd64.openbsd.org:/usr/sr
7 matches
Mail list logo
