From: Diego Calleja <diegocg@gmail.com>
To: "Daniel Bonekeeper" <thehazard@gmail.com>
Cc: bunk@stusta.de, linux-kernel@vger.kernel.org
Subject: Re: Automatic Kernel Bug Report
Date: Sun, 9 Jul 2006 22:24:01 +0200 [thread overview]
Message-ID: <20060709222401.52168a58.diegocg@gmail.com> (raw)
In-Reply-To: <e1e1d5f40607091301j723b92bje147932a4395775c@mail.gmail.com>
El Sun, 9 Jul 2006 16:01:58 -0400,
"Daniel Bonekeeper" <thehazard@gmail.com> escribió:
> Independent of wheter you think that this is useful or not, do you see
> any cleaner way to send those reports, having in mind that the
> userspace may not be responsive ?
Kdump (http://lse.sourceforge.net/kdump/) would be useful for
many cases.
WRT to the bugs where the system completely locks up and doesn't
leaves any option for automatic bug reports: You don't really care
about those, because they're _so_ annoying that people reports them
manually.
next prev parent reply other threads:[~2006-07-09 20:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 8:45 Automatic Kernel Bug Report Daniel Bonekeeper
2006-07-09 9:45 ` Michal Piotrowski
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 [this message]
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=20060709222401.52168a58.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=bunk@stusta.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.