[DragonFlyBSD - Bug #2092] Panic: Bad link elm 0x... next->prev
Issue #2092 has been updated by Magliano Andrea.
https://84.73.12.43/crash/core23.txz is quite big (244M) but shows clearly data in the call level where KKASSERT(xa->state != ATA_S_PUT) fails (patch in previous comment applies too).
Core was manually generated after dropping in ddb and executing 'next', as DDB_UNATTENDED led to no dump.
Running v2.13.0.437.g2b9050-DEVELOPMENT.
(kgdb) bt
#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 0xffffffff802c5485 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:925
#3 0xffffffff802c5aeb in boot (howto=260)
at /usr/src/sys/kern/kern_shutdown.c:387
#4 0xffffffff802c5da2 in panic (
fmt=0xffffffff805891b8 "trap: extra tokens held after trap! %ld/%ld")
at /usr/src/sys/kern/kern_shutdown.c:831
#5 0xffffffff804e5ba5 in trap (frame=0xffffffe0416dba08)
at /usr/src/sys/platform/pc64/x86_64/trap.c:814
#6 0xffffffff804de05e in calltrap ()
at /usr/src/sys/platform/pc64/x86_64/exception.S:187
#7 0xffffffff804dfa0f in breakpoint () at ./cpu/cpufunc.h:73
#8 Debugger (msg=<optimized out>)
at /usr/src/sys/platform/pc64/x86_64/db_interface.c:361
#9 0xffffffff802c5d82 in panic (
fmt=0xffffffff81823380 "assertion \"%s\" failed in %s at %s:%u")
at /usr/src/sys/kern/kern_shutdown.c:822
#10 0xffffffff8181e57f in ahci_ata_cmd_done (ccb=0xffffffe041e4ceb0)
at /usr/src/sys/dev/disk/ahci/ahci.c:3562
#11 0xffffffff8182117b in ahci_port_intr (ap=0xffffffe041e38f38,
blockable=<optimized out>) at /usr/src/sys/dev/disk/ahci/ahci.c:3010
#12 0xffffffff81821391 in ahci_intr (arg=<optimized out>)
at /usr/src/sys/dev/disk/ahci/ahci.c:2352
#13 0xffffffff80295174 in ithread_handler (arg=<optimized out>)
at /usr/src/sys/kern/kern_intr.c:837
#14 0xffffffff802d2cad in lwkt_deschedule_self (td=0x0)
at /usr/src/sys/kern/lwkt_thread.c:357
----------------------------------------
Bug #2092: Panic: Bad link elm 0x... next->prev != elm
http://bugs.dragonflybsd.org/issues/2092
Author: Magliano Andrea
Status: New
Priority: Normal
Assignee: Matthew Dillon
Category:
Target version:
Hi all,
i'm running v2.11.0.397.g4b06a0-DEVELOPMENT x86_64
I got this kind of panic on a daily basis, always at night (probably
while hammer does reblocking?):
Jun 20 03:09:14 randy kernel: ahci0.1: disk_rw: unknown state 6
Jun 20 03:09:14 randy last message repeated 18 times
Jun 20 03:09:14 randy kernel: panic: Bad link elm 0xffffffe01e019e78
next->prev != elm
Jun 20 03:09:14 randy kernel: cpuid = 0
Jun 20 03:09:14 randy kernel: Trace beginning at frame 0xffffffe01de1fa00
Jun 20 03:09:14 randy kernel: panic() at panic+0x1ed
Jun 20 03:09:14 randy kernel: panic() at panic+0x1ed
Jun 20 03:09:14 randy kernel: camisr_runqueue() at camisr_runqueue+0x87
Jun 20 03:09:14 randy kernel: swi_cambio() at swi_cambio+0x169
Jun 20 03:09:14 randy kernel: ithread_handler() at ithread_handler+0x1ba
Jun 20 03:09:14 randy kernel: boot() called on cpu#0
After applying these two patches it's running stable since 4 days.
The difference is now that TAILQ_EMPTY (patch 0002) is in
camisr_runqueue() *and* is protected by a spinlock too. The last maybe
fixes the panic? Does it makes sense?
ByE!
--
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
討論串 (同標題文章)
完整討論串 (本文為第 3 之 3 篇)：