>From ccsanady@bob.scl.ameslab.gov  Sat Nov  8 18:31:08 1997
>Thanks to all who responded..  Now I can show you a backtrace of what
>happened when my system went down. :)
>
>(gdb) target kcore netbsd.0.core
>panic: machine check
>#0  0xfffffc0000412da0 in dumpsys ()
>(gdb) bt
>#0  0xfffffc0000412da0 in dumpsys ()
>#1  0xfffffc0000412b38 in cpu_reboot ()
>#2  0xfffffc0000323034 in panic ()
>#3  0xfffffc0000411840 in machine_check ()
>#4  0xfffffc0000411548 in interrupt ()
>#5  0xfffffc00003003f8 in XentInt ()
>#6  0xfffffc0000300c70 in copyout ()
>
>What usually causes machine checks anyways?
>
>Chris
>
>

Machine checks are for exception conditions in alpha. Interrupts
as well as memory errors.

In -current (and for a while) all of the know machine check
conditions don't lead directly to a panic. There should have
been a printf like:

  panic("unexpected interrupt: type 0x%lx vec 0x%lx a2 0x%lx\n", a0, a1, a2);

What were the contents. What was the release && h/w you're running anyway
(I forget).

Also- it looks wierd that there's a machine check on a copyout.

-matt

p.s.: I'm moving this back to the port-alpha list- it's not for the
current-users list.