Strange syslog messages using sundance (DLINK DL10050 _ DFE-580TX)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


(追記) (追記ここまで)



Hi,
Since I upgraded to 2.6.33.1 I experience the following messages in syslog:
Apr 17 18:10:15 gw kernel: eth2: Transmit timed out, TxStatus 00 TxFrameId 00, resetting... Apr 17 18:10:15 gw kernel: 00 bf813000 bf813010 00018001(00) 2072c800 8000008e Apr 17 18:10:15 gw kernel: 01 bf813010 bf813020 00018005(01) 20946800 8000008e Apr 17 18:10:15 gw kernel: 02 bf813020 bf813030 00018009(02) 20aee000 8000008e Apr 17 18:10:15 gw kernel: 03 bf813030 bf813040 0001800d(03) 20d1b000 8000008e Apr 17 18:10:15 gw kernel: 04 bf813040 bf813050 00018011(04) 20e84000 8000008e Apr 17 18:10:15 gw kernel: 05 bf813050 bf813060 00018015(05) 210b6000 8000008e Apr 17 18:10:15 gw kernel: 06 bf813060 bf813070 00018019(06) 212d0000 8000008e Apr 17 18:10:15 gw kernel: 07 bf813070 bf813080 0001801d(07) 216b4800 8000008e Apr 17 18:10:15 gw kernel: 08 bf813080 bf813090 00018021(08) 217ea000 8000008e Apr 17 18:10:15 gw kernel: 09 bf813090 bf8130a0 00018025(09) 21b27800 8000008e Apr 17 18:10:15 gw kernel: 0a bf8130a0 bf8130b0 00018029(0a) 21da5000 8000008e Apr 17 18:10:15 gw kernel: 0b bf8130b0 bf8130c0 0001802d(0b) 220ee000 8000008e Apr 17 18:10:15 gw kernel: 0c bf8130c0 bf8130d0 00018031(0c) 22232000 8000008e Apr 17 18:10:15 gw kernel: 0d bf8130d0 bf8130e0 00008035(0d) 2237b000 8000008e Apr 17 18:10:15 gw kernel: 0e bf8130e0 bf8130f0 00008039(0e) 22575800 8000008e Apr 17 18:10:15 gw kernel: 0f bf8130f0 bf813100 0000803d(0f) 2291a000 8000008e Apr 17 18:10:15 gw kernel: 10 bf813100 bf813110 00008041(10) 22a71000 8000008e Apr 17 18:10:15 gw kernel: 11 bf813110 bf813120 00008045(11) 22beb000 8000008e Apr 17 18:10:15 gw kernel: 12 bf813120 bf813130 00008049(12) 22d4f800 8000008e Apr 17 18:10:15 gw kernel: 13 bf813130 bf813140 0000804d(13) 22f62000 8000008e Apr 17 18:10:15 gw kernel: 14 bf813140 bf813150 00008051(14) 23253000 8000008e Apr 17 18:10:15 gw kernel: 15 bf813150 bf813160 00008055(15) 23473800 8000008e Apr 17 18:10:15 gw kernel: 16 bf813160 bf813170 00008059(16) 2367d800 8000008e Apr 17 18:10:15 gw kernel: 17 bf813170 bf813180 0000805d(17) 23a29800 8000008e Apr 17 18:10:15 gw kernel: 18 bf813180 bf813190 00008061(18) 23ca3800 8000008e Apr 17 18:10:15 gw kernel: 19 bf813190 bf8131a0 00008065(19) 23ee1800 8000008e Apr 17 18:10:15 gw kernel: 1a bf8131a0 bf8131b0 00008069(1a) 20167000 8000008e Apr 17 18:10:15 gw kernel: 1b bf8131b0 bf8131c0 0000806d(1b) 20414800 8000008e Apr 17 18:10:15 gw kernel: 1c bf8131c0 bf8131d0 00008071(1c) 2085f000 8000008e Apr 17 18:10:15 gw kernel: 1d bf8131d0 00000000 00008075(1d) 20caa000 8000008e Apr 17 18:10:15 gw kernel: 1e bf8131e0 00000000 00008079(1e) 20207000 8000008e Apr 17 18:10:15 gw kernel: 1f bf8131f0 00000000 0000007d(1f) 20e6b800 800005ea
Apr 17 18:10:15 gw kernel: TxListPtr=bf8130d0 netif_queue_stopped=1
Apr 17 18:10:15 gw kernel: cur_tx=30(1e) dirty_tx=0(00)
Apr 17 18:10:15 gw kernel: cur_rx=29 dirty_rx=29
Apr 17 18:10:15 gw kernel: cur_task=30
After getting the first one, no more packets are passing through eth2.
eth2 is directly hooked to a linksys wireless access point running dd wrt.
gw:~# ethtool eth2
Settings for eth2:
 Supported ports: [ TP MII ]
 Supported link modes: 10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 Supports auto-negotiation: Yes
 Advertised link modes: 10baseT/Half 10baseT/Full
 100baseT/Half 100baseT/Full
 Advertised auto-negotiation: Yes
 Speed: 100Mb/s
 Duplex: Full
 Port: MII
 PHYAD: 1
 Transceiver: internal
 Auto-negotiation: on
 Current message level: 0x00000001 (1)
 Link detected: yes
