We'll be spending the next six months stabilising and hardening
the used-to-be-2.5 kernel. If grunts like me can get hold a
copy of the other person's kernel image from time-of-crash, that
has a ton of value.
(Disclaimer: I've never used lkcd. I'm assuming that it's
possible to gdb around in a dump)
> In particular when it comes to this project, I'm told about
> "netdump", which doesn't try to dump to a disk, but over the net.
It could help. But like serial console, the random person whose
kernel just died often can't be bothered setting it up, or simply
doesn't have the gear, or the crash is not repeatable.
So. _If_ lkcd gives me gdb-able images from time-of-crash, I'd
like it please. And I'm the grunt who spent nearly two years
doing not much else apart from working 2.3/2.4 oops reports.
Oh, and as Rusty has pointed out, we lose a *lot* of oops reports
because users are in X and the backtrace doesn't make it to the
logs. Rusty has a little app which dumps just the oops report to
disk somewhere. Want that too.
-
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/