From: Michael Ellerman <michael@ellerman.id.au>
To: nello martuscielli <ppc.addon@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: "event-scan failed" logflood
Date: Wed, 19 May 2010 11:39:22 +1000 [thread overview]
Message-ID: <1274233162.29980.13.camel@concordia> (raw)
In-Reply-To: <loom.20100518T182547-195@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]
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?
> Anyway i got these dumps caused by mv643xx_eth:
>
>
> [...]
> sysfs: cannot create duplicate filename '/class/mdio_bus/0'
> ------------[ cut here ]------------
> Badness at fs/sysfs/dir.c:451
> NIP: c00efc70 LR: c00efc70 CTR: 00000000
> REGS: ef117c70 TRAP: 0700 Not tainted (2.6.34)
> MSR: 00029032 <EE,ME,CE,IR,DR> CR: 22002488 XER: 00000000
> TASK = ef110630[80] 'modprobe' THREAD: ef116000
> GPR00: c00efc70 ef117d20 ef110630 00000042 c0009480 00000000 00134ac8 00000000
> GPR08: 00000000 00000000 22002482 10000002 ffffffff 10023ab8 00000000 00000000
> GPR16: 00000000 107db0b0 00000000 107db088 10005558 00000003 107db324 107db008
> GPR24: 10005558 00000000 0000a9ce fffffffe ef117d48 ef0a4300 efb87000 ffffffef
> NIP [c00efc70] sysfs_add_one+0x88/0xb8
> LR [c00efc70] sysfs_add_one+0x88/0xb8
> Call Trace:
> [ef117d20] [c00efc70] sysfs_add_one+0x88/0xb8 (unreliable)
> [ef117d40] [c00f0d9c] sysfs_do_create_link+0x104/0x1ac
> [ef117d70] [c026b238] device_add+0x1c8/0x534
> [ef117db0] [c02b2e40] mdiobus_register+0xb4/0x1d8
> [ef117de0] [f222c510] mv643xx_eth_shared_probe+0x14c/0x420 [mv643xx_eth]
Can't really help with that, looks like it's trying to register the same
mdio bus twice?
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-05-19 1:39 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 [this message]
2010-06-11 13:32 ` acrux@cruxppc.org
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=1274233162.29980.13.camel@concordia \
--to=michael@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=ppc.addon@gmail.com \
/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).