Messages in this thread |  | | From | Chris Johns <> | Subject | Dumping kernel log (dmesg) and backtraces after a panic | Date | Fri, 20 Aug 2004 21:21:05 -0500 |
| |
We're using Red Hat EL3 Linux (2.4.21 base kernel plus 300 or so Red Hat and/or community patches) and I'm dearly missing KDB already, since we previously used 2.4.21 from kernel.org and applied the appropriate KDB patch(es). Now with EL3, I'm not even sure what the right patch for KDB would be.
The problem is how to debug a hang or panic without KDB. Specifically, I'd like to dump out real backtraces of all (or selected) processes instead of the pseudo-backtraces that the panic or Alt-Sysrq-t provides, and I'd like to dump out the kernel log buffer (dmesg) after a hang or panic.
When I say "pseudo-backtraces", it seems that the oops/sysrq processing picks everything that looks like a text address from the stack of each thread (or the thread that caused the panic) and formats it, rather than walking the stack back correctly like KDB's 'bt' command does. And I don't know of any way of getting the 'dmesg' output after a hang/panic other than by using KDB.
To put it simply, is there either an alternative to KDB that works with RH EL3 and provides what I need (bt and dmesg, or just dmesg), or is there a version of KDB that would work with EL3 already?
Thanks,
Chris Johns
- 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/
|  |