From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Robert E Brose II <bob@kunk.jriver.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: Occasional crash reports
Date: Sat, 18 Aug 2001 12:16:58 +0100 [thread overview]
Message-ID: <20010818111705.1E2B2DB9D0@atlas.valhalla.net> (raw)
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) ...
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).
ciao,
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-18 11:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 11:16 Iain Sandoe [this message]
2001-08-18 19:17 ` Mace and Bmac ethernet drivers [was: Occasional crash reports] Mike Fedyk
2001-08-20 2:51 ` Occasional crash reports Robert E Brose II
-- strict thread matches above, loose matches on Subject: below --
2001-08-18 1:28 Robert E Brose II
2001-08-14 16:02 Jiri Masik
2001-08-14 16:28 ` Benjamin Herrenschmidt
2001-08-14 16:45 ` Benjamin Herrenschmidt
2001-08-14 13:03 Iain Sandoe
2001-08-14 9:45 Iain Sandoe
2001-08-14 12:18 ` Takashi Oe
2001-08-13 16:35 Benjamin Herrenschmidt
2001-08-14 2:59 ` Takashi Oe
2001-08-14 18:15 ` Mike Fedyk
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=20010818111705.1E2B2DB9D0@atlas.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bob@kunk.jriver.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).