Hi everyone, I just had a strange panic with yesterday's current: FreeBSD relativity.student.utwente.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Fri Jan 28 16:15:13 CET 2000 root@:/usr/src/sys/compile/RELATIVITY5 i386 A backtrace seems impossible (but I'm inexperienced with kgdb and I'm also currently at work): djb@relativity:RELATIVITY5# gdb -k kernel /var/crash/vmcore.2 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... SMP -1071755716 cpus IdlePTD 146061567 initial pcb at 291320 panic messages: --- dmesg: cannot read PTD --- cannot read proc pointer at ff800004 (kgdb) bt #0 0x0 in ?? () (kgdb) where #0 0x0 in ?? () (kgdb) up No stack. (kgdb) The number of cpu's is supposed to be 2. If some more experienced/enlightened individual wishes to look into this, I have the crashdump on my system and I can provide (ssh) access. Please contact me. The panic seems to have been triggered by the killall command (executed as a user). Regards, Dave Boers. -- Dave Boers < djb @ relativity . student . utwente . nl > Don't let your schooling interfere with your education. (Mark Twain) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
