David Brownlee wrote:
> 
> 	If you just enter 'cont' it should continue trying to sync the
> 	disks and write the crashdump.

No luck: after a continue it rebooted, but got stuck with

/dev/rwd0a: MARKING FILE SYSTEM CLEAN
uvm_fault(0xf636a21c, 0x4d933000, 0, 1) -> 1
kernel: page fault trap, code=0
Stopped in fsck_ffs at  kprintf+0x9a:   movb    0(%eax),%cl
db> c
uvm_fault(0xf636a21c, 0x4d933000, 0, 1) -> 1
kernel: page fault trap, code=0
Stopped in fsck_ffs at  kprintf+0x9a:   movb    0(%eax),%cl
db> trace
kprintf(4d9330b0,5,0,0,f6400f40) at kprintf+0x9a
printf(4d9330b0) at printf+0x3a
wdgetdisklabel(0) at wdgetdisklabel+0x22
softclock(f04c5ac0,24b8,24b8,1,f6400fa0) at softclock+0x6a
hardclock(f6400fac,f6400fa8,f0100e12,f6400fac,0) at hardclock+0x1a5
clockintr(f6400fac) at clockintr+0xb
Xintr0() at Xintr0+0x6c
--- interrupt ---
0x804f223:
kernel: protection fault trap, code=0
Stopped in swapper at   wdc_ata_addref+0xe:     leave

then next time around

db>c
uvm_fault(0xf0246ce0, 0xf04d2000, 0, 1) -> 5
kernel: page fault trap, code=0
Stopped in swapper at   matchbiosdisks+0x30f:   movl    0(%eax,%edx,4),%eax
db> continue
kernel: page fault trap, code=0
Stopped at      pciide_dma_init+0x14e:  orb     $0x80,0xffffffff(%ecx,%ebx,8)
db>reboot
syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 giving up
rebooting...

so I presume that as it gave up, there is no core dump (this time it came
up fine - time to try a new kernel)

checking for core dump...
savecore: no core dump

Spoke to soon:

kernel: privileged instruction fault trap, code=0
Stopped in cron at      copyoutstr+0x2: movl    0xc(%esp),%esi

This is looking like hard ware problem..

But on the other thread, isn't there a function one can call to say
"make core dump now"?

Cheers,

Patrick