Skip to contentSkip to conversation

PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter

DISCUSSION Ivo Couckuyt 4 participants 8 messages Feb 20, 2008 – Jun 8, 2008

lore
Share & tools
lore
#0 lore raw

Hi,

I followed the guidelines for a bug report.
If there is anything else needed, I'll be happy to do all the testing needed.

[1.] One line summary of the problem:
p54usb driver crashes on trying to associate with an ap with the CPWUA054 usb adapter

[2.] Full description of the problem/report:
What works:
modprobe p54usb
dmesg (displays my adapter correctly)
ifconfig up wlan0
dmesg (using the right firmware 2.5.6.0)

but trying to associate to my accesspoint (using wpa_supplicant) causes a hard-lock up (keyboard leds blinking). Before locking up it spams loads of 'RX: unknown frame received phy1' messages on kmsg/dmesg.

Note that my adapter isn't in the vendor:model id list of the p54 driver, my patch submitted for that is prob. lost somewhere. But I'm using islsm with my usb adapters for >1.5 years with no problems.
lsusb lists my device's model/vendor id
Bus 001 Device 002: ID 083a:5501 Accton Technology Corp.

I also tried the wireless-2.6 kernel some months again with the same issue, though I had some kernel option on that allowed me to do a traceback to the failed function, *rx*() i believe (in p54 itself). I'm not really familiar with kernel debugging but i'll try to give you the full trace in a couple of days, have to figure out how to do it again.
If there is anything else that is useful, I'll be happy to provide it.

[3.] Keywords (i.e., modules, networking, kernel):
wireless, p54 driver

[4.] Kernel version (from /proc/version):
If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes.

Linux barton 2.6.24-gentoo-r2-BARTON #3 PREEMPT Tue Feb 19 20:31:03 CET 2008 i686 AMD Athlon(tm) XP 2500+ AuthenticAMD GNU/Linux

Gnu C                  4.1.2
Gnu make               3.81
binutils               2.18
util-linux             2.12r
mount                  2.12r
module-init-tools      3.2.2
e2fsprogs              1.40.2
PPP                    2.4.4
Linux C Library        2.6.1
Dynamic linker (ldd)   2.6.1
Procps                 3.2.7
Net-tools              1.60
Kbd                    1.13
Sh-utils               6.9
udev                   115
wireless-tools         29
Modules Loaded         p54usb p54common firmware_class nvidia_agp agpgart forcedeth

[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)

[6.] A small shell script or example program which triggers the
problem (if possible)
/ Specific to hardware

[7.] Environment
/

[7.1.] Software (add the output of the ver_linux script here) If some fields are empty or look unusual you may have an old version. Compare to the current minimal requirements in Documentation/Changes.

Linux barton 2.6.24-gentoo-r2-BARTON #3 PREEMPT Tue Feb 19 20:31:03 CET 2008 i686 AMD Athlon(tm) XP 2500+ AuthenticAMD GNU/Linux

Gnu C                  4.1.2
Gnu make               3.81
binutils               2.18
util-linux             2.12r
mount                  2.12r
module-init-tools      3.2.2
e2fsprogs              1.40.2
PPP                    2.4.4
Linux C Library        2.6.1
Dynamic linker (ldd)   2.6.1
Procps                 3.2.7
Net-tools              1.60
Kbd                    1.13
Sh-utils               6.9
udev                   115
wireless-tools         29
Modules Loaded         p54usb p54common firmware_class nvidia_agp agpgart forcedeth

[7.2.] Processor information (from /proc/cpuinfo):
/

[7.3.] Module information (from /proc/modules):
p54usb 12672 0 - Live 0xf8828000
p54common 11136 1 p54usb, Live 0xf8817000
firmware_class 7424 1 p54usb, Live 0xf8814000
nvidia_agp 6428 1 - Live 0xf8825000
agpgart 27056 1 nvidia_agp, Live 0xf881d000
forcedeth 47372 0 - Live 0xf885e000

