Messages in this thread | | | Date | Thu, 8 Jul 2004 11:03:37 -0500 | From | linas@austin ... | Subject | Re: [PATCH] [2.6] PPC64: log firmware errors during boot. |
| |
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.
> The only events I see us > missing are epow events,
Depends on what you are doing. In my case, the fact that the early-boot messages were discarded was hiding a bug (that was causing those messages, that I've sent in a patch for).
--linas - 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/
| |