From: Jonathan Morton <chromi@cyberspace.org>
To: linux-kernel@vger.kernel.org
Subject: Re: d-link dfe-530 tx (bug-report)
Date: Sun, 4 Feb 2001 10:23:34 +0000 [thread overview]
Message-ID: <l03130328b6a2de0ec77b@[192.168.239.105]> (raw)
>/var/log/messages on the linux-server with the d-link dfe-530 tx:
>[THIS IS THE ERROR-MESSAGE!]
>Feb 1 17:25:56 Nethost kernel: NETDEV WATCHDOG: eth0: transmit timed out
>Feb 1 17:25:56 Nethost kernel: eth0: Transmit timed out, status 0000,
>PHY status 782d, resetting...
>
>after booting everthing is fine (..until the big smb-transfer):
>/var/log/messages (good):
>
>via-rhine.c:v1.08b-LK1.1.6 8/9/2000 Written by Donald Becker
> http://www.scyld.com/network/via-rhine.html
>PCI: Assigned IRQ 9 for device 00:0a.0
>PCI: Setting latency timer of device 00:0a.0 to 64
>eth0: VIA VT6102 Rhine-II at 0xe000, 00:50:ba:68:59:9c, IRQ 9.
>eth0: MII PHY found at address 8, status 0x7829 advertising 01e1 Link 0081.
This sounds every much like it's related to the problems we're having with
the card not initialising on reboot from Windows.
What's the bets we're looking at a new revision of the chip which VIA
haven't (publically) released documentation for yet? I'd say they're
pretty high...
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: chromi@cyberspace.org (not for attachments)
big-mail: chromatix@penguinpowered.com
uni-mail: j.d.morton@lancaster.ac.uk
The key to knowledge is not to rely on people to teach you it.
Get VNC Server for Macintosh from http://www.chromatix.uklinux.net/vnc/
-----BEGIN GEEK CODE BLOCK-----
Version 3.12
GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r- y+
-----END GEEK CODE BLOCK-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2001-02-04 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 10:23 Jonathan Morton [this message]
2001-02-04 11:40 ` hjb
2001-02-04 12:14 ` Urban Widmark
2001-02-04 12:35 ` Manfred Spraul
2001-02-04 12:40 ` Urban Widmark
2001-02-04 15:39 ` Manfred
[not found] ` <Pine.LNX.4.30.0102042130100.26061-300000@cola.teststation.com>
2001-02-05 0:07 ` Thomas Stewart
2001-02-05 8:38 ` Manfred Spraul
2001-02-05 9:26 ` Urban Widmark
2001-02-05 10:41 ` Thomas Stewart
2001-02-05 10:58 ` Manfred Spraul
2001-02-05 19:41 ` Thomas Stewart
-- strict thread matches above, loose matches on Subject: below --
2001-02-05 14:51 ksa1
2001-02-06 21:15 ` Jonathan Morton
2001-02-04 9:26 ksa1
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='l03130328b6a2de0ec77b@[192.168.239.105]' \
--to=chromi@cyberspace.org \
--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®