[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)

[7.5.] PCI information ('lspci -vvv' as root)
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?) (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Region 0: Memory at e0000000 (32-bit, prefetchable) [size=128M]
Capabilities: [40] AGP version 3.0
Status: RQ=32 Iso- ArqSz=2 Cal=0 SBA+ ITACoh- GART64- HTrans-
64bit- FW+ AGP3+ Rate=x4,x8

       Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x4

Capabilities: [60] HyperTransport: Host or Secondary Interface
Command: WarmRst+ DblEnd-
Link Control: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO- <CRCErr=0 Link Config: MLWI=8bit MLWO=8bit LWI=8bit LWO=8bit Revision ID: 0.16

00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 1 (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
Subsystem: ASUSTeK Computer Inc. Unknown device 80ac
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-

00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Capabilities: [48] HyperTransport: Slave or Primary Interface
Command: BaseUnitID=1 UnitCnt=15 MastHost- DefDir- Link Control 0: CFlE- CST- CFE- <LkFail- Init+ EOC+ TXO- <CRCErr=0 Link Config 0: MLWI=8bit MLWO=8bit LWI=8bit LWO=8bit Link Control 1: CFlE- CST- CFE- <LkFail- Init+ EOC- TXO+ <CRCErr=0 Link Config 1: MLWI=8bit MLWO=8bit LWI=8bit LWO=8bit Revision ID: 0.00

00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
Subsystem: ASUSTeK Computer Inc. Unknown device 0c11
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at c000 [size=32]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.0 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ea004000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.1 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 10 [OHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin B routed to IRQ 5
Region 0: Memory at ea005000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:02.2 USB Controller: nVidia Corporation nForce2 USB Controller (rev a4) (prog-if 20 [EHCI])
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Interrupt: pin C routed to IRQ 11
Region 0: Memory at ea000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [44] Debug port
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet Controller (rev a1)
Subsystem: ASUSTeK Computer Inc. A7N8X Mainboard onboard nForce2
Ethernet
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (250ns min, 5000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: Memory at ea001000 (32-bit, non-prefetchable) [size=4K] Region 1: I/O ports at c400 [size=8]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable+ DSel=0 DScale=0 PME-

00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97 Audio Controler (MCP) (rev a1)
Subsystem: ASUSTeK Computer Inc. nForce2 AC97 Audio Controler (MCP)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at b000 [size=256]
Region 1: I/O ports at b400 [size=128]
Region 2: Memory at ea002000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
I/O behind bridge: 00009000-00009fff
Memory behind bridge: fff00000-000fffff
Prefetchable memory behind bridge: fff00000-000fffff
Secondary status: 66MHz- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort+ <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr+ DiscTmrStat- DiscTmrSERREn-

00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2) (prog-if 8a [Master SecP PriP])
Subsystem: ASUSTeK Computer Inc. Unknown device 0c11
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0 (750ns min, 250ns max)
Region 0: [virtual] Memory at 000001f0 (32-bit, non-prefetchable)
[disabled] [size=8]
Region 1: [virtual] Memory at 000003f0 (type 3, non-prefetchable)
[disabled] [size=1]
Region 2: [virtual] Memory at 00000170 (32-bit, non-prefetchable)
[disabled] [size=8]
Region 3: [virtual] Memory at 00000370 (type 3, non-prefetchable)
[disabled] [size=1]
Region 4: I/O ports at f000 [size=16]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 240
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
I/O behind bridge: 0000a000-0000afff
Memory behind bridge: e8000000-e9ffffff
Prefetchable memory behind bridge: c0000000-dfffffff
Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR+ NoISA- VGA+ MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-

01:08.0 Multimedia audio controller: Creative Labs SB0400 Audigy2 Value
Subsystem: Creative Labs Unknown device 1021
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 240 (500ns min, 5000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9000 [size=64]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:00.0 VGA compatible controller: ATI Technologies Inc RV350 AP [Radeon 9600] (prog-if 00 [VGA])
Subsystem: C.P. Technology Co. Ltd PowerColor R96A-C3N
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 255 (2000ns min), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 5
Region 0: Memory at c0000000 (32-bit, prefetchable) [size=256M]
Region 1: I/O ports at a000 [size=256]
Region 2: Memory at e9000000 (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at e8000000 [disabled] [size=128K]
Capabilities: [58] AGP version 3.0

       Status: RQ=256 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 
64bit- FW+ AGP3+ Rate=x4,x8
       Command: RQ=1 ArqSz=0 Cal=0 SBA+ AGP- GART64- 64bit- FW- Rate=<none>

Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

02:00.1 Display controller: ATI Technologies Inc RV350 AP [Radeon 9600] (Secondary)
Subsystem: C.P. Technology Co. Ltd Unknown device 2065
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Region 0: Memory at d0000000 (32-bit, prefetchable) [disabled]
[size=256M]
Region 1: Memory at e9010000 (32-bit, non-prefetchable) [disabled]
[size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-

[7.6.] SCSI information (from /proc/scsi/scsi)

[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you think to be relevant):

[X.] Other notes, patches, fixes, workarounds:

kind regards,
Ivo

#1 lore raw
Quoted 16 lines

I followed the guidelines for a bug report.
If there is anything else needed, I'll be happy to do all the testing needed.

[1.] One line summary of the problem:
p54usb driver crashes on trying to associate with an ap with the CPWUA054 usb adapter

[2.] Full description of the problem/report:
What works:
modprobe p54usb
dmesg (displays my adapter correctly)
ifconfig up wlan0
dmesg (using the right firmware 2.5.6.0)

Quoted 4 lines

but trying to associate to my accesspoint (using wpa_supplicant) causes a hard-lock up (keyboard leds blinking).
Before locking up it spams loads of 'RX: unknown frame received phy1' messages on kmsg/dmesg.

Please switch to a VT (e.g. VT 1, usually by pressing ctrl-alt-f1) and associate by hand (e.g. iwconfig wlan0 essid "your ssid") and take a picture of the oops that comes out.

johannes

#2 lore raw

Sorry for the late reply, i just thought i install kernel 2.6.25 r4 and try again.

It is somewhat better and worse, when modprobing p54usb i got a small hang/hickup accompanied with the following error in dmesg ehci_hcd 0000:00:02.2: HC died; cleaning up

afterwards the kernel fails (refuses ?) to detect the device again. so I no longer get a kernel oops but even modprobbing doesnt work anymore. see attachment for full dmesg. any ideas, testing i an do now ?

kind regards,
Ivo Couckuyt

Quoted 17 lines · Johannes Berg
Quoted 13 lines

I followed the guidelines for a bug report.
If there is anything else needed, I'll be happy to do all the testing needed.

[1.] One line summary of the problem:
p54usb driver crashes on trying to associate with an ap with the CPWUA054 usb adapter

[2.] Full description of the problem/report:
What works:
modprobe p54usb
dmesg (displays my adapter correctly)
ifconfig up wlan0
dmesg (using the right firmware 2.5.6.0)

Quoted 3 lines

but trying to associate to my accesspoint (using wpa_supplicant) causes a hard-lock up (keyboard leds blinking). Before locking up it spams loads of 'RX: unknown frame received phy1' messages on kmsg/dmesg.

Quoted 6 lines

Please switch to a VT (e.g. VT 1, usually by pressing ctrl-alt-f1) and associate by hand (e.g. iwconfig wlan0 essid "your ssid") and take a picture of the oops that comes out.

johannes

usb 1-1: new high speed USB device using ehci_hcd and address 4 usb 1-1: configuration #1 chosen from 1 choice
p54: LM86 firmware
p54: FW rev 2.5.6.0 - Softmac protocol 3.0
ehci_hcd 0000:00:02.2: HC died; cleaning up
irq 11: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.25-gentoo-r4-BARTON #1

 [<c0149ee7>] __report_bad_irq+0x27/0x90
 [<c014a218>] note_interrupt+0x2c8/0x300
 [<c01493e1>] ? handle_IRQ_event+0x31/0x70
 [<c014aced>] handle_level_irq+0xdd/0x110
 [<c0105e26>] do_IRQ+0x46/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c01493c7>] ? handle_IRQ_event+0x17/0x70
 [<c014ac8a>] handle_level_irq+0x7a/0x110
 [<c0105e26>] do_IRQ+0x46/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c0120e92>] ? __do_softirq+0x42/0xb0
 [<c0120f35>] do_softirq+0x35/0x40
 [<c01210f4>] irq_exit+0x44/0x50
 [<c0105e2b>] do_IRQ+0x4b/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c0102b9d>] ? default_idle+0x4d/0x80
 [<c0102b50>] ? default_idle+0x0/0x80
 [<c0102af3>] cpu_idle+0x33/0x90
 [<c03caadc>] rest_init+0x5c/0x60
 =======================

handlers:
[<c02fef00>] (usb_hcd_irq+0x0/0x60) [<c02fef00>] (usb_hcd_irq+0x0/0x60) Disabling IRQ #11
usb 1-1: USB disconnect, address 4
usb 1-5: USB disconnect, address 3
usbcore: registered new interface driver prism54usb

#3 lore raw
Quoted 61 lines · Ivo Couckuyt

Sorry for the late reply, i just thought i install kernel 2.6.25 r4 and try again.

It is somewhat better and worse, when modprobing p54usb i got a small hang/hickup accompanied with the following error in dmesg ehci_hcd 0000:00:02.2: HC died; cleaning up

afterwards the kernel fails (refuses ?) to detect the device again. so I no longer get a kernel oops but even modprobbing doesnt work anymore. see attachment for full dmesg. any ideas, testing i an do now ?

kind regards,
Ivo Couckuyt

Quoted 21 lines · Johannes Berg
Quoted 15 lines

I followed the guidelines for a bug report.
If there is anything else needed, I'll be happy to do all the testing needed.

[1.] One line summary of the problem:
p54usb driver crashes on trying to associate with an ap with the CPWUA054 usb adapter

[2.] Full description of the problem/report:
What works:
modprobe p54usb
dmesg (displays my adapter correctly)
ifconfig up wlan0
dmesg (using the right firmware 2.5.6.0)

Quoted 5 lines

but trying to associate to my accesspoint (using wpa_supplicant) causes a hard-lock up (keyboard leds blinking).
Before locking up it spams loads of 'RX: unknown frame received phy1' messages on kmsg/dmesg.

Quoted 6 lines

Please switch to a VT (e.g. VT 1, usually by pressing ctrl-alt-f1) and associate by hand (e.g. iwconfig wlan0 essid "your ssid") and take a picture of the oops that comes out.

johannes

plain text document attachment (2.6.25_irq)
usb 1-1: new high speed USB device using ehci_hcd and address 4 usb 1-1: configuration #1 chosen from 1 choice
p54: LM86 firmware
p54: FW rev 2.5.6.0 - Softmac protocol 3.0
ehci_hcd 0000:00:02.2: HC died; cleaning up
irq 11: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.25-gentoo-r4-BARTON #1

 [<c0149ee7>] __report_bad_irq+0x27/0x90
 [<c014a218>] note_interrupt+0x2c8/0x300
 [<c01493e1>] ? handle_IRQ_event+0x31/0x70
 [<c014aced>] handle_level_irq+0xdd/0x110
 [<c0105e26>] do_IRQ+0x46/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c01493c7>] ? handle_IRQ_event+0x17/0x70
 [<c014ac8a>] handle_level_irq+0x7a/0x110
 [<c0105e26>] do_IRQ+0x46/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c0120e92>] ? __do_softirq+0x42/0xb0
Quoted 8 lines
 [<c0120f35>] do_softirq+0x35/0x40
 [<c01210f4>] irq_exit+0x44/0x50
 [<c0105e2b>] do_IRQ+0x4b/0x80
 [<c010415f>] common_interrupt+0x23/0x28
 [<c0102b9d>] ? default_idle+0x4d/0x80
 [<c0102b50>] ? default_idle+0x0/0x80
 [<c0102af3>] cpu_idle+0x33/0x90
 [<c03caadc>] rest_init+0x5c/0x60

Sorry, no idea. Christian?

johannes

#4 lore raw
Quoted 10 lines · On Sunday 08 June 2008 13:54:14 Johannes Berg wrote:
Quoted 7 lines · Ivo Couckuyt

Sorry for the late reply, i just thought i install kernel 2.6.25 r4 and try again.

It is somewhat better and worse, when modprobing p54usb i got a small hang/hickup accompanied with the following error in dmesg ehci_hcd 0000:00:02.2: HC died; cleaning up
[...]

Sorry, no idea. Christian?

Not yet... but card is on the way, so maybe in the future. :)

