FreeBSD 9.1-RELEASE-p3 instruction pointer = 0x20:0xc0aae65 current process = 99556 (reboot) nm -n /boot/kernel.old9.1/kernel | grep 0x c06ab840 t ed_rtl80x9_media_ioctl c06ab870 T ed_probe_RTL80x9 c06ac950 t ed_pccard_dl100xx_mii_readbits c06aca40 t ed_pccard_dl100xx_mii_writebits c09ac8d0 t xl_txeof_90xB c09ae640 t xl_start_90xB_locked c0ed4150 T ed_probe_WD80x3_generic c0ed4bc0 T ed_probe_WD80x3 c0f36640 T Xint0x80_syscall c0f40930 t topo_probe_0x4
Can you do 'gdb /boot/kernel.old9.1/kernel' and then 'l *0xc0aae65'? Also, can you provide more details about your system (e.g. do you have an ed(4) or xl(4) NIC)? A non-verbose dmesg would be a good start.
Created attachment 147207 [details] dmesg
(In reply to John Baldwin from comment #1) > Can you do 'gdb /boot/kernel.old9.1/kernel' and then 'l *0xc0aae65'? l *0xc0aae65 No symbol table is loaded. Use the "file" command I think, I do it wrong... >Also, can you provide more details about your system (e.g. do you have an ed(4) or > xl(4) NIC)? A non-verbose dmesg would be a good start. No, I haven't ed(4) or xl(4). I add dmesg as attachments.
Ok, I guess the 9.1 kernel did not ship with debug symbols. You can do 'nm -n /boot/kernel.old9.1/kernel | grep c0aae' which might narrow things down some.
(In reply to John Baldwin from comment #4) > Ok, I guess the 9.1 kernel did not ship with debug symbols. You can do 'nm > -n /boot/kernel.old9.1/kernel | grep c0aae' which might narrow things down > some. nm -n /boot/kernel.old9.1/kernel | grep c0aae c0aae160 t idle_setup c0aae280 T intr_handler_source c0aae2a0 t swi_assign_cpu c0aae2b0 T intr_priority c0aae310 t sysctl_intrcnt c0aae340 t sysctl_intrnames c0aae370 t intr_event_schedule_thread c0aae470 T intr_event_execute_handlers c0aae630 t intr_lookup c0aae6f0 t ithread_update c0aae790 t intr_event_update c0aae8d0 T intr_event_remove_handler c0aaeae0 T swi_remove c0aaeb00 T intr_event_add_handler c0aaef10 T intr_event_bind nm -n /boot/kernel.old9.1/kernel | grep c0aae6 c0aae630 t intr_lookup c0aae6f0 t ithread_update
Let us know if this is a problem with newer FreeBSD versions. Clearly this panic on this FreeBSD version isn't going to get fixed.