[Prism54-devel] [Bug 112] New: SMC2835W fails with "...your card may be faulty..." in latest cvs

[bugzilla-daemon at mcgrof.com]

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

           Summary: SMC2835W fails with "...your card may be faulty..." in
                    latest cvs
           Product: prim54
           Version: 1.2
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel at prism54.org
        ReportedBy: mathiasb at email.dk


Hello

With latest CVS my card, which worked before, now comes up with this error:

eth1: resetting device...
eth1: uploading firmware...
eth1: firmware version: 1.0.4.3
eth1: firmware upload complete
eth1: Out of memory, cannot handle oid 0xb8c60000
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 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: errant PIMFOR application frame
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 :(

lspci has this to say about the card (it's a SMC2835W):

$lspci -v
02:00.0 Network controller: Harris Semiconductor D-Links DWL-g650 A1 (rev 01)
        Subsystem: Standard Microsystems Corp [SMC]: Unknown device a835
        Flags: bus master, medium devsel, latency 80, IRQ 5
        Memory at 20800000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [dc] Power Management version 1
$lspci -vn
02:00.0 Class 0280: 1260:3890 (rev 01)
        Subsystem: 10b8:a835
        Flags: bus master, medium devsel, latency 80, IRQ 5
        Memory at 20800000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [dc] Power Management version 1

and /proc/interrupts:
  5:       2045          XT-PIC  yenta, eth1, ohci1394, uhci_hcd


Before this CVS (as of 2004-10-02) the card worked alright, although it was in 
this category:

"Recently I have access to a couple of cards/boxen that have
the same symptons as other people have reported -
Dropped connections, bouncy bitrate, association problems etc." 
-quote Margit on prism54devel

aqtually since Margit wrote that mail i thought i would try out firmware 1.0.3.0
 (had tried earlier but it was a long time ago) and since then i have a pretty
good connection, so i'm guessing that my card is one of those who have problems
with the sleep mode.

But i would like to keep up with this driver so please do something about the
"your card might be faulty"-message :)



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