lkml.org 
[lkml]   [2004]   [Jul]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] [2.6] PPC64: log firmware errors during boot.
On Fri, Jul 02, 2004 at 01:13:47PM -0500, linas@austin.ibm.com wrote:
>
> On Fri, Jul 02, 2004 at 12:29:08PM -0500, Hollis Blanchard wrote:
> > 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.
>
> OK,
>
> I'd like to wait until some of the current patches get in, so as to
> avoid a case of patch-versionitis.
>
> I mis-spoke earlier about who the intendend consumers of the printk'ed
> messages are; rtasd already implements its own kernl-to-user interface
> via the /proc interface. Yes, everything in /proc/ppc64 is prolly
> deprecated, but lets put this off till later.

Later when?

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:04    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site