mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kristof Sardemann <ksardem@linux01.gwdg.de>
To: linux-kernel@vger.kernel.org
Cc: manfred@colorfullife.com, jgarzik@pobox.com, ja6447@albany.edu,
	DONTcwvcaSPAM@hotmail.com
Subject: Re: bug in via-rhine network-driver (transmit timed out) Final Test-results
Date: Wed, 20 Nov 2002 18:13:41 +0100	[thread overview]
Message-ID: <651438577.20021120181341@linux01.gwdg.de> (raw)
In-Reply-To: <3DD76371.4060009@colorfullife.com>

Hi,

thanks for the good help - the card works really good now. =)
In the following I'll answer to all of your suggestions in this one
mail:

>Does booting with "noapic" on the kernel command line fix your problems?
Yes, it did.
(Although I don't understand why cause I have no smp-system ;-))

>Have you tried the 8139too driver?  This driver is suppose to work
>too.
No, it didn't work in my tests.

>Try the linuxfet driver found here:
>http://www.viaarena.com/?PageID=87#ethernet
I took the driver for "Red Hat Linux 7.3 VT8231/VT8233/VT8235/VT6105
Fast Ethernet Controller" (07/23/2002 Ver 0.9) and compiled it on my
SuSE-8.1 - and it worked really good :)

Additional I found out, that booting with "acpi=off" also fixed the
problem - but this might be a specific problem of the
SuSE-8.1-Kernel.

>The hang could be caused by incomplete tx underrun handling, the
>linuxfet driver resets several registers after a tx underrun.
>Could you load the driver with debug=3? For example by adding 'options
>via-rhine debug=3' into your /etc/modules.conf?
To complete the test I'll send the detailed debug-messages tomorrow.

--
Bye.
Kristof <ksardem@linux01.gwdg.de>


  reply	other threads:[~2002-11-20 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-17  9:37 bug in via-rhine network-driver (transmit timed out) Manfred Spraul
2002-11-20 17:13 ` Kristof Sardemann [this message]
2002-11-21 19:07 ` bug in via-rhine network-driver (transmit timed out) debug-report Kristof Sardemann

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=651438577.20021120181341@linux01.gwdg.de \
    --to=ksardem@linux01.gwdg.de \
    --cc=DONTcwvcaSPAM@hotmail.com \
    --cc=ja6447@albany.edu \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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®