Date: Sun, 28 Jul 2002 00:15:09 +0100 (BST) From: Gavin Atkinson <gavin@ury.york.ac.uk> To: <current@freebsd.org> Cc: <julian@elischer.org> Subject: panic: KSE: not on run queue Message-ID: <Pine.BSF.4.33.0207280005560.52083-100000@ury.york.ac.uk>
next in thread | raw e-mail | index | archive | help
hi, FreeBSD epsilon.ury.york.ac.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Jul 26 13:32:52 BST 2002 root@epsilon.ury.york.ac.uk:/usr/obj/usr/src/sys/EPSILON i386 Had this panic twice with current -current on an uniprocessor machine and kernel. Dumps still don't work... Both occurances, i had an ssh running, a portupgrade in progress, and the dnetc client running in the background. panic: KSE not on run queue panic: from debugger Uptime: 1d1h26m12s Dumping 127 MB ata0: resetting devices .. panic: mi_switch: switch in a critical section Uptime: 1d1h26m12s panic: witness_destroy: lock (sleep mutex) pseudofs_vncache is not initialized Uptime: 1d1h26m12s panic: _sx_xlock (shutdown_post_sync): xlock already held @ /usr/src/sys/kern/kern_shutdown.c:341 Uptime: 1d1h26m12s panic: _sx_xlock (shutdown_post_sync): xlock already held @ /usr/src/sys/kern/kern_shutdown.c:341 Uptime: 1d1h26m12s ...etc... traceback from ddb is: panic runq_remove remrunqueue schedcpu softclock thread_loop forkexit forktrampoline Thanks Gavin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.33.0207280005560.52083-100000>