Re: panic: KSE: not on run queue
On Sat, 27 Jul 2002, Julian Elischer wrote: > On Sun, 28 Jul 2002, Gavin Atkinson wrote: > > 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. > > how new is the kernel? > When you created it did you make sure you deleted all .o files > first? Source was supped 26th july 1am (gmt). Kernel and world were built at the same time with make clean buildworld buildkernel. I was running portupgrade -RaO at the time, and two of the three panics were at the same point - after portupgrade has performed the pre-build clean, and has printed: ---> Upgrading 'xxx' to 'xxx' (xxx) ---> Building '/usr/ports/xxx' panic:... (xxx was gnomevfs the first time, and sawfish the second) > I'll check it in a while but the fact that only you cave sen thid does > suggest that maybe you have some mixed versions or something I will blow away the whole /usr/obj and recompile with fresh source. Thanks Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic: KSE: not on run queue
On Sun, 28 Jul 2002, Gavin Atkinson wrote: > hi, > > FreeBSD epsilon.ury.york.ac.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Jul 26 >13:32:52 BST 2002 [EMAIL PROTECTED]:/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. how new is the kernel? When you created it did you make sure you deleted all .o files first? > > 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 I'll check it in a while but the fact that only you cave sen thid does suggest that maybe you have some mixed versions or something > > Thanks > > Gavin >> > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic: KSE: not on run queue
hi, FreeBSD epsilon.ury.york.ac.uk 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Fri Jul 26 13:32:52 BST 2002 [EMAIL PROTECTED]:/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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