I googled for "HC died; cleaning up" and yes, there "are" other people with the same issue... But noone had a solutions other than use ndiswrapper.

So, i took a look at the driver... it ships with a really old firmware 2.4.6.0 So, I know that there are atleast some (mini)PCI Cards that have big problems with anything newer than 2.4.x.y, maybe there are broken USB-Parts too...

Ivo, can you please try the older firmware? You can find a copy @
(http://daemonizer.de/prism54/prism54-fw/ scroll down to USB).

If this doesn't work? could you please about ndiswrapper?

Regards,
Christian

#5 lore raw

i tried the following firmwares:
2.4.4.0.arm 2.4.6.0.arm
2.5.11.0.arm 2.5.6.0.arm 2.5.2.0.arm 2.7.0.0.arm
All give the same dmesg output, (HC died; cleaning up)
except 2.5.8.0.arm which gives something else, probably not worth much, but nevertheless see attachment

In the very beginning I used ndiswrapper without any problem (still works now), but at the moment i'm using the old islsm driver together
with kernel 2.6.9 and firmware 2.5.6.0 (only one that works), which doesn't seem to be on the site you mentioned
md5sum:
6ff238179cf9618aac2b5d7a34e41450 2.5.6.0.arm (is included for what it is worth)
So i've been stuck at kernel 2.6.9 for some time now as islsm doesn't compile with newer kernels :-) p54usb should be a relatively straight port from islsm yes ? except for the control rate algorithm and some cleaning up i guess.

