Thread (10 messages) 10 messages, 5 authors, 2010-06-11

Re: "event-scan failed" logflood

From: Michael Ellerman <hidden>
Date: 2010-05-13 06:04:45

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

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help