Comment 2 for bug 1575860

Note that, coincidentally, a Windows host on the same network *also* bluescreened last night. If there's any chance the above could have been cause by, say, a power brownout, it's entirely possibly both machines were a victim of circumstance rather than bad code. Still, the bit where the kernel was able to register a BUG in the ringbuffer before locking up seems to indicate something worth reporting.