[Prism54-devel] [Bug 67] hard hang on readl

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=67





------- Additional Comments From babel42@t-online.de  2004-03-11 08:48 -------
After Feyd told me that my gigabyte 6bxe mainboard is not a real PCI 2.2
mainboard I swapped the mainboard and now use a MSI KT3V MS-6712 v1.0 mainboard
(http://www.msi-computer.de/produkte/produkt.php?Prod_id=269). After running a
rsync over the wlan link the card dies sometime last night. An iwpriv ethX reset
didn't bring up the card again. This is what happens after an iwpriv ethX reset:

Mar 11 09:38:51 fli4l kernel: eth4: resetting device...
Mar 11 09:38:52 fli4l kernel: eth4: device soft reset timed out
Mar 11 09:38:52 fli4l kernel: eth4: timeout waiting for mgmt response 100,
trigging device
Mar 11 09:38:52 fli4l kernel: NETDEV WATCHDOG: eth4: transmit timed out
Mar 11 09:38:53 fli4l kernel: eth4: timeout waiting for mgmt response
Mar 11 09:38:53 fli4l kernel: eth4: timeout waiting for mgmt response 100,
trigging device
Mar 11 09:38:54 fli4l kernel: eth4: timeout waiting for mgmt response
Mar 11 09:38:54 fli4l kernel: eth4: timeout waiting for mgmt response 100,
trigging device
Mar 11 09:38:54 fli4l kernel: NETDEV WATCHDOG: eth4: transmit timed out
Mar 11 09:38:55 fli4l kernel: eth4: timeout waiting for mgmt response
Mar 11 09:38:55 fli4l kernel: eth4: timeout waiting for mgmt response 100,
trigging device
Mar 11 09:38:56 fli4l kernel: NETDEV WATCHDOG: eth4: transmit timed out
Mar 11 09:38:56 fli4l kernel: eth4: timeout waiting for mgmt response
Mar 11 09:38:56 fli4l kernel: eth4: mgmt tx queue is still full
Mar 11 09:38:56 fli4l last message repeated 14 times
Mar 11 09:38:56 fli4l kernel: eth4: mgt_commit has failed. Restart the device
Mar 11 09:38:56 fli4l kernel: eth4: mgmt tx queue is still full
Mar 11 09:38:58 fli4l kernel: NETDEV WATCHDOG: eth4: transmit timed out
Mar 11 09:39:01 fli4l kernel: NETDEV WATCHDOG: eth4: transmit timed out

Is it possible that the mode the wlan card is configured has something to do
with the problems? I'm not sure but my wlan link partner uses his prism54 card
in master mode and I think he didn't have the problems with ethX timeouts. I'm
using my card in managed mode. The strange thing is: He's using a gigabyte 6bxe
mainboard too.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.