From: Stephan von Krawczynski <skraw@ithnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Bug Report: 2.4.23-pre9 / SIS chipset / sundance
Date: Fri, 7 Nov 2003 17:48:24 +0100 [thread overview]
Message-ID: <20031107174824.4853e437.skraw@ithnet.com> (raw)
Hello,
I just experienced a problem with a configuration that is known to only work
with ACPI. It consists of:
P-III 1,4 GHz
Mainboard with SIS 630E chipset
Adaptec 29160 Controller
DLINK DFE-580 TX (four port card) (sundance driver)
A slightly different setup is known to work with 2.4.19 and ACPI patch. Problem
with this SIS chipset is interrupt sharing. If you do not use ACPI the box
freezes sometime.
The known-to-work setup is identical besides it contains a tulip-based four
port ethernet card (old DLINK cards).
We stress-tested the working box by NFS-copying data to the local hd over an
ethernet port that shares its interrupt with the aic.
The above failing setup with sundance driver results in network hanging, but no
other negative points. The network hang can be cured by "mii-tool -r <device>"
(restart autonegotiation). After that everything works well, until the next
hang.
During the network hang the shared interrupt (aic + ethernet) still counts up.
Maybe the sundance driver just misses an interrupt and hangs, and restarting
autonegotiation resets some internals.
I can try whatever patch you like, this is no production setup.
Regards,
Stephan
next reply other threads:[~2003-11-07 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 16:48 Stephan von Krawczynski [this message]
2003-11-09 14:29 ` Bug Report: 2.4.23-pre9 / SIS chipset / sundance Stephan von Krawczynski
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=20031107174824.4853e437.skraw@ithnet.com \
--to=skraw@ithnet.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