From: Beezly <beezly@beezly.org.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Sun GEM card looses TX on x86 32bit PCI
Date: 10 Mar 2002 20:36:59 +0000 [thread overview]
Message-ID: <1015792619.1801.4.camel@monkey> (raw)
[-- Attachment #1: Type: text/plain, Size: 910 bytes --]
Hi David,
Unfortunately not. I've just applied these changes and recompiled, but
I'm suffering exactly the same problem.
This is what I have this time when the card has stopped receiving;
monkey:/home/andy# ifconfig
eth0 Link encap:Ethernet HWaddr 00:03:BA:04:5B:D7 =20
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::203:baff:fe04:5bd7/10 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:48508 errors:0 dropped:1 overruns:1 frame:68
TX packets:49362 errors:0 dropped:0 overruns:0 carrier:1
collisions:2 txqueuelen:100=20
RX bytes:61058494 (58.2 MiB) TX bytes:61988220 (59.1 MiB)
Interrupt:5 Base address:0x8400=20
Cheers,
Beezly
On Sun, 2002-03-10 at 08:19, David S. Miller wrote:
>=20
> Let me know if this makes things any better:
>=20
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-03-10 20:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-10 20:36 Beezly [this message]
2002-03-11 0:43 ` Sun GEM card looses TX on x86 32bit PCI David S. Miller
2002-03-11 8:19 ` Beezly
2002-03-11 12:19 ` Beezly
2002-03-11 12:21 ` David S. Miller
2002-03-11 18:35 ` Beezly
2002-03-11 19:02 ` David S. Miller
2002-03-11 21:11 ` Beezly
2002-03-11 21:23 ` Beezly
2002-03-11 22:51 ` Beezly
2002-03-12 17:31 ` David S. Miller
2002-03-12 20:34 ` Beezly
2002-03-12 20:39 ` David S. Miller
2002-03-14 20:43 ` Aaron Sethman
2002-03-14 21:21 ` Aaron Sethman
2002-03-11 1:39 ` David S. Miller
2002-03-11 1:58 ` David S. Miller
2002-03-11 8:29 ` Beezly
2002-03-11 8:42 ` David S. Miller
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=1015792619.1801.4.camel@monkey \
--to=beezly@beezly.org.uk \
--cc=linux-kernel@vger.kernel.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