How hard would it be to:

1. identify the physical address that caused the trap

2. clear the trap

3. figure out if the address is user space or kernel space

4. if kernel, panic.

5. if user, kill the process, zap the contents of that page with zeros to
reset parity (should only get a parity error on a read, after all)

6. There Is No Rule Six!

My attempts to "mach halt" and "reboot" both failed from DDB - I had to
power cycle the machine to get it back.

	Erik <fair@clock.org>