[Prism54-devel] [Bug 129] New: wpa_supplicant problem: no 'reset complete' IRQ seen - retrying

[bugzilla-daemon at mcgrof.com]

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

           Summary: wpa_supplicant problem: no 'reset complete' IRQ seen -
                    retrying
           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: syzop at vulnscan.org


I get messages like this:
Jul  7 00:24:44 localhost kernel: eth0: no 'reset complete' IRQ seen - retrying
Jul  7 00:24:45 localhost kernel: eth0: no 'reset complete' IRQ seen - retrying
Jul  7 00:24:45 localhost kernel: eth0: interface reset failure
Jul  7 00:24:45 localhost kernel: prism54: Your card/socket may be faulty, or
IRQ line too busy :(
Jul  7 00:24:45 localhost kernel: eth0: resetting device...
Jul  7 00:24:46 localhost kernel: eth0: no 'reset complete' IRQ seen - retrying
[etc]

But I'm only having this problem when trying to use WPA Supplicant, normal WEP
works just fine (for hours, have been using it for like a week, and at full speed).

CARD INFO:
zyxel g-110 
lspci:
0000:04:00.0 Network controller: Intersil Corporation Intersil ISL3890
[Prism GT/Prism Duette] (rev 01)
        Subsystem: Unknown device 187e:3403
        Flags: bus master, medium devsel, latency 80, IRQ 11
        Memory at 10800000 (32-bit, non-prefetchable) [size=8K]
        Capabilities: [dc] Power Management version 1 

Using firmware 1.0.4.3

Tried both kernel 2.4.30 (native) and 2.6.12.1 + latest cvs patch
(patch-2.6-prism54-svn-latest.bz2) from a few hours ago (had to do several
tweaks though, got quite some implicit function declarations).

If there's anyway to give you extra information or to debug it (does kernel
debugging -> on help?), let me know.

Or is this a known problem with prism2 gt chipset + WPA ?



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