On Mon, 2010-05-17 at 12:58 +0000, nello martuscielli wrote: > Benjamin Herrenschmidt <benh <at> kernel.crashing.org> writes: > > _omissis__ > > > > Ok, that gives us a good thing to use to not do the scanning then. If > > that's 0 then we assume it's a bogus OF and we disable the scan > > completely. I'll do a patch later today, though feel free to beat me to > > it. > > > > Cheers, > > Ben. > > > > 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 */ + printk(KERN_DEBUG "rtasd: scan rate is 0, not scanning\n"); + 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); cheers
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev