From: linas@austin.ibm.com
To: Jake Moilanen <moilanen@austin.ibm.com>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.6] PPC64: log firmware errors during boot.
Date: Thu, 8 Jul 2004 11:03:37 -0500 [thread overview]
Message-ID: <20040708110337.N21634@forte.austin.ibm.com> (raw)
In-Reply-To: <20040706084116.11ab7988.moilanen@austin.ibm.com>; from moilanen@austin.ibm.com on Tue, Jul 06, 2004 at 08:41:16AM -0500
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
next prev parent reply other threads:[~2004-07-08 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 0:10 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
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 [this message]
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=20040708110337.N21634@forte.austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=moilanen@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
all inboxes | Powered by JetHome®