ps: thanks for the effort.
ps2: firmware 2.5.7.0 isn't on site too: 09f9da7ea757173c9de1a0322a1f9782 2.7.0.0.arm

kind regards,
Ivo Couckuyt

Quoted 20 lines · Chr
Quoted 5 lines · On Sunday 08 June 2008 13:54:14 Johannes Berg wrote:
Quoted 3 lines · Ivo Couckuyt

Sorry for the late reply, i just thought i install kernel 2.6.25 r4 and try again.

Quoted 7 lines
Quoted 5 lines

It is somewhat better and worse, when modprobing p54usb i got a small hang/hickup accompanied with the following error in dmesg ehci_hcd 0000:00:02.2: HC died; cleaning up
[...]

Sorry, no idea. Christian?

Not yet... but card is on the way, so maybe in the future. :)

I googled for "HC died; cleaning up" and yes, there "are" other people with the same issue... But noone had a solutions other than use ndiswrapper.

So, i took a look at the driver... it ships with a really old firmware 2.4.6.0 So, I know that there are atleast some (mini)PCI Cards that have big problems with anything newer than 2.4.x.y, maybe there are broken USB-Parts too...

Quoted 9 lines

Ivo, can you please try the older firmware? You can find a copy @
(http://daemonizer.de/prism54/prism54-fw/ scroll down to USB).

If this doesn't work? could you please about ndiswrapper?

Regards,
Christian

usb 1-1: new high speed USB device using ehci_hcd and address 5 usb 1-1: configuration #1 chosen from 1 choice
p54: LM86 firmware
p54: FW rev 2.5.8.0 - Softmac protocol 3.0
prism54usb: probe of 1-1:1.0 failed with error -110
usbcore: registered new interface driver prism54usb

#6 lore raw
In reply to Ivo Couckuyt
Quoted 5 lines · Ivo Couckuyt

Note that my adapter isn't in the vendor:model id list of the p54 driver, my patch submitted for that is prob. lost somewhere.
But I'm using islsm with my usb adapters for >1.5 years with no problems. lsusb lists my device's model/vendor id
Bus 001 Device 002: ID 083a:5501 Accton Technology Corp.

This is the Internet, nothing is ever lost... :-)

