From: "R. Herbst" <ruediger.herbst@googlemail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Sun GEM PPC32 Bug?
Date: Sat, 05 Feb 2011 19:35:46 +0100 [thread overview]
Message-ID: <4D4D9882.107@googlemail.com> (raw)
In-Reply-To: <20110204.145508.59670453.davem@davemloft.net>
Am 04.02.2011 23:55, schrieb David Miller:
>
> I think we're simply not resetting enough when the RX FIFO overflow
> happens.
>
> Just for fun I checked the OpenBSD GEM driver to see what they do.
> When an overflow occurs, they bump the statistic, record the current
> read and write fifo pointer registers, and schedule a watchdog timer
> for 400ms into the future.
>
> If the watchdog timer sees that the RX FIFO overflow bit is still set
> in the RX status register, and the RX FIFO read and write pointers
> have not changed, it resets the entire chip.
>
> We unconditionally reset the RX MAC when an overflow occurs, that may
> simply not be enough to unwedge this thing.
>
Is there a special Kernel parameter (sysctl.conf), that makes it
possible to use the Network. So how it is now I can´t work with it. What
can I do at the moment?
next prev parent reply other threads:[~2011-02-05 18:35 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
2011-02-04 22:55 ` David Miller
2011-02-05 18:35 ` R. Herbst [this message]
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=4D4D9882.107@googlemail.com \
--to=ruediger.herbst@googlemail.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.