Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

timer KASSERT running atf rump/rumpkern/t_sp

Hello, running ATF from the 2017-06-24 20:50 UTC build, the system
paniced with:
rump/rumpkern/t_sp (617/712): 10 test cases
    basic: [0.346508s] Passed.
    fork_fakeauth: [0.404515s] Passed.
    fork_pipecomm: [0.404736s] Passed.
    fork_simple: [0.420127s] Passed.
    reconnect: [2.353532s] Passed.
    signal: [0.345045s] Passed.
    sigsafe: panic: kernel diagnostic assertion "(c->c_flags & CALLOUT_PENDING) 
== 0" failed: file "/usr/src/sys/kern/kern_timeout.c", line 314 callout 0xffffa000012f0c60: c_func (0xffffffff804bacd2) c_flags (0x102) destroyed from 0xffffffff804babe5
cpu2: Begin traceback...
vpanic() at netbsd:vpanic+0x140
nd6_hint() at netbsd:nd6_hint
callout_destroy() at netbsd:callout_destroy+0x105
itimerfree() at netbsd:itimerfree+0xa5
timers_free() at netbsd:timers_free+0xe6
exit1() at netbsd:exit1+0x113
sys_exit() at netbsd:sys_exit+0x3d
syscall() at netbsd:syscall+0x9c
--- syscall (number 1) ---

Does it ring a bell ?

The 2017-06-23 21:40 UTC run did complete, but if it is a race it may not
reliably trigger ...

Manuel Bouyer <>
     NetBSD: 26 ans d'experience feront toujours la difference

Home | Main Index | Thread Index | Old Index