From: pacman@kosh•dhis.org
To: benh@kernel•crashing.org (Benjamin Herrenschmidt)
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: "event-scan failed" logflood
Date: Thu, 13 May 2010 06:16:03 -0500 (GMT+5) [thread overview]
Message-ID: <20100513111603.3352.qmail@kosh.dhis.org> (raw)
In-Reply-To: <1273747607.21352.185.camel@pasglop>
Benjamin Herrenschmidt writes:
>
> Well, first it should be called once per second, not 60 times per
> second, so something is wrong there...
Actually I think it was happening a lot more than 60 times per second, and
klogd was losing most of the messages because they came too fast. When
running the new kernel, vmstat shows 170000 context switches per second (and
CPU usage never going below 5%) even when everything should be idle.
My next experiment was to hack rtas_init to return 0 unconditionally. Now
everything still runs fine, and the context switches per second are back down
in the 2-digit range.
>
> 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.
If I'm reading things correctly, rtas-event-scan-rate is the key to the
frequency of attempts. And rtasd.c didn't expect this:
$ od -t x1 /proc/device-tree/rtas/rtas-event-scan-rate
0000000 00 00 00 00
0000004
--
Alan Curry
next prev parent reply other threads:[~2010-05-13 11:16 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
2010-05-13 11:16 ` pacman [this message]
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=20100513111603.3352.qmail@kosh.dhis.org \
--to=pacman@kosh$(echo .)dhis.org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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