From: Andrew Morton <akpm@zip.com.au>
To: Hilbert Barelds <hilbert@hjb-design.com>
Cc: Zwane Mwaikambo <zwane@linux.realnet.co.sz>,
linux-kernel@vger.kernel.org
Subject: Re: kernel 2.4.19-pre8 reboots instead of halt and 3com messages
Date: Thu, 23 May 2002 11:47:48 -0700 [thread overview]
Message-ID: <3CED3954.44998141@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0205231345400.23578-100000@netfinity.realnet.co.sz> <1022170254.1806.0.camel@calvin.hjblocal.nl>
Hilbert Barelds wrote:
>
> On Thu, 2002-05-23 at 13:48, Zwane Mwaikambo wrote:
> > On Thu, 23 May 2002 hilbert@hjb-design.com wrote:
> >
> > > PS The 3com card complains about a "transpoder" x times.
> >
> > Can you get the exact error message? Is the driver modular?
>
> The exact error message is:
> PCI: Found IRQ 12 for device 00:0a.0
> 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
> 00:0a.0: 3Com PCI 3c900 Boomerang 10Mbps Combo at 0xdc00. Vers LK1.1.17
> phy=0, phyx=24, mii_status=0xffff
> phy=1, phyx=0, mii_status=0xffff
That's just a rampant printk - no real problem. The
3c59x update was, err, somewhat unexpected. I've actually
asked Marcelo to back out to the 2.4.18 version because
there has been one report of a transceiver selection failure
with the 2.4.19-pre8 driver.
The thing's totally fragile, I'm afraid. It supports 32 different
devices, of which I have five. If you change anything, you break
something, and for some types of cards it takes months before
you hear about the breakage.
-
next prev parent reply other threads:[~2002-05-23 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-23 11:55 kernel 2.4.19-pre8 reboots instead of halt and 3com messages hilbert
2002-05-23 11:48 ` Zwane Mwaikambo
2002-05-23 16:10 ` Hilbert Barelds
2002-05-23 18:47 ` Andrew Morton [this message]
2002-05-24 15:19 ` Alan Cox
2002-05-24 22:06 ` Hilbert Barelds
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=3CED3954.44998141@zip.com.au \
--to=akpm@zip.com.au \
--cc=hilbert@hjb-design.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linux.realnet.co.sz \
/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).