From: "Deian Chepishev" <deian@blue-edge.bg>
To: <andrewm@uow.edu.au>
Cc: <netdev@oss.sgi.com>, <linux-kernel@vger.kernel.org>
Subject: 3Com PCI 3c905C Tornado problems (no network sometimes)
Date: Mon, 30 Dec 2002 13:53:23 +0200 [thread overview]
Message-ID: <002d01c2affa$0e76d9b0$0b00050a@deian> (raw)
[-- Attachment #1: Type: text/plain, Size: 2436 bytes --]
Hi all,
for about a year and a half i have problems with network cards 3Com PCI
3c905C Tornado
here is the description of the problem:
I have the following hardware:
MB EliteGroup P6ISAII with chipset Intel815
LAN CARD 3Com PCI 3c905C Tornado
CPU Intel PIII 733 and 933
Sound Embeded
Video Intel815 Embeded
Log entries while loading driver 3c90x are:
Dec 19 16:03:35 oboroten kernel: 3c59x: Donald Becker and others.
www.scyld.com/network/vortex.html
Dec 19 16:03:35 oboroten kernel: 01:03.0: at 0xc000. Vers LK1.1.18-ac
The tower is ATX. when i shut down the computer from the button and after
start it the led which shows that nic is connected to 100Mb mode (I have
leds for 10Mb, 100Mb,ACT) start blinking each second the same do and the led
on the switch (the switch is 3COM office connect DualSpeedSwitch 16).
and when linux boots i have no network at all. I have attached logs for
notworking and working situation.
In order to fix the problem i must unplug the power cord(there is no other
way to copletely stop powering the computer) wait a few seconds plug it
again and start the computer from the button and check to see if the led is
blinking if yes reapeat this action as much times as is necessary for the
led to stop blinking. The interesting part is that if the NIC is blinking
and i load windows the things are working just fine i think that windows
driver has some initialisation (the led stops blinking) which the linux
driver does not have but these are just suppositions.
Notice that i have some lines in the messages log "working situation" which
looks like this:
Dec 30 12:52:01 oboroten kernel: eth0: vortex_error(), status=0xe081
this appears when i execute the following command:
ping -f some.host
i have running 4 machines with the same HW configuration and the problem is
reproducable on all of them. I have noticed this problem since kernel 2.4.2
and it is here by now.
on the machine that i use for testing these things i have kernel:
Linux xxxx.xxxxx.xxxxx 2.4.18-19.8.0 #1 Thu Dec 12 05:39:29 EST 2002 i686
i686 i386 GNU/Linux
but I have and machines with 2.4.19 which has the same problem.
I have this problem often when we have power failure and my boss is not very
happy the servers to be down when i am not in the office after power
failure.
I have executed and the diagnostic programs mii-diag and vortex-diag their
logs are attached to the mail too.
Best Regards,
Deian Chepishev
[-- Attachment #2: messages-not-working.zip --]
[-- Type: application/octet-stream, Size: 6466 bytes --]
[-- Attachment #3: messages--working.zip --]
[-- Type: application/octet-stream, Size: 19091 bytes --]
[-- Attachment #4: vortex-diag-working --]
[-- Type: application/octet-stream, Size: 3117 bytes --]
vortex-diag.c:v2.13a 12/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xc000.
Station address 00:01:02:f6:e4:7d.
Receive mode is 0x07: Normal unicast and all multicast.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 4, registers values by window:
Window 0: 0000 0000 d93f 0000 e3e3 00bf ffff 0000.
Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000.
Window 2: 0100 f602 7de4 0000 0000 0000 0052 4000.
Window 3: 0000 0180 05ea 0020 000a 0800 0800 6000.
Window 4: 0000 0000 0000 0cfa 0001 8880 0000 8000.
Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
Window 6: 0000 0000 0000 0300 0000 00b4 0000 c000.
Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xc000
0xC010: **FIFO** 00000000 0000000a *STATUS*
0xC020: 00000020 00000000 00080000 00000004
0xC030: 00000000 919f6e61 0f005060 00080004
0xC040: 00a81984 00000000 000000b7 00000000
0xC050: 00000000 00000000 00000000 00000000
0xC060: 00000000 00000000 00000000 00000000
0xC070: 00009000 00000000 00400020 00000000
DMA control register is 00000020.
Tx list starts at 00000000.
Tx FIFO thresholds: min. burst 256 bytes, priority with 128 bytes to empty.
Rx FIFO thresholds: min. burst 256 bytes, priority with 128 bytes to full.
Poll period Tx 00 ns., Rx 0 ns.
Maximum burst recorded Tx 32, Rx 64.
Indication enable is 06c6, interrupt enable is 06ce.
No interrupt sources are pending.
Transceiver/media interfaces available: 100baseTx 10baseT.
Transceiver type in use: Autonegotiate.
MAC settings: full-duplex.
Station address set to 00:01:02:f6:e4:7d.
Configuration options 0052.
Setting the EEPROM BIOS ROM field to 0800, new checksum 6f.
Would write new 19 entry 0xff80 (old value 0x0180).
Would write new 32 entry 0x006f (old value 0x0097).
EEPROM format 64x16, configuration table at offset 0:
00: 0001 02f6 e47d 9200 017a 0048 5245 6d50
0x08: 2940 0800 0001 02f6 e47d 0010 0000 00aa
0x10: 72a2 0000 0000 0180 0000 0000 0429 10b7
0x18: 1000 000a 0002 6300 ffb7 b7b7 0000 0000
0x20: 0097 1234 5600 0000 0000 0000 0000 0000
0x28: 0000 0000 0000 0000 0000 0000 0000 0000
0x30: ffff ffff ffff ffff ffff ffff ffff ffff
...
The word-wide EEPROM checksum is 0x7078.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
3Com Node Address 00:01:02:F6:E4:7D (used as a unique ID only).
OEM Station address 00:01:02:F6:E4:7D (used as the ethernet address).
Device ID 9200, Manufacturer ID 6d50.
Manufacture date (MM/DD/YYYY) 11/26/2000, division H, product ER.
A BIOS ROM of size 0Kx8 is expected.
Transceiver selection: Autonegotiate.
Options: negotiated duplex, link beat required.
PCI Subsystem IDs: Vendor 10b7 Device 1000.
100baseTx 10baseT.
Vortex format checksum is incorrect (01 vs. 10b7).
Cyclone format checksum is incorrect (0x91 vs. 0x97).
Hurricane format checksum is incorrect (0xb8 vs. 0x97).
[-- Attachment #5: mii-diag-working --]
[-- Type: application/octet-stream, Size: 879 bytes --]
mii-diag.c:v2.07 11/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Using the new SIOCGMIIPHY value on PHY 24 (BMCR 0x3000).
The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
Basic mode control register 0x3000: Auto-negotiation enabled.
You have link beat, and everything is working OK.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation complete.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
End of basic transceiver information.
MII PHY #24 transceiver registers:
3000 782d 0040 6176 05e1 45e1 0003 0000
0000 0000 0000 0000 0000 0000 0000 0000
1000 0300 0000 0000 0000 0158 0200 0000
003f 8d3e 0f00 ff40 002f 0000 80a0 000b
[-- Attachment #6: vortex-diag-notworking --]
[-- Type: application/octet-stream, Size: 3116 bytes --]
vortex-diag.c:v2.13a 12/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Index #1: Found a 3c905C Tornado 100baseTx adapter at 0xc000.
Station address 00:01:02:f6:e4:7d.
Receive mode is 0x07: Normal unicast and all multicast.
The Vortex chip may be active, so FIFO registers will not be read.
To see all register values use the '-f' flag.
Initial window 4, registers values by window:
Window 0: 0000 0000 d93f 0000 e3e3 00bf ffff 0000.
Window 1: FIFO FIFO 0700 0000 0000 007f 0000 2000.
Window 2: 0100 f602 7de4 0000 0000 0000 0052 4000.
Window 3: 0000 0180 05ea 0020 000a 0800 0800 6000.
Window 4: 0000 0000 0000 0cfa 0001 8080 0000 8000.
Window 5: 1ffc 0000 0000 0600 0807 06ce 06c6 a000.
Window 6: 0000 0000 0000 0000 0000 0000 0000 c000.
Window 7: 0000 0000 0000 0000 0000 0000 0000 e000.
Vortex chip registers at 0xc000
0xC010: **FIFO** 00000000 0000003e *STATUS*
0xC020: 00000020 00000000 00080000 00000004
0xC030: 00000000 6ede9122 0d47a000 00080004
0xC040: 00ddd1c6 00000000 000000b7 00000000
0xC050: 00000000 00000000 00000000 00000000
0xC060: 00000000 00000000 00000000 00000000
0xC070: 00009000 00000000 00000020 00000000
DMA control register is 00000020.
Tx list starts at 00000000.
Tx FIFO thresholds: min. burst 256 bytes, priority with 128 bytes to empty.
Rx FIFO thresholds: min. burst 256 bytes, priority with 128 bytes to full.
Poll period Tx 00 ns., Rx 0 ns.
Maximum burst recorded Tx 32, Rx 0.
Indication enable is 06c6, interrupt enable is 06ce.
No interrupt sources are pending.
Transceiver/media interfaces available: 100baseTx 10baseT.
Transceiver type in use: Autonegotiate.
MAC settings: full-duplex.
Station address set to 00:01:02:f6:e4:7d.
Configuration options 0052.
Setting the EEPROM BIOS ROM field to 0800, new checksum 6f.
Would write new 19 entry 0xff80 (old value 0x0180).
Would write new 32 entry 0x006f (old value 0x0097).
EEPROM format 64x16, configuration table at offset 0:
00: 0001 02f6 e47d 9200 017a 0048 5245 6d50
0x08: 2940 0800 0001 02f6 e47d 0010 0000 00aa
0x10: 72a2 0000 0000 0180 0000 0000 0429 10b7
0x18: 1000 000a 0002 6300 ffb7 b7b7 0000 0000
0x20: 0097 1234 5600 0000 0000 0000 0000 0000
0x28: 0000 0000 0000 0000 0000 0000 0000 0000
0x30: ffff ffff ffff ffff ffff ffff ffff ffff
...
The word-wide EEPROM checksum is 0x7078.
Saved EEPROM settings of a 3Com Vortex/Boomerang:
3Com Node Address 00:01:02:F6:E4:7D (used as a unique ID only).
OEM Station address 00:01:02:F6:E4:7D (used as the ethernet address).
Device ID 9200, Manufacturer ID 6d50.
Manufacture date (MM/DD/YYYY) 11/26/2000, division H, product ER.
A BIOS ROM of size 0Kx8 is expected.
Transceiver selection: Autonegotiate.
Options: negotiated duplex, link beat required.
PCI Subsystem IDs: Vendor 10b7 Device 1000.
100baseTx 10baseT.
Vortex format checksum is incorrect (01 vs. 10b7).
Cyclone format checksum is incorrect (0x91 vs. 0x97).
Hurricane format checksum is incorrect (0xb8 vs. 0x97).
[-- Attachment #7: mii-diag-notworking --]
[-- Type: application/octet-stream, Size: 705 bytes --]
mii-diag.c:v2.07 11/15/2002 Donald Becker (becker@scyld.com)
http://www.scyld.com/diag/index.html
Using the new SIOCGMIIPHY value on PHY 24 (BMCR 0x3000).
Basic mode control register 0x3000: Auto-negotiation enabled.
Basic mode status register 0x7809 ... 7809.
Link status: not established.
This transceiver is capable of 100baseTx-FD 100baseTx 10baseT-FD 10baseT.
Able to perform Auto-negotiation, negotiation not complete.
End of basic transceiver information.
MII PHY #24 transceiver registers:
3000 7809 0040 6176 05e1 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
1000 0021 0000 0009 0000 0000 0600 0000
003c 7d02 0f00 ff40 002c 0000 8020 000b
next reply other threads:[~2002-12-30 11:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 11:53 Deian Chepishev [this message]
2002-12-30 12:59 ` Donald Becker
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='002d01c2affa$0e76d9b0$0b00050a@deian' \
--to=deian@blue-edge.bg \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.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
Powered by JetHome