On Tue, 13 Jun 2017 11:38:46 +0000 (UTC) Stuart Henderson <[email protected]> wrote:
> 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 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+0xe4 Jun 14 16:52:05 nat2 /bsd: pipex_timer() at pipex_timer+0x85 Jun 14 16:52:05 nat2 /bsd: timeout_run() at timeout_run+0x48 Jun 14 16:52:05 nat2 /bsd: softclock() at softclock+0x147 Jun 14 16:52:05 nat2 /bsd: softintr_dispatch() at softintr_dispatch+0x8b Jun 14 16:52:05 nat2 /bsd: Xsoftclock() at Xsoftclock+0x1f Jun 14 16:52:05 nat2 /bsd: --- interrupt --- Jun 14 16:52:05 nat2 /bsd: end of kernel Jun 14 16:52:05 nat2 /bsd: end trace frame: 0x1388, count: 250 Jun 14 16:52:05 nat2 /bsd: 0x8: Jun 14 16:52:05 nat2 /bsd: End of stack trace. 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+0xf3 Jun 14 16:52:05 nat2 /bsd: pipex_timer() at pipex_timer+0x85 Jun 14 16:52:05 nat2 /bsd: timeout_run() at timeout_run+0x48 Jun 14 16:52:05 nat2 /bsd: softclock() at softclock+0x147 Jun 14 16:52:05 nat2 /bsd: softintr_dispatch() at softintr_dispatch+0x8b Jun 14 16:52:05 nat2 /bsd: Xsoftclock() at Xsoftclock+0x1f Jun 14 16:52:05 nat2 /bsd: --- interrupt --- Jun 14 16:52:05 nat2 /bsd: end of kernel Jun 14 16:52:05 nat2 /bsd: end trace frame: 0x1388, count: 250 Jun 14 16:52:05 nat2 /bsd: 0x8: Jun 14 16:52:05 nat2 /bsd: End of stack trace. Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
