Hi,

I've tried several times to make kernel dump core to dump device and 
restart, but the ddb never completed the job. It just hangs. I thought 
that the problem could be raidframe dump device or mp kernel, but ddb 
hangs even on non-mp kernel and ordinary wd dump device. Sometimes the 
ddb hangs right after:

Stopped at netbsd:cpu_Debugger+0x1: ret
db{0}> sync
syncing disks... done

and sometimes it prints:

satalink0:3:0: lost interrupt
  type: ata tc_bcount: 2048 tc_skip: 0
satalink0:2:0: lost interrupt
  type: ata tc_bcount: 2048 tc_skip: 0

yet. Savecore on consequent boot never saved anything. I don't really 
understand these things so what do you think is wrong here? It's amd64 
machine with 2 processors, kernel 2.0_STABLE.

Are these valid examples how to set dump device to whatever I want on 
startup using fstab:
/dev/raid4a none swap sw,dp 0 0
or
/dev/wd2a none swap dp 0 0
?
(I miss some fstab example for dump devices in 
/usr/share/examples/fstab/ ). What if there are more dump devices 
configured in fstab (makes it sense?)?

Thanks,

r.