From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: michael@ellerman.id.au
Cc: pacman@kosh.dhis.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: "event-scan failed" logflood
Date: Thu, 13 May 2010 20:46:47 +1000 [thread overview]
Message-ID: <1273747607.21352.185.camel@pasglop> (raw)
In-Reply-To: <1273730685.25436.66.camel@concordia>
On Thu, 2010-05-13 at 16:04 +1000, Michael Ellerman wrote:
> It's probably caused by 3d541c4b7f6efd55a98189afd1b2f1c9d048c1b3.
>
> Is Pegasos a chrp, I can't remember. It did get called in the old chrp
> code, and the comments suggest you have to call it.
>
> It's not obvious looking at the diff why it would be failing now but
> didn't previously.
Well, first it should be called once per second, not 60 times per
second, so something is wrong there...
Then, it wouldn't surprise me if the Pegasos RTAS didn't implement
the event scan properly. Maybe we failed silently before that ? I
doubt it's necessary there anyways.
It would be relatively easy to avoid starting the event scan on a
pegasos, I think we have a _chrp_type variable that can be tested
for that.
Cheers,
Ben.
next prev parent reply other threads:[~2010-05-13 10:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 4:13 "event-scan failed" logflood pacman
2010-05-13 6:04 ` Michael Ellerman
2010-05-13 10:46 ` Benjamin Herrenschmidt [this message]
2010-05-13 11:16 ` pacman
2010-05-13 21:28 ` Benjamin Herrenschmidt
2010-05-17 12:58 ` nello martuscielli
2010-05-18 12:33 ` Michael Ellerman
2010-05-18 16:30 ` nello martuscielli
2010-05-19 1:39 ` Michael Ellerman
2010-06-11 13:32 ` acrux@cruxppc.org
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=1273747607.21352.185.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=pacman@kosh.dhis.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;
as well as URLs for NNTP newsgroup(s).