All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert E Brose II <bob@kunk.jriver.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Occasional crash reports
Date: Fri, 17 Aug 2001 20:28:10 -0500 (CDT)	[thread overview]
Message-ID: <20010818012810.26415.qmail@kunk.jriver.com> (raw)


-- forwarded message --
From: mfedyk@matchmail.com (Mike Fedyk)
Subject: Re: Occasional crash reports
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.

Mike
-- 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. It's a bummer because it sure
would be nice to have another PCI slot free. Tulip works well as does
ne2k-pci.

Bmac has given me problems on a rev C imac. I've almost given up on
the iMac because yaboot seems unable to handle booting partition 13 which
is about 30 gigs up into a 45 gig drive. I can only get at it by using
bootx on a 8.6 CD (the iMac os is 9.1).

Bob
--
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

----- End of forwarded message from Robert E Brose II -----

--
Robert E. Brose II    N0QBJ
http://www.jriver.com/~bob/
bob@kunk.jriver.com

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

             reply	other threads:[~2001-08-18  1:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18  1:28 Robert E Brose II [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-18 11:16 Occasional crash reports Iain Sandoe
2001-08-20  2:51 ` 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=20010818012810.26415.qmail@kunk.jriver.com \
    --to=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 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.