Chris G. Demetriou writes:
 > does your machine crash with "panic: unexpected machine check", or
 > "panic: fatal machine check or error (unknown type)"?
 > 
 > It turns out that i disable correctable error reporting, so it
 > shouldn't be seeing machine check interrupts for correctable errors.
 > (I forgot about this earlier.)
 > 
 > It could be that disabling correctable error reporting turns
 > correctable errors into "real" machine checks somehow, but if so
 > that's not documented (that i'm aware of).
 > 
 > It'd probably make sense to enable correctable errors and print out
 > what i can about them, when they happen...
 > 
 > 
 > chris

I've gotten several like this:

 unexpected machine check:
 
     mces    = 0x19
     vector  = 0x670
     param   = 0xfffffc0000006060
     pc      = 0xfffffc0000300948
     ra      = 0xfffffc0000300bf4
     curproc = 0xfffffe004a5da800
         pid = 52, comm = syslogd
 
 panic: machine check
 syncing disks... 24 24 21 16 8 done

According to nm, it looks like it might be somewhere in copyoutstr,
with the ra somewhere in copyout.  (The kernel its referencing is the
ISP-enabled netbsd-GENERIC-970312).

Drew