From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Daniel Bonekeeper" <thehazard@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Automatic Kernel Bug Report
Date: Sun, 9 Jul 2006 11:45:06 +0200 [thread overview]
Message-ID: <6bffcb0e0607090245t2dbcd394n86ce91eec661f215@mail.gmail.com> (raw)
In-Reply-To: <e1e1d5f40607090145k365c0009ia3448d71290154c@mail.gmail.com>
Hi Daniel,
On 09/07/06, Daniel Bonekeeper <thehazard@gmail.com> wrote:
> Well this probably was already discussed. Some distros have automatic
> bug reporting tools that are triggered when something bad happens
> (don't know if includes kernel stuff). But have anybody thought about
> some kind of bug report tool that, under an Oops like a NULL point
> dereference, it creates for example a packed file with the config used
> to build the kernel, the kernel version, loaded modules, some hardware
> info, backtraces, everything that could be useful for debugging, and
> sends to a server to be catalogued ?
How about oops reporting tool?
http://www.stardust.webpages.pl/files/ort/
[snip]
>
> Wouldn't that be helpful ?
>
> Daniel
>
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)
next prev parent reply other threads:[~2006-07-09 9:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 8:45 Daniel Bonekeeper
2006-07-09 9:45 ` Michal Piotrowski [this message]
2006-07-09 10:29 ` Daniel Bonekeeper
2006-07-09 12:58 ` Adrian Bunk
2006-07-09 18:46 ` Daniel Bonekeeper
2006-07-09 19:11 ` Adrian Bunk
2006-07-09 20:01 ` Daniel Bonekeeper
2006-07-09 20:19 ` Valdis.Kletnieks
2006-07-09 20:27 ` Daniel Bonekeeper
2006-07-10 8:11 ` Pavel Machek
2006-07-10 17:40 ` Daniel Bonekeeper
2006-07-10 17:59 ` Valdis.Kletnieks
2006-07-10 22:05 ` Daniel Bonekeeper
2006-07-10 23:41 ` Lee Revell
2006-07-11 1:15 ` Daniel Bonekeeper
2006-07-10 18:41 ` Horst von Brand
2006-07-10 21:34 ` Daniel Bonekeeper
2006-07-11 14:16 ` Horst von Brand
2006-07-09 20:24 ` Diego Calleja
2006-07-09 20:37 ` Daniel Bonekeeper
2006-07-09 22:19 ` Diego Calleja
2006-07-09 22:49 ` Daniel Bonekeeper
2006-07-09 20:25 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bffcb0e0607090245t2dbcd394n86ce91eec661f215@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thehazard@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®