Re: splassert: pool_put: want 0 have 4
On 21/06/17(Wed) 17:42, Marko Cupać wrote: > On Tue, 20 Jun 2017 12:22:46 +0200 > Martin Pieuchot <m...@openbsd.org> wrote: > > > On 14/06/17(Wed) 16:56, Marko Cupać wrote: > > > On Tue, 13 Jun 2017 11:38:46 + (UTC) > > > Stuart Henderson <s...@spacehopper.org> 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 > > > > This has been fixed by yasuoka@ on Mai 28th. Please try a new > > snapshot and report back if you still encounter similar problems. > > Thanx for info. Any chance to get this as (sys)patch? I'm tracking > binary -stable for my production, I'd rather not experiment with > snapshots as they tend to fix one thing while breaking another. No it won't happen, this is not critical and the change is too intrusive.
Re: splassert: pool_put: want 0 have 4
On Tue, 20 Jun 2017 12:22:46 +0200 Martin Pieuchot <m...@openbsd.org> wrote: > On 14/06/17(Wed) 16:56, Marko Cupać wrote: > > On Tue, 13 Jun 2017 11:38:46 + (UTC) > > Stuart Henderson <s...@spacehopper.org> 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 > > This has been fixed by yasuoka@ on Mai 28th. Please try a new > snapshot and report back if you still encounter similar problems. Thanx for info. Any chance to get this as (sys)patch? I'm tracking binary -stable for my production, I'd rather not experiment with snapshots as they tend to fix one thing while breaking another. -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: splassert: pool_put: want 0 have 4
On 14/06/17(Wed) 16:56, Marko Cupać wrote: > On Tue, 13 Jun 2017 11:38:46 + (UTC) > Stuart Henderson <s...@spacehopper.org> 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 This has been fixed by yasuoka@ on Mai 28th. Please try a new snapshot and report back if you still encounter similar problems. Cheers, Martin
Re: splassert: pool_put: want 0 have 4
On Tue, 13 Jun 2017 11:38:46 + (UTC) Stuart Henderson <s...@spacehopper.org> 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/
Re: splassert: pool_put: want 0 have 4
On Tue, 13 Jun 2017 11:38:46 + (UTC) Stuart Henderson <s...@spacehopper.org> wrote: > On 2017-06-13, Marko Cupać <marko.cu...@mimar.rs> 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 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). I've turned it on, let's see what happens. I'll check back when I see something related in log. Some additional info: I noticed these messages always appear after pptp user disconnects: Jun 6 15:47:40 nat2 npppd[18637]: ppp id=10 layer=base logtype=TUNNELUSAGE user="someuser" duration=241sec layer2=COMPANY layer2from=IP.ADD.RE.SS:29019 auth=MS-CHAP-V2 data_in=90561bytes,634packets data_out=332801bytes,587packets error_in=6 error_out=0 mppe=yes mppe_in=128bits,stateless mppe_out=128bits,stateless iface=tun1 Jun 6 15:47:40 nat2 npppd[18637]: pptpd ctrl=10 call=34773 logtype=Terminated Jun 6 15:47:40 nat2 npppd[18637]: pptpd ctrl=10 logtype=Finished Jun 6 15:47:41 nat2 /bsd: splassert: pool_put: want 0 have 4 Jun 6 15:47:41 nat2 /bsd: splassert: pool_put: want 0 have 4 Regards, -- Before enlightenment - chop wood, draw water. After enlightenment - chop wood, draw water. Marko Cupać https://www.mimar.rs/
Re: splassert: pool_put: want 0 have 4
On 2017-06-13, Marko Cupać <marko.cu...@mimar.rs> 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 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).
splassert: pool_put: want 0 have 4
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/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2128887808 (2030MB) avail mem = 2059747328 (1964MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xee000 (69 entries) bios0: vendor HP version "P58" date 05/02/2011 bios0: HP ProLiant DL360 G5 acpi0 at bios0: rev 2 acpi0: sleep states S0 S4 S5 acpi0: tables DSDT FACP SPCR MCFG HPET SPMI ERST APIC BERT HEST SSDT acpi0: wakeup devices PCI0(S5) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpihpet0 at acpi0: 14318179 Hz acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz, 2500.44 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu0: 6MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 333MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.2, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz, 2000.07 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu1: 6MB 64b/line 16-way L2 cache cpu1: smt 0, core 2, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz, 2500.09 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu2: 6MB 64b/line 16-way L2 cache cpu2: smt 0, core 1, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Xeon(R) CPU E5420 @ 2.50GHz, 2500.09 MHz cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1,NXE,LONG,LAHF,PERF,SENSOR cpu3: 6MB 64b/line 16-way L2 cache cpu3: smt 0, core 3, package 0 ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins ioapic1 at mainbus0: apid 9 pa 0xfec8, version 20, 24 pins acpiprt0 at acpi0: bus 1 (IP2P) acpiprt1 at acpi0: bus 11 (IPE1) acpiprt2 at acpi0: bus 10 (IPE4) acpiprt3 at acpi0: bus 16 (P2P2) acpiprt4 at acpi0: bus 9 (PT02) acpiprt5 at acpi0: bus 6 (PT03) acpiprt6 at acpi0: bus 19 (PT04) acpiprt7 at acpi0: bus 3 (NB01) acpiprt8 at acpi0: bus 5 (NB02) acpiprt9 at acpi0: bus 0 (PCI0) acpicpu0 at acpi0: !C3(250@17 io@0x915), C1(1000@1 halt) acpicpu1 at acpi0: !C3(250@17 io@0x915), C1(1000@1 halt) acpicpu2 at acpi0: !C3(250@17 io@0x915), C1(1000@1 halt) acpicpu3 at acpi0: !C3(250@17 io@0x915), C1(1000@1 halt) acpitz0 at acpi0: critical temperature is 31 degC "IPI0001" at acpi0 not configured "PNP0303" at acpi0 not configured "PNP0F13" at acpi0 not configured "PNP0A06" at acpi0 not configured ipmi at mainbus0 not configured pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "Intel 5000P Host" rev 0xb1 ppb0 at pci0 dev 2 function 0 "Intel 5000 PCIE" rev 0xb1 pci1 at ppb0 bus 9 ppb1 at pci1 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci2 at ppb1 bus 10 ppb2 at pci2 dev 0 function 0 "Intel 6321ESB PCIE" rev 0x01 pci3 at ppb2 bus 11 ppb3 at pci2 dev 1 function 0 "Intel 6321ESB PCIE" rev 0x01 pci4 at ppb3 bus 14 ppb4 at pci2 dev 2 function 0 "Intel 6321ESB PCIE" rev 0x01 pci5 at ppb4 bus 15 ppb5 at pci1 dev 0 function 3 "Intel 6321ESB PCIE-PCIX" rev 0x01 pci6 at ppb5 bus 16 ppb6 at pci0 dev 3 function 0 "Intel 5000 PCIE" rev 0xb1 pci7 at ppb6 bus 6 ciss0 at pci7 dev 0 function 0 "Hewlett-Packard Smart Array" rev 0x04: apic 8 int 16 ciss0: 1 LD, HW rev 4, FW 7.24/7.24, 64bit fifo scsibus1 at ciss0: 1 targets sd0 at scsibus1 targ 0 lun 0: <HP, LOGICAL VOLUME, 7.24> SCSI3 0/direct fixed sd0: 139979MB, 512 bytes/sector, 286677120 sectors ppb7 at pci0 dev 4 function 0 "Intel 5000 PCIE x8" rev 0xb1 pci8 at ppb7 bus 19 em0 at pci8 dev 0 function 0 "Intel 82574L" rev 0x00: msi, address 2c:27:d7:15:21:95 ppb8 at pci0 dev 5 function 0 "Intel 5000 PCIE" rev 0xb1 pci9 at ppb8 bus 22 ppb9 at pci0 dev 6 function 0 "Intel 5000 PCIE" rev 0xb1 pci10 at ppb9 bus 2 ppb10 at pci10 dev 0 function 0 "ServerWorks PC
