DragonFly BSD
DragonFly bugs List (threaded) for 2012-01
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

[DragonFlyBSD - Bug #2269] Panic on KKASSERT((c->c_flags & (CALLOUT_PENDING|CALLOUT_ACTIVE))


From: "G. Isenmann via Redmine" <bugtracker-admin@xxxxxxxxxxxxxxxxxxxxx>
Date: Thu, 19 Jan 2012 06:04:06 -0800

Issue #2269 has been updated by G. Isenmann.


Since the upgrade from 2.12 to master last friday, I see this panic:
assertion "(c->c_flags & (CALLOUT_PENDING|CALLOUT_ACTIVE)) == 0"
failed in callout_stop_sync at /usr/src/sys/kern/kern_timeout.c:519
regularly.

Have just seen this panic again after an update to v2.13.0.964.g2c5c4
and about 1h uptime.

----------------------------------------
Bug #2269: Panic on KKASSERT((c->c_flags & (CALLOUT_PENDING|CALLOUT_ACTIVE))
http://bugs.dragonflybsd.org/issues/2269

Author: Magliano Andrea
Status: New
Priority: Normal
Assignee: 
Category: 
Target version: 


On v2.13.0.784.gc1745-DEVELOPMENT, x86_64

#0  _get_mycpu () at ./machine/thread.h:69
#1  md_dumpsys (di=<optimized out>)
    at /usr/src/sys/platform/pc64/x86_64/dump_machdep.c:263
#2  0xffffffff802bd915 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:925
#3  0xffffffff802bdf7b in boot (howto=260)
    at /usr/src/sys/kern/kern_shutdown.c:387
#4  0xffffffff802be232 in panic (
    fmt=0xffffffff8051bdf0 "assertion \"%s\" failed in %s at %s:%u")
    at /usr/src/sys/kern/kern_shutdown.c:831
#5  0xffffffff802dbeb7 in callout_stop_sync (c=0xffffffe065c82990)
    at /usr/src/sys/kern/kern_timeout.c:519
#6  0xffffffff802dadd0 in sys_setitimer (uap=0xffffffe066028b68)
    at /usr/src/sys/kern/kern_time.c:762
#7  0xffffffff804de981 in syscall2 (frame=0xffffffe066028c18)
    at /usr/src/sys/platform/pc64/x86_64/trap.c:1248
#8  0xffffffff804c806b in Xfast_syscall ()
    at /usr/src/sys/platform/pc64/x86_64/exception.S:323
#9  0x000000000000002b in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Get dump from https://84.73.12.43/crash/core25.txz

I'm still experiencing regularly issue 2092, it could be related to it as ahci_ata_cmd_done() calls callout_stop_sync() (which panic comes from)


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account



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