FWIW, your old patch was against the prism54usb driver. I retargeted against p54usb and just posted it to this list. I'll send it upstream with the next round of fixes.

John

Signature · 2 lines
John W. Linville
[email protected]
#7 lore raw
Quoted 9 lines · John W. Linville

On Sun, Feb 10, 2008 at 11:25:30PM +0100, Ivo Couckuyt wrote:
This is the Internet, nothing is ever lost... :-)

FWIW, your old patch was against the prism54usb driver. I retargeted against p54usb and just posted it to this list. I'll send it upstream with the next round of fixes.

John

Great, thanks

Quoted 3 lines

Please switch to a VT (e.g. VT 1, usually by pressing ctrl-alt-f1) and associate by hand (e.g. iwconfig wlan0 essid "your ssid") and take a picture of the oops that comes out.

k, i configured my ap as plain text and turned off xorg.
In the first console I did:
ifconfig wlan0 up
iwconfig wlan0 essid ilm
dmesg shows several of this lines... which is normal scanning i believe:
...
HW CONFIG: channel=8 freq=2447 phymode=2
HW CONFIG: channel=9 freq=2452 phymode=2
HW CONFIG: channel=10 freq=2457 phymode=2
HW CONFIG: channel=11 freq=2462 phymode=2
HW CONFIG: channel=1 freq=2412 phymode=2
...
iwconfig -> Not-associated

