From: David Blythe <blythe@routefree.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: dcache BUG()
Date: Tue, 08 May 2001 11:01:51 -0700 [thread overview]
Message-ID: <3AF8348F.FEBF22DE@routefree.com> (raw)
In-Reply-To: 3AF747C4.9C2D74A5@mvista.com
Dan Malek wrote:
> There may be something else wrong with the Ethernet driver itself.
> When I updated it to the 2.4_devel baseline, there were some weird
> cache management calls that didn't make sense. My updates were to
> use the standard non-coherent cache management functions, and I
> changed the logic to make sense (to me :-). From this quick update,
> I noticed it would be nice to make the transmit more efficient
> and higher performance by handling multiple frames, but it should
> function properly.
There are a large number of bugs in the 405 ethernet driver. We (I)
were waiting until we had resolved this reference count problem, and had
a some workable solution to the starvation under packet floods problem
discussed a few weeks ago with other embedded processors before posting
a patch (i.e., have the driver stand up to reasonable stress tests).
Among the bugs are:
leaks of all the receive buffers, plus other memory on every device
close,
not checking for failed allocations in skb allocations,
poor choice of cache operations when manipulating buffers,
race conditions in data structure access between the rxde and rxeob
interrupt handlers
In either event we had proven to ourselves that this "reference count"
bug happened with other nic cards when used with the 405GP processor, so
we are reasonably certain that it is not specific to the 405 ethernet
driver. As Eli mentioned ping flooding demonstrates the problem too so
we still believe that it is a generic atomic op problem. However, we
can only make it happen on our 405GP walnut board(s) and not our
prototype 405GP board(s) (they both have rev D processors).
Just to refresh everyone's memory, the other reference count problems we
were seeing were "Freeing alive device" messages indicating the dev
reference count had gone to zero, and another one in the skb code when
ping flooding with large packet sizes (causing lots of fragments to be
generated).
david
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-08 18:01 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 19:04 dcache BUG() Eli Chen
2001-05-07 21:04 ` Dan Malek
2001-05-07 21:17 ` Dan Malek
2001-05-07 21:30 ` Tom Rini
2001-05-07 23:03 ` Dan Malek
2001-05-07 21:47 ` Eli Chen
2001-05-07 23:01 ` Dan Malek
2001-05-07 23:06 ` Gabriel Paubert
2001-05-07 23:15 ` Dan Malek
2001-05-07 23:28 ` Gabriel Paubert
2001-05-07 23:35 ` Eli Chen
2001-05-07 23:36 ` Dan Malek
2001-05-08 0:16 ` Eli Chen
2001-05-08 0:41 ` Dan Malek
2001-05-08 1:14 ` Eli Chen
2001-05-08 1:11 ` Dan Malek
2001-05-08 18:01 ` David Blythe [this message]
2001-05-08 20:27 ` Dan Malek
2001-05-08 21:34 ` David Blythe
2001-05-08 21:49 ` Dan Malek
2001-05-08 22:34 ` Ira Weiny
2001-05-08 22:53 ` Dan Malek
2001-05-08 1:37 ` Gabriel Paubert
2001-05-08 1:44 ` Dan Malek
2001-05-07 23:40 ` Gabriel Paubert
-- strict thread matches above, loose matches on Subject: below --
2001-05-12 0:44 Brian Kuschak
2001-05-12 0:57 ` Eli Chen
2001-05-14 9:28 ` Gabriel Paubert
2001-05-10 21:20 Brian Kuschak
2001-05-10 21:26 ` Dan Malek
2001-05-09 16:40 Brian Kuschak
2001-05-09 18:31 ` Dan Malek
2001-05-09 19:18 ` Gabriel Paubert
2001-05-10 18:39 ` Frank Rowand
2001-05-10 18:49 ` Gabriel Paubert
2001-05-10 19:10 ` Frank Rowand
2001-05-11 4:23 ` Paul Mielke
2001-05-11 10:09 ` Gabriel Paubert
2001-05-10 20:56 ` Dan Malek
2001-05-10 23:14 ` Cort Dougan
2001-05-11 11:01 ` Gabriel Paubert
2001-05-11 10:57 ` Gabriel Paubert
2001-05-11 18:49 ` Dan Malek
2001-05-08 17:43 Brian Kuschak
2001-05-09 11:06 ` Gabriel Paubert
2001-05-08 15:43 Brian Kuschak
2001-05-08 3:36 Brian Kuschak
2001-05-08 1:53 Brian Kuschak
2001-05-08 2:03 ` Dan Malek
2001-05-08 11:59 ` Gabriel Paubert
2001-05-08 0:40 Brian Kuschak
2001-05-07 23:01 Brian Kuschak
2001-05-07 22:19 Brian Kuschak
2001-05-07 22:35 ` Cort Dougan
2001-05-07 22:43 ` Eli Chen
2001-05-07 17:21 Brian Kuschak
2001-05-07 20:58 ` Dan Malek
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=3AF8348F.FEBF22DE@routefree.com \
--to=blythe@routefree.com \
--cc=linuxppc-embedded@lists.linuxppc.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).