Issue #2355 has been updated by Francois Tigeot. % Done changed from 0 to 10
I got the same sort of panic on a 24-threads xeon box: rtrequest1_msghandler: rtrequest table error was cpu16, err 17 Core dump available on leaf:~ftigeot/crash/crash.rtrequest1_msghandler ---------------------------------------- Bug #2355: panic: rtrequest1_msghandler: rtrequest table error was cpu4, err 17 http://bugs.dragonflybsd.org/issues/2355 Author: Joachim de Groot Status: New Priority: Normal Assignee: Category: Target version: I experimented with wlan and dhcp and had some trouble to get it to work. To start from scratch, I've deleted the generated interface wlan0 after running /etc/rc.d/netif stop. At some point after running /etc/rc.d/netif start again this panic occurs. This is reproducible. Version String: DragonFly v3.1.0.347.g228a6-DEVELOPMENT #4: Mon Mar 19 08:37:17 CET 2012 #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 0xffffffff802f9b62 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:937 #3 0xffffffff802fa1c6 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:387 #4 0xffffffff802fa47d in panic (fmt=0xffffffff805b26a8 "rtrequest1_msghandler: rtrequest table error was cpu%d, err %d\n") at /usr/src/sys/kern/kern_shutdown.c:843 #5 0xffffffff8039d657 in rtrequest1_msghandler (msg=<optimized out>) at /usr/src/sys/net/route.c:815 #6 0xffffffff8039bc70 in rtable_service_loop (dummy=<optimized out>) at /usr/src/sys/net/route.c:205 #7 0xffffffff80305300 in lwkt_deschedule_self (td=<unavailable>) at /usr/src/sys/kern/lwkt_thread.c:362 Backtrace stopped: previous frame inner to this frame (corrupt stack?) A dump is available. -- 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