[Bug 221151] panic: tdsendsignal(): invalid signal 0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue Aug 1 14:10:43 UTC 2017


            Bug ID: 221151
           Summary: panic: tdsendsignal(): invalid signal 0
           Product: Base System
           Version: 11.1-RELEASE
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: nbe at renzel.net

Created attachment 184914
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=184914&action=edit
tar.gz archive of the /var/crash folder (excluding core files)


during execution of a new tool "sandsifter" - here's the feature report:


I get kernel panics that all look the same to me:
capetown.renzel.net dumped core - see /var/crash/vmcore.0

Tue Aug  1 13:57:11 CEST 2017

FreeBSD capetown.renzel.net 11.1-RELEASE FreeBSD 11.1-RELEASE #7 r321628M: Mon
Jul 31 09:13:21 CEST 2017    
root at capetown.renzel.net:/usr/obj/usr/src/sys/GENERIC  amd64

panic: tdsendsignal(): invalid signal 0

GNU gdb (GDB) 7.12.1 [GDB v7.12.1 for FreeBSD]
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-portbld-freebsd11.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /boot/kernel/kernel...Reading symbols from

Unread portion of the kernel message buffer:
panic: tdsendsignal(): invalid signal 0
cpuid = 3
KDB: stack backtrace:
#0 0xffffffff80aada97 at kdb_backtrace+0x67
#1 0xffffffff80a6bb76 at vpanic+0x186
#2 0xffffffff80a6b9e3 at panic+0x43
#3 0xffffffff80a71bbd at tdsendsignal+0xcbd
#4 0xffffffff80a70be4 at trapsignal+0x184
#5 0xffffffff80edf3cd at trap+0x58d
#6 0xffffffff80ec3671 at calltrap+0x8
Uptime: 5h3m50s
Dumping 903 out of 16282 MB:..2%..11%..22%..31%..41%..52%..61%..71%..82%..91%

Reading symbols from /boot/kernel/zfs.ko...Reading symbols from
Reading symbols from /boot/kernel/opensolaris.ko...Reading symbols from
Reading symbols from /boot/kernel/uhid.ko...Reading symbols from
Reading symbols from /boot/kernel/pflog.ko...Reading symbols from
Reading symbols from /boot/kernel/pf.ko...Reading symbols from
__curthread () at ./machine/pcpu.h:222
222             __asm("movq %%gs:%1,%0" : "=r" (td)
(kgdb) #0  __curthread () at ./machine/pcpu.h:222
#1  doadump (textdump=<optimized out>)
    at /usr/src/sys/kern/kern_shutdown.c:298
#2  0xffffffff80a6b6f1 in kern_reboot (howto=260)
    at /usr/src/sys/kern/kern_shutdown.c:366
#3  0xffffffff80a6bbb0 in vpanic (fmt=<optimized out>, ap=0xfffffe0466890780)
    at /usr/src/sys/kern/kern_shutdown.c:759
#4  0xffffffff80a6b9e3 in panic (fmt=<unavailable>)
    at /usr/src/sys/kern/kern_shutdown.c:690
#5  0xffffffff80a71bbd in tdsendsignal (p=0xfffff80044340000, 
    td=0xfffff8004433b560, sig=<optimized out>, ksi=<unavailable>)
    at /usr/src/sys/kern/kern_sig.c:2137
#6  0xffffffff80a70be4 in trapsignal (td=<optimized out>, ksi=<optimized out>)
    at /usr/src/sys/kern/kern_sig.c:2021
#7  0xffffffff80edf3cd in trap (frame=0xfffffe0466890ac0)
    at /usr/src/sys/amd64/amd64/trap.c:578
#8  <signal handler called>
#9  0x000000080121e000 in ?? ()
Backtrace stopped: Cannot access memory at address 0x866800

I was suggested to inform "kib" about that. If someone needs a core file I can
upload it somewhere - but only on request because it's 1GB large...

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list