From: Adam Kropelin <akropel1@rochester.rr.com>
To: Piotr Kaczuba <pepe@attika.ath.cx>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: tulip driver: errors instead TX packets?
Date: Sun, 11 Jan 2004 12:27:36 -0500 [thread overview]
Message-ID: <20040111122736.A16869@mail.kroptech.com> (raw)
In-Reply-To: <40013E83.6070108@attika.ath.cx>; from pepe@attika.ath.cx on Sun, Jan 11, 2004 at 01:16:03PM +0100
On Sun, Jan 11, 2004 at 01:16:03PM +0100, Piotr Kaczuba wrote:
>
> Here is the output of dmesg after setting TULIP_DEBUG to 4 and starting
> pppd (eth0 is used by PPPoE). I agree that the code looks okay but
<snip>
> eth0: Transmit error, Tx status 1a078c80.
That would be heartbeat failure, no carrier, and loss of carrier. It's
interesting that you seem to be able to get valid packets on the wire
because the latter two errors are usually quite fatal. I suspect either
the Comet is just buggy and those error bits aren't to be trusted or
there is something wrong with the PHY config. I don't have docs on the
Comet PHY so there's not much I can do.
On whim, does the patch below change anything for you?
--Adam
--- linux-2.6.1/drivers/net/tulip/tulip_core.c.orig Sun Jan 11 12:06:34 2004
+++ linux-2.6.1/drivers/net/tulip/tulip_core.c Sun Jan 11 12:09:13 2004
@@ -438,7 +438,7 @@
/* Enable automatic Tx underrun recovery. */
outl(inl(ioaddr + 0x88) | 1, ioaddr + 0x88);
dev->if_port = tp->mii_cnt ? 11 : 0;
- tp->csr6 = 0x00040000;
+ tp->csr6 = 0x000C0000;
} else if (tp->chip_id == AX88140) {
tp->csr6 = tp->mii_cnt ? 0x00040100 : 0x00000100;
} else
next prev parent reply other threads:[~2004-01-11 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 14:48 tulip driver: errors instead TX packets? Piotr Kaczuba
2004-01-10 17:27 ` Jeff Garzik
2004-01-10 20:28 ` Piotr Kaczuba
2004-01-11 3:20 ` Adam Kropelin
2004-01-11 12:16 ` Piotr Kaczuba
2004-01-11 17:27 ` Adam Kropelin [this message]
2004-01-12 22:10 ` Piotr Kaczuba
2004-01-13 5:09 ` Adam Kropelin
2004-01-14 20:47 ` Piotr Kaczuba
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=20040111122736.A16869@mail.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pepe@attika.ath.cx \
/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).