Michael Ellerman wrote:
>
> On Tue, 2010-05-18 at 16:30 +, nello martuscielli wrote:
>> Michael Ellerman 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 t
On Tue, 2010-05-18 at 16:30 +, nello martuscielli wrote:
> Michael Ellerman 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:
> >
> >
Michael Ellerman 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 41
On Mon, 2010-05-17 at 12:58 +, nello martuscielli wrote:
> Benjamin Herrenschmidt 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
Benjamin Herrenschmidt 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,
On Thu, 2010-05-13 at 06:16 -0500, pac...@kosh.dhis.org wrote:
> Benjamin Herrenschmidt writes:
> >
> > Well, first it should be called once per second, not 60 times per
> > second, so something is wrong there...
>
> Actually I think it was happening a lot more than 60 times per second, and
> klo
Benjamin Herrenschmidt writes:
>
> Well, first it should be called once per second, not 60 times per
> second, so something is wrong there...
Actually I think it was happening a lot more than 60 times per second, and
klogd was losing most of the messages because they came too fast. When
running t
On Thu, 2010-05-13 at 16:04 +1000, Michael Ellerman wrote:
> 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
On Wed, 2010-05-12 at 23:13 -0500, pac...@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.
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 abou
10 matches
Mail list logo
