From: Wolfgang Denk <wd@denx.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
Mike Frysinger <vapier@gentoo.org>,
Greg Ungerer <gerg@snapgear.com>,
Paul Mundt <lethal@linux-sh.org>, Tim Bird <tim.bird@am.sony.com>,
Grant Erickson <gerickson@nuovations.com>,
linux-embedded <linux-embedded@vger.kernel.org>
Subject: Re: Kernel crashing and log buffers...
Date: Sat, 13 Jun 2009 20:59:26 +0200 [thread overview]
Message-ID: <20090613185926.BAB66832E416@gemini.denx.de> (raw)
In-Reply-To: <20090613102642.GB7976@flint.arm.linux.org.uk>
Dear Russell King,
In message <20090613102642.GB7976@flint.arm.linux.org.uk> you wrote:
>
> The other way I've seen people read out crash messages is using a
> debugger to dump the kernel's log buffer directly. That seems to work
> as well as any other method, and has the advantage that it doesn't
> require any kernel modifications.
This works well in the lab during hardware bringup or BSP development.
But we are also interested in a solution that allows to get more or
less automatic access to the log buffer content after a crash - when
you have several ten thousand systems in the field, such a feature
can save you a lot of money.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
next prev parent reply other threads:[~2009-06-13 18:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 1:26 Kernel crashing and log buffers Robin Getz
2009-06-11 17:53 ` David VomLehn
2009-06-11 18:22 ` Tim Bird
2009-06-11 22:46 ` David VomLehn
2009-06-11 18:52 ` Robin Getz
2009-06-11 19:35 ` David VomLehn
2009-06-11 22:57 ` Grant Erickson
2009-06-12 0:33 ` David VomLehn
2009-06-12 5:33 ` Wolfgang Denk
2009-06-11 23:27 ` Mike Frysinger
2009-06-12 1:07 ` David VomLehn
2009-06-12 4:54 ` Robin Getz
2009-06-13 16:49 ` Jamie Lokier
2009-06-26 14:39 ` Robin Getz
2009-06-26 17:42 ` David VomLehn
2009-06-26 17:50 ` Mike Frysinger
2009-06-26 17:59 ` Robin Getz
2009-06-13 10:26 ` Russell King
2009-06-13 18:59 ` Wolfgang Denk [this message]
2009-06-14 18:33 ` Robin Getz
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=20090613185926.BAB66832E416@gemini.denx.de \
--to=wd@denx.de \
--cc=gerg@snapgear.com \
--cc=gerickson@nuovations.com \
--cc=lethal@linux-sh.org \
--cc=linux-embedded@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=rmk@arm.linux.org.uk \
--cc=tim.bird@am.sony.com \
--cc=vapier@gentoo.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;
as well as URLs for NNTP newsgroup(s).