Another panic

2003-11-20 Thread vze2ztys
FreeBSD bogushost2 5.1-CURRENT FreeBSD 5.1-CURRENT #7: Tue Nov 18 18:36:56 EST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ARL5KERNEL i386 Another panic that occured just after loading and attempting to play an audio CD: (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1

another panic for your viewing pleasure

2003-11-17 Thread vze2ztys
I think this one occured as a result of cdcontrol -f /dev/acd1 p, but I can't be sure. (kgdb) bt #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240 #1 0xc04c7ce4 in boot (howto=0x100) at /usr/src/sys/kern/kern_shutdown.c:372 #2 0xc04c8088 in panic () at

kldload(2) and debug kernels

2003-11-16 Thread vze2ztys
It looks like the kldload system call takes the name of the module you give it, like ums, and just tacks on .ko and searches in whatever the default paths are for kernel modules until it finds ums.ko. Peachy. But what about if you built your kernel and modules with debugging symbols added in?

Small bug with pppctl

2003-11-07 Thread vze2ztys
Hello, I noticed that using pppctl interactively doesn't work quite right, at least for certain commands that produce a lot of output. I cut and pasted a few invocations to show what works and what doesn't quite work: $ pppctl /var/ppp/ppp PPP ON bogushost2 show route Destination