linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Mace and Bmac ethernet drivers [was: Occasional crash reports]
Date: Sat, 18 Aug 2001 12:17:19 -0700	[thread overview]
Message-ID: <20010818121719.C1579@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20010818111705.1E2B2DB9D0@atlas.valhalla.net>


On Sat, Aug 18, 2001 at 12:16:58PM +0100, Iain Sandoe wrote:
>
> On Sat, Aug 18, 2001, Robert E Brose II wrote:
> > On Mon, Aug 13, 2001 at 09:59:05PM -0500, Takashi Oe wrote:
> >> I don't really know, but I can confirm that both 2.2.x and 2.4.x kernels
> >> are unstable on a beige g3 and a bmac equipped b/w g3.  I can crash them
> >> rather easily with regular programs, given a day or two.  I have not seen
> >> similar instability on other machines (dual g4, 7600, all nubus).
> >> Unfortunately, I don't have any time to track it down right now  :(
> >
> > I've been able to trace that to the mace and bmac ethernet drivers, which
> > are *very* unreliable in 2.2.  Get the latest drivers from Donald Becker for
> > tulip, rtl8139, eepro100, etc. and you're set.  I haven't tried 2.4 yet.
>
> apropos bmac - is there a dbdma problem?
> I think Takashi did a dbdma fix ... did that go in?
>
> > -- end of forwarded message --
> >
> > Mace is still unreliable in 2.4. It's always been just plain unreliable
> > for me on 7200, 7500 and 7600's.
>
>  - are these clones or Apple originals?
> we found other dbdma problems on clone 7x00 machines for PowerComputing (in
> the sound side) ...
>

They were all origional Apple products.  7200, 6500 (which has no built in
ethernet), and beige g3 (oldworld).

> might be worth checking that there are no cases of "DEAD" status coming up
> on the Mace driver...
>
> as I say, booting with the BootX *init* (rather than the application) bmac,
> at least, seems reliable on g3/beige (don't use Mace much).
>

What's your best uptime for the g3?  I have one setup as a ipsec
gateway/firewall, and it didn't last over 28 days.  Add a tulip card (it
already had one for firewall, now has two...) and I now have 70 days uptime.

Also note: Mace has only worked over two days for me in about 20% of my
7200s (I have about 15) and in the case where it was able to reach 14 days
uptime, I was seeing kernel memory corruption, but no oops or crashes, just
owkward behavior.  Same solution, add another ethernet (this one has
eepro100, and tulip) and it now has 90 days uptime.

If anyone wants to try to fix the mace driver, I'd be happy to test any
patches available.

Mike

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-08-18 19:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18 11:16 Occasional crash reports Iain Sandoe
2001-08-18 19:17 ` Mike Fedyk [this message]
2001-08-20  2:51 ` Robert E Brose II
  -- strict thread matches above, loose matches on Subject: below --
2001-08-19  0:26 Mace and Bmac ethernet drivers [was: Occasional crash reports] Iain Sandoe

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=20010818121719.C1579@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=linuxppc-dev@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).