Michael Ellerman wrote:

On Tue, 2010-05-18 at 16:30 +0000, nello martuscielli wrote:

quoted

Michael Ellerman <michael <at> ellerman.id.au> writes:

_omissis__

quoted

quoted

hi, is there available that patch?
With the fresh new 2.6.34 the logflood problem is still present.

You could try this, completely untested:

diff --git a/arch/powerpc/kernel/rtasd.c b/arch/powerpc/kernel/rtasd.c
index 4190eae..fd68bed 100644
--- a/arch/powerpc/kernel/rtasd.c
+++ b/arch/powerpc/kernel/rtasd.c

@@ -490,6 +490,12 @@ static int __init rtas_init(void)
                return -ENODEV;
        }

+       if (!rtas_event_scan_rate) {
+               /* Broken firmware: take a rate of zero to mean don't

scan */

quoted

+               printk(KERN_DEBUG "rtasd: scan rate is 0, not

scanning\n");

quoted

+               return 0;
+       }
+
        /* Make room for the sequence number */
        rtas_error_log_max = rtas_get_error_log_max();
        rtas_error_log_buffer_max = rtas_error_log_max + sizeof(int);

hi Michael, thanks for pointing me to that patch, now my Pegasos2 G4
seems to
work fine.

Great. Can I add Tested-by you?

hi Michael,
thanks, this patch seems to solve that problem on my Pegasos2 too.


thanks,
Nico

-- 
View this message in context: http://old.nabble.com/Re%3A-%22event-scan-failed%22-logflood-tp28585064p28855222.html
Sent from the linuxppc-dev mailing list archive at Nabble.com.