wlan0 IEEE 802.11g ESSID:"ilm"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=27 dBm
Retry min limit:7 RTS thr:off Fragment thr=2346 B
Encryption key:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

but nothing, so i do
iwlist wlan0 scanning
which 99.99% of the time returns nothing, and very occasional one accesspoint that isn't mine.

configuring wpa_supplicant for plain text and starting it in the foreground gives me:
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - ioctl[SIOCSIWAUTH]: Operation not supported WEXT auth param 5 value 0x1 - ioctl[SIOCGIFADDR]: Cannot assign requested address ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIWSCAN]: Resource temporarily unavailable ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address
ioctl[SIOCGIFADDR]: Cannot assign requested address

Which i think isn't really relevant to the problem, in any case wpa_supplicant doesnt work. The strange thing is i don't get any oops anymore, that only happeneded with wpa_supplicant AND wpa enabled

Using the good old islsm driver i can configure it all manually without problems:
ifconfig eth1 up
iwlist eth1 scanning -> returns about 5 ap, including mine
iwconfig eth1 essid ilm
iwconfig -> shows associated
dhcpcd eth1 -> in business

so apparantly the p54usb/cpwua054 combination doesn't find the ap in the first place.
I vaguely remember some thread on the islsm mailing list about those unknown frame messages that may be related to the empty scan results, to be exact:
...
phy0: unknown frame RXed (0x20)
phy0: unknown frame RXed (0x30)
phy0: unknown frame RXed (0x30)
phy0: unknown frame RXed (0x20)
phy0: unknown frame RXed (0x20)
phy0: unknown frame RXed (0x20)
...

Next step is probably enabling debug in the p54usb driver i think, if possible. Any suggestions for tests i can do ?

kind regards,
Ivo Couckuyt