Bug #2202

DFBSD v2.13.0.278.g46437 - panic: assertion "td->td_gd == mycpu" failed in setrunnable

Added by tuxillo almost 3 years ago. Updated almost 3 years ago.

Status:ClosedStart date:11/16/2011
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi,

After less than a day of uptime, I got the following panic:

Unread portion of the kernel message buffer:
panic: assertion "td->td_gd == mycpu" failed in setrunnable at /home/source/dfbsd/sys/kern/kern_synch.c:1041
cpuid = 3
Trace beginning at frame 0xffffffe0e4bb69a8
panic() at panic+0x1fb
panic() at panic+0x1fb
setrunnable() at setrunnable+0x8c
lwp_signotify() at lwp_signotify+0xa0
lwpsignal() at lwpsignal+0x7ac
kern_kill() at kern_kill+0x186
sys_lwp_kill() at sys_lwp_kill+0x38
syscall2() at syscall2+0x370
Xfast_syscall() at Xfast_syscall+0xcb
boot() called on cpu#3
Uptime: 18h17m29s
Physical memory: 6019 MB
Dumping 1873 MB: 1858 1842 1826 1810 1794 1778 1762 1746 1730 1714 1698 1682 1666 1650 1634 1618 1602 1586 1570 1554 1538 1522 1506 1490 14
74 1458 1442 1426 1410 1394 1378 1362 1346 1330 1314 1298 1282 1266 1250 1234 1218 1202 1186 1170 1154 1138 1122 1106 1090 1074 1058 1042 1
026 1010 994 978 962 946 930 914 898 882 866 850 834 818 802 786 770 754 738 722 706 690 674 658 642 626 610 594 578 562 546 530 514 498 48
2 466 450 434 418 402 386 370 354 338 322 306 290 274 258 242 226 210 194 178 162 146 130 114 98 82 66 50 34 18 2

KGDB backtrace is:

(kgdb) bt
#0 0xffffffff804a8cae in lwkt_switch () at /home/source/dfbsd/sys/kern/lwkt_thread.c:929
#1 0xffffffff804a9473 in lwkt_yield () at /home/source/dfbsd/sys/kern/lwkt_thread.c:1187
#2 0xffffffff804a4f00 in bsd4_acquire_curproc (lp=0xffffffff804a62a1) at /home/source/dfbsd/sys/kern/usched_bsd4.c:263
#3 0xffffffff8075b771 in syscall2 (frame=0xffffffe0e418cc08) at /home/source/dfbsd/sys/platform/pc64/x86_64/trap.c:1247
#4 0xffffffff80753a0b in Xfast_syscall () at /home/source/dfbsd/sys/platform/pc64/x86_64/exception.S:321
#5 0x000000000000002b in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

I got the coredump on demand to be uploaded to leaf.

Cheers,
Antonio Huete

History

#1 Updated by tuxillo almost 3 years ago

  • Status changed from New to In Progress

As specified by dillon, it can be fixed in commit (3813baa3a4e1aeb63d3f1b1412fdc64c513975ce - kernel - Major signal path adjustments (2))

#2 Updated by tuxillo almost 3 years ago

  • Priority changed from Normal to High

#3 Updated by ftigeot almost 3 years ago

  • Status changed from In Progress to Resolved

Should be fixed in commit 81cd8ede74a6a09d318c1642787a8b8936374786
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/81cd8ede74a6a09d318c1642787a8b8936374786

#4 Updated by tuxillo almost 3 years ago

  • Status changed from Resolved to Closed

It's gone after the commit specified by Francois

Also available in: Atom PDF