public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: VIA Rhine problem in 2.4.9-pre4
Date: Fri, 24 Aug 2001 23:55:41 -0700	[thread overview]
Message-ID: <3B874BED.E641DB96@candelatech.com> (raw)

It seem that my built-in ethernet NIC has either gone bad, or the
2.4.9-pre4 drivers are bad.  It only seems to happen with this one machine,
so it could be hardware.  The symptom is that the NIC looses the ability
to transmit.  It does receive pkts OK (ie it received an ARP request from
my other machine, and answered according to tcpdump, but the pkt was
never put on the wire it seems.

Here is a snippet of the dmesg:

eth0: VIA VT2043 Rhine at 0xe000, 00:50:08:00:35:c6, IRQ 11.
eth0:  MII PHY found at address 1, status 0x782d advertising 05e1 Link 0021

This last time it happened, I noticed this printed to the console:

eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x9 length 0 status 00000600
eth0:  Oversized Ethernet frame c7572090 vs c7572090.


I looked at /proc/net/dev and didn't see too many errors (there were a few, though,
including carrier errors).  I tried replacing the cable but that did not fix
the problem.  The link does come back up after reboot...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>          <Ben_Greear@excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear

             reply	other threads:[~2001-08-25  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-25  6:55 Ben Greear [this message]
2001-08-25 17:30 ` VIA Rhine problem in 2.4.9-pre4 Urban Widmark
2001-08-27  4:41   ` Ben Greear
2001-08-27  7:39     ` Urban Widmark

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=3B874BED.E641DB96@candelatech.com \
    --to=greearb@candelatech.com \
    --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