From: "acrux@cruxppc.org" <acrux@linuxmail.org>
To: linuxppc-dev@ozlabs.org
Subject: Re: "event-scan failed" logflood
Date: Fri, 11 Jun 2010 06:32:38 -0700 (PDT) [thread overview]
Message-ID: <28855222.post@talk.nabble.com> (raw)
In-Reply-To: <1274233162.29980.13.camel@concordia>
Michael Ellerman wrote:
>
> On Tue, 2010-05-18 at 16:30 +0000, nello martuscielli wrote:
>> Michael Ellerman <michael <at> ellerman.id.au> writes:
>>
>> _omissis__
>> > >
>> > > 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);
>> >
>>
>>
>> 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.
prev parent reply other threads:[~2010-06-11 13:54 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
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 [this message]
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=28855222.post@talk.nabble.com \
--to=acrux@linuxmail.org \
--cc=linuxppc-dev@ozlabs.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).