Adam K Kirchhoff <adamk@thorn.ashke.com> wrote:
> Adam K Kirchhoff <adamk@voicenet.com> wrote:
>> Sascha Wildner <saw@online.de> wrote:
>>> Adam K Kirchhoff wrote:
>>>> Unfortunately, I don't have a core file. Is there someway to force
>>>> it to generate one?
>>> Set the dumpdev in /etc/rc.conf, i.e.:
>>> dumpdev="/dev/ad0s1b"
>>> Upon reboot the core is then saved to /var/crash.
>> What do you do if the crash is happening before dumpon can read rc.conf
>> and execute? :-)
> Also, if you don't think you're going to have enough room in /var/crash,
> can you symlink that from another partition? :-)
After some googling, I see that dumpdev can be set as a variable in the
bootloader (this should be added to the help for the "set" command" in
the loader, imho). I rebooted, dropped to the bootloader command
prompt, set that variable to /dev/ad1s2b (my swap device) and rebooted.
When I got to the debug prompt, I ran "panic" to cause a panic. All I
got was the following 4 lines repeated over and over and over :-)
panic: assertion: gd->gd_vme_base != NULL in vm_map_entry_kreserve
mp_lock = 00000003; cpuid = 3; lapci_id = 07000000
boot() called on cpu#3
Uptime: 16s
The values change, as does the cpu#, but that's the error.
Am I missing some step in getting this core file?
Adam