[Prism54-devel] [Bug 56] New: NETDEV WATCHDOG: eth2: transmit timed out
bugzilla-daemon@mcgrof.com
bugzilla-daemon@mcgrof.com
Fri, 13 Feb 2004 07:46:07 +0000 (UTC)
http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=56
Summary: NETDEV WATCHDOG: eth2: transmit timed out
Product: prim54
Version: 1.0.2.2
Platform: ia32
OS/Version: Linux 2.4
Status: NEW
Severity: critical
Priority: P2
Component: Device Driver
AssignedTo: prism54-devel@prism54.org
ReportedBy: constantin.andrita@expert.ro
00:00.0 Host bridge: Intel Corp. 440BX/ZX - 82443BX/ZX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX - 82443BX/ZX AGP bridge (rev 03)
00:02.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 02)
00:02.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
00:02.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
00:02.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 02)
00:10.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01)
00:12.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01)
00:14.0 Network controller: Harris Semiconductor: Unknown device 3890 (rev 01)
01:01.0 VGA compatible controller: S3 Inc. Trio 64 3D (rev 01)
CPU0
0: 350629 XT-PIC timer
1: 2 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 194009 XT-PIC NE2000
5: 0 XT-PIC usb-uhci
10: 0 XT-PIC eth3
11: 70617 XT-PIC eth2
14: 4201 XT-PIC ide0
15: 124324 XT-PIC eth1
NMI: 0
ERR: 0
eth1 IEEE 802.11b/g ESSID:"XXXXX"
Mode:Master Channel:6 Access Point: 00:60:B3:13:A6:F6
Bit Rate:54Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Link Quality:209 Signal level:0 Noise level:82
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth2 IEEE 802.11b/g ESSID:"YYYYY"
Mode:Master Channel:2 Access Point: 00:60:B3:13:30:F4
Bit Rate:54Mb/s Tx-Power=31 dBm Sensitivity=20/200
Retry min limit:8 RTS thr:2347 B Fragment thr:2346 B
Encryption key:off
Link Quality:92 Signal level:0 Noise level:138
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
eth3 NOT READY! ESSID:off/any
Mode:Managed Channel:6 Access Point: 00:00:00:00:00:00
Tx-Power=31 dBm Sensitivity=0/200
Retry min limit:0 RTS thr=0 B Fragment thr=0 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Every once in a while I get the following errors and the device doesn't show
anymore in iwconfig output as wireless.
if I put down the interface and bring it up again it works.
It doesn't have a pattern of time. Still I think it works longer without the
error if do a hardware reset of the machine hosting these devices.
The devices are miniPCI XG-600 plugged in PCI to miniPCI adapters into an
desktop IBM PC300GL.
I tried even the latest prism54 snapshot and no luck I still have this problem.
Through those interfaces I have at least 500kbps traffic most of the time.
NETDEV WATCHDOG: eth2: transmit timed out
NETDEV WATCHDOG: eth2: transmit timed out
eth2: timeout waiting for mgmt response 100, trigging device
eth2: timeout waiting for mgmt response
NETDEV WATCHDOG: eth2: transmit timed out
NETDEV WATCHDOG: eth2: transmit timed out
eth2: resetting device...
NETDEV WATCHDOG: eth2: transmit timed out
eth2: device soft reset timed out
eth2: islpci_close ()
eth2: islpci_open()
eth2: resetting device...
eth2: uploading firmware...
eth2: firmware uploaded done, now triggering reset...
Issuing iwpriv eth2 reset doesn't do me any good as you can see above, only
going down and up again works or restarting the machine of course.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.