Server panicked about midnight PST.. Really not much more to say..
|-||Grizzly666||2s||BEAT THEIR FACE IN.|
|-||Mory||8s||Jikook ftw. Army for lyf.|
|-||Kiwi||3m||I guess there's always something killing me.|
|c||Butako||35s||Butakooooo the builder. Can she fix it? Eh.|
|-||Baguette||7h||thanks, i hate it|
|j||Johnny||4h||New Code Written Nightly. Not a GM.|
|And 22 more hiding and/or disguised|
In our case, a sig 11.
Signal 11, or officially know as "segmentation fault", means that the program accessed a memory location that was not assigned.
Mainly this happens (in stable production systems like ours) due to timing problems in the CPU <-> cache <-> memory path, but other explinations include stray alpha particles randomly flipping a bit, and of course, software bugs.
I'm pretty convinced it's not a LambdaMOO issue (if it were we should be able to reproduce it with the same hour old database before the panic), which leaves my custom compiled kernel, and the hardware as the possible culprits.
Take your pick.
One day I may upgrade the kernel to a newer version, but as this one has been solid save a few panics after 2+ months straight of uptime, It's not a priority. Why fix what's (mostly) not broken?