panic("bogons in the VM system!");

Slashdot posted to Remotely Crash OpenBSD as panic("bogons in the VM system!");:

A crash means you killed, not just a task, but the whole system. In a system as robust as BSD this usually means that the code that was corrupted by the exploit was running at a kernel permission level. So if you can take it over you can get it to give you any permission you want.

You make a good point.

However, keep in mind that there are quite a few areas in (all?) BSD-derived IP stacks where a seriously malformed packet will cause the kernel itself to throw up it's hands and call panic("WTF?!?").

$ grep panic /usr/src/sys/netinet6/*.c | wc -l
42

I've found that just about any system will eventually panic if you sic ISIC at it from within the same subnet.

Cool OpenBSD kernel panic messages:

panic("can't happen: system seems to have no memory!");
panic("pmap_init: bogons in the VM system!");

or the elegantly simple:

panic("something is wrong");
panic("for safety");