On Fri, 9 Jan 2009 14:52:33 -0500 Theodore Tso <tytso@xxxxxxx> wrote: > On Fri, Jan 09, 2009 at 07:55:09PM +0100, Andi Kleen wrote: > > > But _users_ just get their oopses sent automatically. So it's not > > > about > > > > If they send it from distro kernels the automated oops sender could > > just fetch the debuginfo rpm and decode it down to a line. > > My old automatic user segfault uploader I did originally > > for the core pipe code did that too. > > Fetch a gigabyte's worth of data for the debuginfo RPM? Um, I think > most users would not be happy with that, especially if they are behind > a slow network. Including the necessary information so someone who > wants to investigate the oops, or having kerneloops.org pull apart the > oops makes more sense, I think, and is already done. > it is. > Something that would be **really** useful would be a web page where if > someone sends me an oops message from Fedora or Open SUSE kernel to > linux-kernel or linux-ext4, I could take the oops message, cut and > paste it into a web page, along with the kernel version information, > and the kernel developer could get back a decoded oops information > with line number information. > > Kerneloops.org does this, so the code is mostly written; but it does > this in a blinded fashion, so it only makes sense for oops which are > very common and for which we don't need to ask the user, "so what were > you doing at the time". In cases where the user has already stepped > up and reported the oops on a mailing list, it would be nice if > kerneloops.org had a way of decoding the oops via some web page. > > Arjan, would something like this be doable, hopefully without too much > effort? I suppose it could be done if the exact idea is there, and it would be nice if I'd get help from the distro kernel mainainers so that they'll send me the vmlinux'n ;) -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
