> for the symbol resolution to be done later, someone will have to
> manually transcribe the oops message (most of the time), when
> the kernel knows that it's in bad shape you really don't want
> to have it writing to a disk (it may end up writing over your data)
Maybe on production systems, but on test systems you really do want those
oopses stored automatically somewhere (separate disk partition without
filesystem has worked without problems for over a year).
If disk is too risky for Oops information, send them to serial or over
network and have at the other end something that automatically resolves
the oopses properly with kernel debug symbols (which you've separated from
the kernel binary after it's been built).