From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matt <jackdachef@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
"R. Herbst" <ruediger.herbst@googlemail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Sun GEM PPC32 Bug?
Date: Sat, 05 Feb 2011 07:51:07 +1100 [thread overview]
Message-ID: <1296852667.2349.804.camel@pasglop> (raw)
In-Reply-To: <AANLkTimBFBKJf0-TNRLr2hHNEehR2cnKPvx06=yyHGVj@mail.gmail.com>
On Fri, 2011-02-04 at 16:55 +0000, Matt wrote:
> Hi guys,
>
> I myself don't have any PPC32 box but I just googled some of the
> keywords Ruediger posted "gem eth0: RX MAC fifooverflow smac"
>
> and there were even similar or related messages going back to 2004
> (and kernel 2.6.9).
>
> Slab corruption seems to be involved (in some ?) cases (e.g.
> http://www.mail-archive.com/netdev@vger.kernel.org/msg08345.html)
>
> so it sounds serious to me (from an users point of view).
>
> A kind of temporary fix seems to rmmod and modprobe the kernel-module,
> according to:http://ubuntuforums.org/showthread.php?t=1428330
>
>
> For the German speaking folks there's a thread over at
> forums.gentoo.org (http://forums.gentoo.org/viewtopic-t-862767.html)
>
> and 2 additional English threads which might provide additional info
> on this (and another sound) issue:
>
> http://forums.gentoo.org/viewtopic-t-862229.html "kernel: eth0: RX MAC
> fifo overflow smac"
>
> http://forums.gentoo.org/viewtopic-t-862579.html "Soundissue extreme quietly"
>
> I'm not subscribed to the list so please CC
So the slab corruption doesn't seem to have ever been reported since
2.6.16, do we know if that's still a problem ?
The FIFO overflow could be a driver bug or a HW issue, there are some
known issues with the small FIFOs in that chip, but it's also possible
that we don't configure them quite right. Anybody wants to dig in and
see what's going on there ? May want to look at the Darwin sungem driver
for reference on how it configures them... However, it should generally
recover when that happens. If not, then we have a bug there.
Cheers,
Ben.
next prev parent reply other threads:[~2011-02-04 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 16:55 Sun GEM PPC32 Bug? Matt
2011-02-04 20:51 ` Benjamin Herrenschmidt [this message]
2011-02-04 22:55 ` David Miller
2011-02-05 18:35 ` R. Herbst
2011-02-05 23:39 ` Benjamin Herrenschmidt
2011-02-05 23:45 ` Benjamin Herrenschmidt
2011-02-06 0:20 ` Matt
2011-02-05 20:32 ` Matt
2011-02-05 23:20 ` Benjamin Herrenschmidt
2011-02-06 14:22 ` R. Herbst
-- strict thread matches above, loose matches on Subject: below --
2011-02-06 15:01 R. Herbst
2011-02-07 5:34 ` Benjamin Herrenschmidt
2011-02-08 18:28 ` R. Herbst
2011-02-08 19:58 ` Andreas Schwab
2011-02-09 0:18 ` Benjamin Herrenschmidt
2011-02-09 17:37 ` Andreas Schwab
2011-02-03 19:47 R. Herbst
2011-02-04 8:02 ` Geert Uytterhoeven
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=1296852667.2349.804.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=jackdachef@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ruediger.herbst@googlemail.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