From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] DMI: log system, BIOS, and board information
Date: Wed, 29 Sep 2010 15:35:12 -0600 [thread overview]
Message-ID: <201009291535.12969.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20100929222623.4b020427@lxorguk.ukuu.org.uk>
On Wednesday, September 29, 2010 03:26:23 pm Alan Cox wrote:
> On Wed, 29 Sep 2010 12:24:02 -0600
> Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
> >
> > Put basic system information in the dmesg log. There are lots of dmesg
> > logs on the web, and it would be useful if they contained this information
> > for debugging platform problems.
> >
> > DMI often doesn't supply a board name, but I assume the others are pretty
> > standard.
>
> You need to filter the characters before printing them in the log. Some
> platforms contain binary garbage.
Oh, good point. Filtering sounds feasible in concept, at least.
> It's also the wrong thing in most cases because the key data is in sysfs
> so your bug capturing tool can collect it.
Sure, there's no question that this information and a lot more is
easily available elsewhere.
Most of the bug reports I see are not generated by bug capturing
tools; they're generated by Joe User posting a dmesg log. For many
platform issues, it would be quite useful if that log already contained
a hint about what platform it is. The collection of dmesg logs on
the web + Google indexing + a platform ID would be a great help in
locating similar failures and contacting testers.
Bjorn
prev parent reply other threads:[~2010-09-29 21:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 18:24 Bjorn Helgaas
2010-09-29 21:26 ` Alan Cox
2010-09-29 21:35 ` Bjorn Helgaas [this message]
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=201009291535.12969.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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®