From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: roger blofeld <blofeldus@yahoo.com>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Sungem bug or something else?
Date: Thu, 6 Jun 2002 21:45:18 +0200 [thread overview]
Message-ID: <20020606194518.27675@smtp.wanadoo.fr> (raw)
In-Reply-To: <20020606192510.58822.qmail@web11106.mail.yahoo.com>
>I encounter an oops during boot bringing up a sungem
>interface. (smp g4 450/gcc 3.1/glibc 2.2.5) If I defer
>bringing up the network at boot, I can successfully
>start eth0 (sungem) if I start eth1 (tulip) first, so
>it may not be the sungem driver itself. This happens
>on benh 2.4.19-Bpre10, and pre9.
What kind of error is it ? A Machine Check ?
Looking at your backtrace, it looks like the driver is
trying to access the PHY chip. That can sometimes happen
if you have some tool like miitool or ethtool trying to
get at the link status while the chip isn't powered up.
The problem here is that sungem on Apple HW only powers
the chip when the interface is brought up, and powers it
down about 10 seconds after bringing the interface down.
This improve power management, but kills link monitoring
tools.
There may be also a bug in the driver causing it to try
to access the PHY registers when the chip is in down
mode & getting the ethtool ioctl's
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-06 19:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 20:20 Patch: Fix SMP hang on modem close roger blofeld
2002-04-06 10:24 ` Benjamin Herrenschmidt
2002-06-06 19:25 ` Sungem bug or something else? roger blofeld
2002-06-06 19:30 ` Tom Rini
2002-06-06 19:45 ` Benjamin Herrenschmidt [this message]
2002-06-06 20:35 ` roger blofeld
2002-06-06 20:41 ` Kevin B. Hendricks
2002-06-06 20:25 ` benh
2002-06-06 21:02 ` roger blofeld
2002-06-07 0:51 ` roger blofeld
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=20020606194518.27675@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=blofeldus@yahoo.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).