[Prism54-devel] [Bug 112] SMC2835W fails with "...your card may be
faulty..." [worksaround needed]
bugzilla-daemon at mcgrof.com
bugzilla-daemon at mcgrof.com
Mon Apr 25 09:49:25 UTC 2005
http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=112
------- Additional Comments From mathiasb at email.dk 2005-04-25 09:49 -------
Sorry for the slow answer, im not checking my mail so often in the weekend.
I have tried the new patch. This is the output (I normally use firmware 1.0.3.0
as my card only seems stable with it, but I have tried with both firmware
1.0.3.0 and 1.0.4.3 as they give different output):
eth1: uploading firmware...
eth1: firmware version: 1.0.3.0
eth1: firmware upload complete
eth1: expecting oid 0x10000002, received 0x19000001.
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response 900, triggering device
eth1: timeout waiting for mgmt response 800, triggering device
eth1: timeout waiting for mgmt response 700, triggering device
eth1: timeout waiting for mgmt response 600, triggering device
eth1: timeout waiting for mgmt response 500, triggering device
eth1: timeout waiting for mgmt response 400, triggering device
eth1: timeout waiting for mgmt response 300, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=10000002 err=-110
eth1: expecting oid 0x12000002, received 0x10000002.
eth1: timeout waiting for mgmt response 999, triggering device
eth1: timeout waiting for mgmt response 899, triggering device
eth1: timeout waiting for mgmt response 799, triggering device
eth1: timeout waiting for mgmt response 699, triggering device
eth1: timeout waiting for mgmt response 599, triggering device
eth1: timeout waiting for mgmt response 499, triggering device
eth1: timeout waiting for mgmt response 399, triggering device
eth1: timeout waiting for mgmt response 299, triggering device
eth1: timeout waiting for mgmt response 199, triggering device
eth1: timeout waiting for mgmt response 99, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=12000002 err=-110
eth1: expecting oid 0x12000007, received 0x12000002.
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response 900, triggering device
eth1: timeout waiting for mgmt response 800, triggering device
eth1: timeout waiting for mgmt response 700, triggering device
eth1: timeout waiting for mgmt response 600, triggering device
eth1: timeout waiting for mgmt response 500, triggering device
eth1: timeout waiting for mgmt response 400, triggering device
eth1: timeout waiting for mgmt response 300, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=12000007 err=-110
eth1: expecting oid 0xff020003, received 0x12000007.
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response 900, triggering device
eth1: timeout waiting for mgmt response 800, triggering device
eth1: timeout waiting for mgmt response 700, triggering device
eth1: timeout waiting for mgmt response 600, triggering device
eth1: timeout waiting for mgmt response 500, triggering device
eth1: timeout waiting for mgmt response 400, triggering device
eth1: timeout waiting for mgmt response 300, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=ff020003 err=-110
eth1: mgt_commit: failure
eth1: interface reset failure
prism54: Your card/socket may be faulty, or IRQ line too busy :(
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware version: 1.0.4.3
eth1: firmware upload complete
eth1: expecting oid 0xff020003, received 0x0.
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response 900, triggering device
eth1: timeout waiting for mgmt response 800, triggering device
eth1: timeout waiting for mgmt response 700, triggering device
eth1: timeout waiting for mgmt response 600, triggering device
eth1: timeout waiting for mgmt response 500, triggering device
eth1: timeout waiting for mgmt response 400, triggering device
eth1: timeout waiting for mgmt response 300, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=ff020003 err=-110
eth1: expecting oid 0x10000002, received 0xff020003.
eth1: timeout waiting for mgmt response 996, triggering device
eth1: timeout waiting for mgmt response 896, triggering device
eth1: timeout waiting for mgmt response 796, triggering device
eth1: timeout waiting for mgmt response 696, triggering device
eth1: timeout waiting for mgmt response 596, triggering device
eth1: timeout waiting for mgmt response 496, triggering device
eth1: timeout waiting for mgmt response 396, triggering device
eth1: timeout waiting for mgmt response 296, triggering device
eth1: timeout waiting for mgmt response 196, triggering device
eth1: timeout waiting for mgmt response 96, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=10000002 err=-110
eth1: expecting oid 0x12000002, received 0xdccc0010.
eth1: timeout waiting for mgmt response 999, triggering device
eth1: timeout waiting for mgmt response 899, triggering device
eth1: timeout waiting for mgmt response 799, triggering device
eth1: timeout waiting for mgmt response 699, triggering device
eth1: timeout waiting for mgmt response 599, triggering device
eth1: timeout waiting for mgmt response 499, triggering device
eth1: timeout waiting for mgmt response 399, triggering device
eth1: timeout waiting for mgmt response 299, triggering device
eth1: timeout waiting for mgmt response 199, triggering device
eth1: timeout waiting for mgmt response 99, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=12000002 err=-110
eth1: expecting oid 0x12000007, received 0x12000002.
eth1: timeout waiting for mgmt response 999, triggering device
eth1: timeout waiting for mgmt response 899, triggering device
eth1: timeout waiting for mgmt response 799, triggering device
eth1: timeout waiting for mgmt response 699, triggering device
eth1: timeout waiting for mgmt response 599, triggering device
eth1: timeout waiting for mgmt response 499, triggering device
eth1: timeout waiting for mgmt response 399, triggering device
eth1: timeout waiting for mgmt response 299, triggering device
eth1: timeout waiting for mgmt response 199, triggering device
eth1: timeout waiting for mgmt response 99, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=12000007 err=-110
eth1: expecting oid 0xff020003, received 0xdccc0010.
eth1: timeout waiting for mgmt response 1000, triggering device
eth1: timeout waiting for mgmt response 900, triggering device
eth1: timeout waiting for mgmt response 800, triggering device
eth1: timeout waiting for mgmt response 700, triggering device
eth1: timeout waiting for mgmt response 600, triggering device
eth1: timeout waiting for mgmt response 500, triggering device
eth1: timeout waiting for mgmt response 400, triggering device
eth1: timeout waiting for mgmt response 300, triggering device
eth1: timeout waiting for mgmt response 200, triggering device
eth1: timeout waiting for mgmt response 100, triggering device
eth1: timeout waiting for mgmt response
eth1: mgt_commit_list: failure. oid=ff020003 err=-110
eth1: mgt_commit: failure
eth1: interface reset failure
prism54: Your card/socket may be faulty, or IRQ line too busy :(
Now, I don't know anything about how drivers work and if this is helpful or not,
but notice how the expected oid and recieved oid is shifted by one. It expects
one oid but it doesn't come until it expects something else (from the firmware
1.0.3.0 output):
eth1: expecting oid 0x10000002, received 0x19000001.
eth1: expecting oid 0x12000002, received 0x10000002.
eth1: expecting oid 0x12000007, received 0x12000002.
eth1: expecting oid 0xff020003, received 0x12000007.
eth1: mgt_commit_list: failure. oid=ff020003 err=-110
Do i have to give you any other output?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the Prism54-devel
mailing list