gw:~# mii-tool eth2
eth2: negotiated 100baseTx-FD flow-control, link ok
gw:~# mii-diag eth2
Basic registers of MII PHY #1: 3100 782d 0243 0c40 05e1 45e1 0001 0000.
 The autonegotiated capability is 01e0.
The autonegotiated media type is 100baseTx-FD.
 Basic mode control register 0x3100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
Your link partner advertised 45e1: Flow-control 100baseTx-FD 100baseTx 10baseT-FD 10baseT, w/ 802.3X flow control.
 End of basic transceiver information.
gw:~# alta-diag
alta-diag.c:v2.04 2/28/2005 Donald Becker (becker@xxxxxxxxx)
 http://www.scyld.com/diag/index.html
Index #1: Found a Sundance Technology Alta adapter at 0xc800.
 Station address 00:0d:88:68:4c:e4.
 Receive mode is 0x15: Normal unicast and hashed multicast.
 MAC mode is 0120: full duplex NON-ETHERNET-STANDARD FEATURES SET.
 Tx status 00, threshold 8188.
 Interrupt status is 0000: No interrupts pending.
Index #2: Found a Sundance Technology Alta adapter at 0xc880.
 Station address 00:0d:88:68:4c:e5.
 Receive mode is 0x15: Normal unicast and hashed multicast.
 MAC mode is 0120: full duplex NON-ETHERNET-STANDARD FEATURES SET.
 Tx status 00, threshold 8188.
 Interrupt status is 0000: No interrupts pending.
Index #3: Found a Sundance Technology Alta adapter at 0xcc00.
 Station address 00:0d:88:68:4c:e6.
 Receive mode is 0x15: Normal unicast and hashed multicast.
 MAC mode is 0120: full duplex NON-ETHERNET-STANDARD FEATURES SET.
 Tx status 00, threshold 8188.
 Interrupt status is 0000: No interrupts pending.
Index #4: Found a Sundance Technology Alta adapter at 0xcc80.
 Station address 00:0d:88:68:4c:e7.
 Receive mode is 0x15: Normal unicast and hashed multicast.
 MAC mode is 0000: half duplex.
 Tx status 00, threshold 8188.
 Interrupt status is 0000: No interrupts pending.
Should anyone have a clue, please don't hesitate.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html

[Index of Archives] [Netdev] [Ethernet Bridging] [Linux 802.1Q VLAN] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Git] [Bugtraq] [Yosemite News and Information] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux PCI] [Linux Admin] [Samba]

(追記) (追記ここまで)
Powered by Linux

AltStyle によって変換されたページ (->オリジナル) /