Re: [PATCH] [2.6] PPC64: log firmware errors during boot.

From: Jake Moilanen
Date: Thu Jul 08 2004 - 12:58:02 EST


On Thu, 8 Jul 2004 11:03:37 -0500
linas@xxxxxxxxxxxxxx wrote:

> On Tue, Jul 06, 2004 at 08:41:16AM -0500, Jake Moilanen wrote:
> >
> > > > Firmware can report errors at any time, and not atypically during boot.
> > > > However, these reports were being discarded until th rtasd comes up,
> > > > which occurs fairly late in the boot cycle. As a result, firmware
> > > > errors during boot were being silently ignored.
> >
> > Linas, the main consumer of error-log is events coming in from
> > event-scan. We don't call event-scan until rtasd is up (eg they are
> > queued in FW until we call event-scan).
>
> Actually, they don't seem to be queueed at all; when I turned on
> logging earlier, a whole pile of messages poped out that weren't
> visible before.

event-scan is called every 30 seconds. FW has to queue them.

If you are seeing a different pile of messages, I would imagine the
messages that popped out are not coming from event-scan then. Might be
last_error, which messages do not come in from event-scan. I can see
them not being logged in early boot.

A problem I could see, is if we make an rtas call before the VM
is up. The kmalloc for last_error won't like that.

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