mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Guggenberger  <christian.guggenberger@physik.uni-regensburg.de>
To: linux-kernel@vger.kernel.org
Subject: via-rhine weirdness with via kt8235 Southbridge
Date: Wed, 23 Oct 2002 15:49:31 +0200	[thread overview]
Message-ID: <20021023154931.E14930@pc9391.uni-regensburg.de> (raw)
In-Reply-To: <20021023154824.C14930@pc9391.uni-regensburg.de>; from christian.guggenberger@physik.uni-regensburg.de on Wed, Oct 23, 2002 at 15:48:24 +0200


I like to report some Problems with the NIC integrated in the via kt8235 
chipset.
(Mobo is a Epox 8k5a3+, network is 10 MBit half-duplex)

1.
This concerns both 2.4 and 2.5 kernels  (testet with 2.4.20pre*aa series, and 
with 2.5.43, 2.5.44 and 2.5.44-ac1):

When I enable APIC in the Bios, the via-rhine module will insert properly, but 
I won't get a link... With APIC disabled, link is ok.
Ok, this could be caused by buggy bios, so I'll try again, when a new 
biosversion is available.

2.
This only happens with the 2.5 series (testet with 2.5.43 and above):
When there's much flow on the nic, I get many timeouts ending in dead NIC and 
I've to reboot...

Oct 23 14:56:45 bonnie79 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 23 14:56:45 bonnie79 kernel: eth0: Transmit timed out, status 0000, PHY 
status 786d, resetting...
Oct 23 14:56:49 bonnie79 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 23 14:56:49 bonnie79 kernel: eth0: Transmit timed out, status 0000, PHY 
status 786d, resetting...
Oct 23 14:56:59 bonnie79 kernel: NETDEV WATCHDOG: eth0: transmit timed out
Oct 23 14:56:59 bonnie79 kernel: eth0: Transmit timed out, status 0000, PHY 
status 786d, resetting...

I remember a discussion (Sep. 26th, I think), where such problems had been 
reported for the 2.4.20pre kernels.... which now seem to be fixed in the 
latest 2.4 series.

Christian
  

       reply	other threads:[~2002-10-23 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021023154824.C14930@pc9391.uni-regensburg.de>
2002-10-23 13:49 ` Christian Guggenberger [this message]
2002-10-23 15:34   ` Roger Luethi
     [not found] <20021115002822.G6981@pc9391.uni-regensburg.de>
2002-11-15  0:17 ` Christian Guggenberger
2002-11-15 10:09   ` Erik Hensema
2002-11-15 10:28 Nicolas Mailhot

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=20021023154931.E14930@pc9391.uni-regensburg.de \
    --to=christian.guggenberger@physik.uni-regensburg.de \
    --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

all inboxes | Powered by JetHome®