From: Michael Ellerman <michael@ellerman.id.au>
To: pacman@kosh.dhis.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: "event-scan failed" logflood
Date: Thu, 13 May 2010 16:04:45 +1000 [thread overview]
Message-ID: <1273730685.25436.66.camel@concordia> (raw)
In-Reply-To: <20100513041329.1972.qmail@kosh.dhis.org>
[-- Attachment #1: Type: text/plain, Size: 995 bytes --]
On Wed, 2010-05-12 at 23:13 -0500, pacman@kosh.dhis.org wrote:
> I upgraded the kernel on my Pegasos from 2.6.32 to 2.6.33 and now it sends
> the message "event-scan failed" to the kernel log about 60 times per second
> as long as it's running.
>
> The message comes from arch/powerpc/kernel/rtasd.c but I don't know what's
> going on in there so I can't say much more about it.
>
> How may I help find the cause of this problem?
>
> (Or alternatively: what is the correct way to disable this "event-scan"? I
> suspect it's not really necessary since it didn't exist in the previous
> kernel version, and the system is running perfectly aside from the error
> message flood.)
>
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.
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-13 6:04 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 [this message]
2010-05-13 10:46 ` Benjamin Herrenschmidt
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=1273730685.25436.66.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--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).