[Prism54-devel] [Bug 5] New: Second card does not initialize

bugzilla-daemon@mcgrof.com bugzilla-daemon@mcgrof.com
Fri, 14 Nov 2003 18:59:31 +0000 (UTC)


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

           Summary: Second card does not initialize
           Product: prim54
           Version: 1.0.2.2
          Platform: ia32
        OS/Version: Linux 2.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Device Driver
        AssignedTo: prism54-devel@prism54.org
        ReportedBy: feyd@seznam.cz


I have two SMC 2802W. The second seems to be not initialized completely after
loading the module.

dmesg:
Loaded prism54 driver, version 1.0.2.2
PCI: Enabling device 0000:00:0a.0 (0000 -> 0002)
eth1: resetting device...
eth1: uploading firmware...
eth1: firmware uploaded done, now triggering reset...
PCI: Enabling device 0000:00:0c.0 (0000 -> 0002)
eth2: resetting device...
eth2: uploading firmware...
eth1: prism54_mib_init()
eth1: done with prism54_mib_init()!
eth2: firmware uploaded done, now triggering reset...
eth2: prism54_mib_init()
islpci_mgt_response(): queue empty, retrying (jiffies left = 900
islpci_mgt_response(): queue empty, retrying (jiffies left = 800
islpci_mgt_response(): queue empty, retrying (jiffies left = 700
islpci_mgt_response(): queue empty, retrying (jiffies left = 600
islpci_mgt_response(): queue empty, retrying (jiffies left = 500
islpci_mgt_response(): queue empty, retrying (jiffies left = 400
islpci_mgt_response(): queue empty, retrying (jiffies left = 300
islpci_mgt_response(): queue empty, retrying (jiffies left = 200
islpci_mgt_response(): queue empty, retrying (jiffies left = 100
islpci_mgt_response(): queue empty, retrying (jiffies left = 0

ip l:
32: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:04:e2:80:9c:8e brd ff:ff:ff:ff:ff:ff
33: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

iwconfig hangs on eth2



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