Re: OpenBSD 6.0 panic
Le vendredi 02 septembre 2016 à 18:25 +0200, Bastien Durel a écrit : > Hello. > > I upgraded my router to 6.0 yesterday, and now I got a panic each > time > I reboot it. > > Here is a console log : > > # > reboot > > stopping package daemons: munin_node svscanpanic: kernel diagnostic > assertion "ifp != NULL" failed: file "../../../../net/route.c", line > 902 > Starting stack trace... > panic() at panic+0x10b > __assert() at __assert+0x25 > rtrequest_delete() at rtrequest_delete+0x206 > rtrequest() at rtrequest+0x247 > route_output() at route_output+0x4e8 > raw_usrreq() at raw_usrreq+0x217 > route_usrreq() at route_usrreq+0x6e > sosend() at sosend+0x3c8 > dofilewritev() at dofilewritev+0x205 > sys_writev() at sys_writev+0x6d > syscall() at syscall+0x27b > --- syscall (number 121) --- > end of kernel > end trace frame: 0x4, count: 246 > 0xa46bf29a62a: > End of stack trace. > syncing disks... 14 12 12 12 12 12 12 12 12 12 12 12 8 8 8 8 8 8 8 8 > giving up > > dumping to dev 4,1 offset 492607 > dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 > 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 > 47d > > > rebooting... > I saw the dmesg was missing, stripped down by dmime, so I'll include it inline. The panic occurs each time openvpn is shut down, not only at host shutdown ; I guess it's related to interface removal. My openvpn interfaces are configured in TAP mode. booting hd0a:/bsd: 6892100+2179088+267272+0+663552 [72+726576+483179]=0xab3868 entry point at 0x1001000 [7205c766, 3404, 24448b12, 3be0a304] [ using 1210472 bytes of bsd ELF symbol table ] Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2016 OpenBSD. All rights reserved. http://www.OpenB SD.org OpenBSD 6.0 (GENERIC.MP) #2319: Tue Jul 26 13:00:43 MDT 2016 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.M P real mem = 519962624 (495MB) avail mem = 499789824 (476MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0 acpi at bios0 not configured mpbios0 at bios0: Intel MP Specification 1.4 cpu0 at mainbus0: apid 0 (boot processor) cpu0: Genuine Intel(R) CPU @ 600MHz, 600.08 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DSR cpu0: 512KB 64b/line 8-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 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.2.0.2.0.3, IBE cpu1 at mainbus0: apid 1 (application processor) cpu1: Genuine Intel(R) CPU @ 600MHz, 600.00 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUS H,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,DTES64,MWAIT,DSR cpu1: 512KB 64b/line 8-way L2 cache cpu1: smt 1, core 0, package 0 mpbios0: bus 0 is type PCI mpbios0: bus 64 is type ISA ioapic0 at mainbus0: apid 0 pa 0xfec0, version 20, 24 pins pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 vendor "Intel", unknown product 0x4115 rev 0x05 pchb1 at pci0 dev 1 function 0 "Intel E600 Config" rev 0x00 ppb0 at pci0 dev 23 function 0 "Intel E600 PCIE" rev 0x00 pci1 at ppb0 bus 1 ppb1 at pci1 dev 0 function 0 "Intel EG20T PCIE" rev 0x01 pci2 at ppb1 bus 2 "Intel EG20T Packet Hub" rev 0x01 at pci2 dev 0 function 0 not configured "Intel EG20T Ethernet" rev 0x02 at pci2 dev 0 function 1 not configured "Intel EG20T GPIO" rev 0x01 at pci2 dev 0 function 2 not configured ohci0 at pci2 dev 2 function 0 "Intel EG20T USB" rev 0x02: apic 0 int 19, version 1.0 ohci1 at pci2 dev 2 function 1 "Intel EG20T USB" rev 0x02: apic 0 int 19, version 1.0 ohci2 at pci2 dev 2 function 2 "Intel EG20T USB" rev 0x02: apic 0 int 19, version 1.0 ehci0 at pci2 dev 2 function 3 "Intel EG20T USB" rev 0x02: apic 0 int 19 usb0 at ehci0: USB revision 2.0 uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1 "Intel EG20T USB Client" rev 0x02 at pci2 dev 2 function 4 not configured sdhc0 at pci2 dev 4 function 0 "Intel EG20T SDIO" rev 0x01: apic 0 int 18 sdhc0: SDHC 1.0, 50 MHz base clock sdmmc0 at sdhc0: 4-bit, sd high-speed, mmc high-speed sdhc1 at pci2 dev 4 function 1 "Intel EG20T SDIO" rev 0x01: apic 0 int 18 sdhc1: SDHC 1.0, 50 MHz base clock sdmmc1 at sdhc1: 4-bit, sd high-speed, mmc high-speed ahci0 at pci2 dev 6 function 0 "Intel EG20T AHCI" rev 0x02: msi, AHCI 1.1 ahci0: port 0: 3.0Gb/s scsibus1 at ahci0: 32 targets sd0 at scsibus1 targ 0 lun 0: SCSI3 0/direct fixed naa.50026b7253081a83 sd0: 28626MB, 512 bytes/sector, 58626288 sectors, thin ohci3 at pci2 dev 8 function 0 "Intel EG20T USB" rev 0x02: apic 0 int 16, version 1.0 ohci4 at pci2 dev 8 function 1 "Intel EG20T USB" rev 0x02: apic 0 int 16, version 1.0 ohci5 at pci2 dev 8 function 2 "Int
Re: OpenBSD 6.0 panic
On 2016-09-03, Bastien Durel wrote: > Le 02/09/2016 à 23:28, Ryan Freeman a écrit : >> On Fri, Sep 02, 2016 at 06:25:15PM +0200, Bastien Durel wrote: >>> Hello. >>> >>> I upgraded my router to 6.0 yesterday, and now I got a panic each time >>> I reboot it. >> >> Hi, >> >> Did you happen to forget to do your pkg_add -u to upgrade packages? I >> suspect it might be openvpn not updated yet throwing the error? >> >> Cheers! >> -ryan >> > Hello, > > I did ran pkg_add -u, but there's a mess in my package database, and > some packages was not registered I would do this: run pkg_check, let it finish, run pkg_add -u, run pkg_check again. But I don't think it's related to the panic. > But upgrading it did not solved the panic (I would have been surprised > if an application crash made the kernel panic) It's a bug obviously, but it can happen sometimes.
Re: OpenBSD 6.0 panic
Le 02/09/2016 à 23:28, Ryan Freeman a écrit : On Fri, Sep 02, 2016 at 06:25:15PM +0200, Bastien Durel wrote: Hello. I upgraded my router to 6.0 yesterday, and now I got a panic each time I reboot it. Hi, Did you happen to forget to do your pkg_add -u to upgrade packages? I suspect it might be openvpn not updated yet throwing the error? Cheers! -ryan Hello, I did ran pkg_add -u, but there's a mess in my package database, and some packages was not registered # pkg_add openvpn quirks-2.241 signed on 2016-07-26T16:56:10Z Collision in openvpn-2.3.11: the following files already exist /usr/local/include/openvpn/openvpn-plugin.h from openvpn-2.3.11 (different checksum) /usr/local/lib/openvpn/plugins/openvpn-plugin-down-root.a from openvpn-2.3.11 (different checksum) /usr/local/lib/openvpn/plugins/openvpn-plugin-down-root.la from openvpn-2.3.11 (same checksum) /usr/local/lib/openvpn/plugins/openvpn-plugin-down-root.so from openvpn-2.3.11 (different checksum) /usr/local/man/man8/openvpn.8 from openvpn-2.3.11 (different checksum) /usr/local/sbin/openvpn from openvpn-2.3.11 (different checksum) [...] wide-dhcpc6 was affected too. But upgrading it did not solved the panic (I would have been surprised if an application crash made the kernel panic) -- Bastien
Re: OpenBSD 6.0 panic
On Fri, Sep 02, 2016 at 06:25:15PM +0200, Bastien Durel wrote: > Hello. > > I upgraded my router to 6.0 yesterday, and now I got a panic each time > I reboot it. Hi, Did you happen to forget to do your pkg_add -u to upgrade packages? I suspect it might be openvpn not updated yet throwing the error? Cheers! -ryan > > Here is a console log : > > # reboot > stopping package daemons: munin_node svscanpanic: kernel diagnostic assertion > "ifp != NULL" failed: file "../../../../net/route.c", line 902 > Starting stack trace... > panic() at panic+0x10b > __assert() at __assert+0x25 > rtrequest_delete() at rtrequest_delete+0x206 > rtrequest() at rtrequest+0x247 > route_output() at route_output+0x4e8 > raw_usrreq() at raw_usrreq+0x217 > route_usrreq() at route_usrreq+0x6e > sosend() at sosend+0x3c8 > dofilewritev() at dofilewritev+0x205 > sys_writev() at sys_writev+0x6d > syscall() at syscall+0x27b > --- syscall (number 121) --- > end of kernel > end trace frame: 0x4, count: 246 > 0xa46bf29a62a: > End of stack trace. > syncing disks... 14 12 12 12 12 12 12 12 12 12 12 12 8 8 8 8 8 8 8 8 giving up > > dumping to dev 4,1 offset 492607 > dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 > 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 47d > > > rebooting... > > The svcan deamon which is to be shut down when the panic occurs > monitors a few(4) openvpn tunnels, in TAP mode, over which ospfd+ospf6d > runs. When it's stopped, the tun* interfaces is removed, I guess it's > related ? > > I've attached a boot log (with dmesg). > > There's a "Bad system call" in the networking start too, but I think > it's not related (and I don't know what interface produces this > message) > > Thanks, > > --?? > Bastien > > [demime 1.01d removed an attachment of type text/x-log which had a name of > fremen.log"; charset="UTF-8]
Re: OpenBSD 6.0 panic
Bastien Durel [bast...@durel.org] wrote: > > There's a "Bad system call" in the networking start too, but I think > it's not related (and I don't know what interface produces this > message) > This would be a program you compiled that you are calling from hostname.if.
OpenBSD 6.0 panic
Hello. I upgraded my router to 6.0 yesterday, and now I got a panic each time I reboot it. Here is a console log : # reboot stopping package daemons: munin_node svscanpanic: kernel diagnostic assertion "ifp != NULL" failed: file "../../../../net/route.c", line 902 Starting stack trace... panic() at panic+0x10b __assert() at __assert+0x25 rtrequest_delete() at rtrequest_delete+0x206 rtrequest() at rtrequest+0x247 route_output() at route_output+0x4e8 raw_usrreq() at raw_usrreq+0x217 route_usrreq() at route_usrreq+0x6e sosend() at sosend+0x3c8 dofilewritev() at dofilewritev+0x205 sys_writev() at sys_writev+0x6d syscall() at syscall+0x27b --- syscall (number 121) --- end of kernel end trace frame: 0x4, count: 246 0xa46bf29a62a: End of stack trace. syncing disks... 14 12 12 12 12 12 12 12 12 12 12 12 8 8 8 8 8 8 8 8 giving up dumping to dev 4,1 offset 492607 dump 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 490 489 488 487 486 485 484 483 482 481 480 479 47d rebooting... The svcan deamon which is to be shut down when the panic occurs monitors a few(4) openvpn tunnels, in TAP mode, over which ospfd+ospf6d runs. When it's stopped, the tun* interfaces is removed, I guess it's related ? I've attached a boot log (with dmesg). There's a "Bad system call" in the networking start too, but I think it's not related (and I don't know what interface produces this message) Thanks, --Â Bastien [demime 1.01d removed an attachment of type text/x-log which had a name of fremen.log"; charset="UTF-8]
