From: Hollis Blanchard <hollisb@us.ibm.com>
To: nfont@austin.ibm.com
Cc: Paul Mackerras <paulus@samba.org>,
linas@austin.ibm.com, linuxppc64-dev@lists.linuxppc.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.6] PPC64: log firmware errors during boot.
Date: Fri, 02 Jul 2004 12:29:08 -0500 [thread overview]
Message-ID: <1088789345.26946.9.camel@localhost> (raw)
In-Reply-To: <40E58AE9.6050009@austin.ibm.com>
On Fri, 2004-07-02 at 11:18, Nathan Fontenot wrote:
> > I asked about this before, and was told that there is no way to
> > determine the severity of an event without doing full parsing of the
> > binary data. I'd be thrilled to be wrong...
>
> Gettting the severity of an RTAS event is possible, and not too
> difficult. Check out asm-ppc64/rtas.h for a definition of the
> RTAS event header (struct rtas_error_log). All RTAS events have the
> same initial header containing the severity of the event.
Great! Of course that won't help much if we get repeating "important"
events that aren't even interesting much less important, but it's worth
trying to printk only the important ones and leave the rest to netlink.
Note that currently we printk them all as KERN_DEBUG messages. Although
they aren't spewed to console, they still take up (lots of) space in the
printk buffer, and dmesg is still afflicted too...
--
Hollis Blanchard
IBM Linux Technology Center
next prev parent reply other threads:[~2004-07-02 17:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 0:10 [PATCH] [2.6] PPC64: log firmware errors during boot linas
2004-06-30 10:55 ` Paul Mackerras
2004-07-01 21:06 ` linas
2004-07-02 5:36 ` Greg KH
2004-07-02 10:44 ` Paul Mackerras
2004-07-02 14:15 ` Hollis Blanchard
2004-07-02 16:18 ` Nathan Fontenot
2004-07-02 17:29 ` Hollis Blanchard [this message]
2004-07-02 18:13 ` linas
2004-07-02 18:27 ` Greg KH
2004-07-02 18:55 ` Dave Hansen
2004-07-02 19:44 ` Greg KH
2004-07-06 13:24 ` Jake Moilanen
2004-07-06 13:41 ` Jake Moilanen
2004-07-08 16:03 ` linas
2004-07-08 17:55 ` Jake Moilanen
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=1088789345.26946.9.camel@localhost \
--to=hollisb@us.ibm.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=nfont@austin.ibm.com \
--cc=paulus@samba.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