From: pacman@kosh•dhis.org
To: linuxppc-dev@lists•ozlabs.org
Subject: "event-scan failed" logflood
Date: Wed, 12 May 2010 23:13:29 -0500 (GMT+5) [thread overview]
Message-ID: <20100513041329.1972.qmail@kosh.dhis.org> (raw)
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.)
--
Alan Curry
next reply other threads:[~2010-05-13 4:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-13 4:13 pacman [this message]
2010-05-13 6:04 ` "event-scan failed" logflood Michael Ellerman
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=20100513041329.1972.qmail@kosh.dhis.org \
--to=pacman@kosh$(echo .)dhis.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