Has anyone ever thought about that fact that although the dog might bark (printk), klogd may be deaf in some cases? It seems to me that there will be cases where this happens and thus we see no data.
I don't know if all x86 hardware has this, but I know that the couple of systems I typically use have a small amount of battery backed ram that is available for use in the RTC. Anyone ever write a patch to dump data (small stack trace) to this memory so it can be retrieved after a reboot? It seems to me that some data is better than none... Of course it would be nice to know what the lowest common denominator is so that one patch will work with all PC hardware but I don't even know if a general approach is really feasible.
Regards,
Scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/