* PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
@ 2008-02-10 22:25 Ivo Couckuyt
2008-02-20 18:40 ` Johannes Berg
2008-02-20 20:09 ` John W. Linville
0 siblings, 2 replies; 13+ messages in thread
From: Ivo Couckuyt @ 2008-02-10 22:25 UTC (permalink / raw)
To: linux-wireless
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
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-02-10 22:25 PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter Ivo Couckuyt
@ 2008-02-20 18:40 ` Johannes Berg
2008-06-06 21:06 ` Ivo Couckuyt
2008-02-20 20:09 ` John W. Linville
1 sibling, 1 reply; 13+ messages in thread
From: Johannes Berg @ 2008-02-20 18:40 UTC (permalink / raw)
To: Ivo Couckuyt; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
> 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.
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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-02-20 18:40 ` Johannes Berg
@ 2008-06-06 21:06 ` Ivo Couckuyt
2008-06-08 11:54 ` Johannes Berg
0 siblings, 1 reply; 13+ messages in thread
From: Ivo Couckuyt @ 2008-06-06 21:06 UTC (permalink / raw)
To: Johannes Berg; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
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
Johannes Berg wrote:
>> 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.
>>
>
> 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
>
[-- Attachment #2: 2.6.25_irq --]
[-- Type: text/plain, Size: 1305 bytes --]
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-06-06 21:06 ` Ivo Couckuyt
@ 2008-06-08 11:54 ` Johannes Berg
2008-06-08 20:03 ` Chr
0 siblings, 1 reply; 13+ messages in thread
From: Johannes Berg @ 2008-06-08 11:54 UTC (permalink / raw)
To: Ivo Couckuyt; +Cc: linux-wireless, Chr
[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]
On Fri, 2008-06-06 at 23:06 +0200, Ivo Couckuyt wrote:
> 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
>
> Johannes Berg wrote:
> >> 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.
> >>
> >
> > 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
> [<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
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-06-08 11:54 ` Johannes Berg
@ 2008-06-08 20:03 ` Chr
2008-06-08 21:23 ` Ivo Couckuyt
0 siblings, 1 reply; 13+ messages in thread
From: Chr @ 2008-06-08 20:03 UTC (permalink / raw)
To: Johannes Berg; +Cc: Ivo Couckuyt, linux-wireless
On Sunday 08 June 2008 13:54:14 Johannes Berg wrote:
> On Fri, 2008-06-06 at 23:06 +0200, Ivo Couckuyt wrote:
> > 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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-06-08 20:03 ` Chr
@ 2008-06-08 21:23 ` Ivo Couckuyt
0 siblings, 0 replies; 13+ messages in thread
From: Ivo Couckuyt @ 2008-06-08 21:23 UTC (permalink / raw)
To: Chr; +Cc: Johannes Berg, linux-wireless
[-- Attachment #1: Type: text/plain, Size: 2155 bytes --]
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
Chr wrote:
> On Sunday 08 June 2008 13:54:14 Johannes Berg wrote:
>
>> On Fri, 2008-06-06 at 23:06 +0200, Ivo Couckuyt wrote:
>>
>>> 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
>
>
[-- Attachment #2: 2.5.8.0.err --]
[-- Type: text/plain, Size: 277 bytes --]
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
[-- Attachment #3: 2.5.6.0.arm --]
[-- Type: application/octet-stream, Size: 30176 bytes --]
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-02-10 22:25 PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter Ivo Couckuyt
2008-02-20 18:40 ` Johannes Berg
@ 2008-02-20 20:09 ` John W. Linville
2008-02-11 2:04 ` Ivo Couckuyt
1 sibling, 1 reply; 13+ messages in thread
From: John W. Linville @ 2008-02-20 20:09 UTC (permalink / raw)
To: Ivo Couckuyt; +Cc: linux-wireless
On Sun, Feb 10, 2008 at 11:25:30PM +0100, Ivo Couckuyt wrote:
> 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
--
John W. Linville
linville@tuxdriver.com
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-02-20 20:09 ` John W. Linville
@ 2008-02-11 2:04 ` Ivo Couckuyt
0 siblings, 0 replies; 13+ messages in thread
From: Ivo Couckuyt @ 2008-02-11 2:04 UTC (permalink / raw)
To: John W. Linville; +Cc: linux-wireless
John W. Linville wrote:
> 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
> 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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
@ 2008-07-02 17:07 Ivo Couckuyt
2008-07-02 17:26 ` Chr
0 siblings, 1 reply; 13+ messages in thread
From: Ivo Couckuyt @ 2008-07-02 17:07 UTC (permalink / raw)
To: linux-wireless
sent this a while ago, but might be filtered due to attachment (removed
now):
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
Chr wrote:
> On Sunday 08 June 2008 13:54:14 Johannes Berg wrote:
>
>> On Fri, 2008-06-06 at 23:06 +0200, Ivo Couckuyt wrote:
>>
>>> 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
>
>
------------------------------------------------------------------------
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
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-07-02 17:07 Ivo Couckuyt
@ 2008-07-02 17:26 ` Chr
2008-07-02 20:31 ` Ivo Couckuyt
0 siblings, 1 reply; 13+ messages in thread
From: Chr @ 2008-07-02 17:26 UTC (permalink / raw)
To: Ivo Couckuyt; +Cc: linux-wireless
On Wednesday 02 July 2008 19:07:32 Ivo Couckuyt wrote:
> sent this a while ago, but might be filtered due to attachment (removed
> now):
>
> 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)
No, your post didn't get lost...
however I don't know what's wrong with it, as my USB device is
probably ?still? sitting in the custom office.. *sigh*. And even then,
when I'll finally get it... It probably differs alot from yours.
However... the p54 code has sometimes some timing problems,
that islsm didn't have?! so what happends have you add some
delays inside the the initialization/probe code?
(BTW: do you have a "lsusb -v" of the wlan stick somewhere?)
Regards,
Christian
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-07-02 17:26 ` Chr
@ 2008-07-02 20:31 ` Ivo Couckuyt
2008-07-04 17:56 ` Chr
0 siblings, 1 reply; 13+ messages in thread
From: Ivo Couckuyt @ 2008-07-02 20:31 UTC (permalink / raw)
To: Chr; +Cc: linux-wireless
[-- Attachment #1: Type: text/plain, Size: 3069 bytes --]
Chr wrote:
> On Wednesday 02 July 2008 19:07:32 Ivo Couckuyt wrote:
>
>> sent this a while ago, but might be filtered due to attachment (removed
>> now):
>>
>> 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)
>>
>
> No, your post didn't get lost...
>
> however I don't know what's wrong with it, as my USB device is
> probably ?still? sitting in the custom office.. *sigh*. And even then,
> when I'll finally get it... It probably differs alot from yours.
>
> However... the p54 code has sometimes some timing problems,
> that islsm didn't have?! so what happends have you add some
> delays inside the the initialization/probe code?
>
Added several delays (mdelay(200) )in the probe and/or init code didn't
change a thing (except that it takes longer before it gets to the part
where it errors :-) ).
I also added some prints to narrow it down (tedious work, have to
restart everytime i make a change). dmesg log is attached (ILM:
statements were added).
snippet of changed code where it seems to fail, it is in p54usc.c
function p54u_upload_firmware_net2280:
...
printk(KERN_INFO "ILM: usb_interrupt...\n" );
err = usb_interrupt_msg(priv->udev,
usb_rcvbulkpipe(priv->udev, P54U_PIPE_INT),
buf, sizeof(__le32), &alen, 1000);
printk(KERN_INFO "ILM: call finished (error %i)
(sizeof(__le32)=%i=%i)...\n", err, sizeof(__le32), alen );
if (err || alen != sizeof(__le32))
goto fail;
mdelay(200);
P54U_READ(NET2280_DEV_U32, &devreg->int_ident);
P54U_WRITE(NET2280_DEV_U32, &devreg->int_ack, reg);
if (!(reg & cpu_to_le32(ISL38XX_INT_IDENT_INIT)))
err = -EINVAL;
printk(KERN_INFO "ILM: some read/acks: error %i", err );
P54U_WRITE(NET2280_BRG_U32, NET2280_USBIRQENB1, 0);
P54U_WRITE(NET2280_BRG_U32, NET2280_IRQSTAT1,
cpu_to_le32(NET2280_PCI_INTA_INTERRUPT));
printk(KERN_INFO "ILM: startup firmware OK\n" );
...
so the usb_interrupt thing might be related somehow (causes the HC
failed), or it is just that the usb stick should send 'keep-alive' irq's
but doesn't because initialization before that has actually failed ?
(don't know
anything about kernel dev, just guessing here).
so the
P54U_READ(NET2280_DEV_U32, &devreg->int_ident);
P54U_WRITE(NET2280_DEV_U32, &devreg->int_ack, reg);
causes the actually 'goto fail'.
> (BTW: do you have a "lsusb -v" of the wlan stick somewhere?)
>
sure, attached.
> Regards,
> Christian
>
>
[-- Attachment #2: lsusb.out --]
[-- Type: text/plain, Size: 5635 bytes --]
Bus 001 Device 002: ID 083a:5501 Accton Technology Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x083a Accton Technology Corp.
idProduct 0x5501
bcdDevice 2.02
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 95
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 11
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8d EP 13 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0d EP 13 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x0e EP 14 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8f EP 15 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 1
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0002
(Bus Powered)
Remote Wakeup Enabled
[-- Attachment #3: 2.6.25_debug.dmesg --]
[-- Type: text/plain, Size: 15415 bytes --]
896MB will be used.
Use a HIGHMEM enabled kernel.
896MB LOWMEM available.
Entering add_active_range(0, 0, 229376) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 -> 229376
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0 -> 229376
On node 0 totalpages: 229376
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 1760 pages used for memmap
Normal zone: 223520 pages, LIFO batch:31
Movable zone: 0 pages used for memmap
DMI 2.2 present.
ACPI: RSDP 000F75C0, 0014 (r0 Nvidia)
ACPI: RSDT 3FFF3000, 002C (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: FACP 3FFF3040, 0074 (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: DSDT 3FFF30C0, 43E7 (r1 NVIDIA AWRDACPI 1000 MSFT 100000E)
ACPI: FACS 3FFF0000, 0040
ACPI: APIC 3FFF74C0, 006E (r1 Nvidia AWRDACPI 42302E31 AWRD 0)
ACPI: PM-Timer IO Port: 0x4008
Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227584
Kernel command line: root=/dev/hdb3
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 16384 bytes)
Detected 1830.012 MHz processor.
Console: colour VGA+ 80x25
console [tty0] enabled
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 904820k/917504k available (2894k kernel code, 12196k reserved, 943k data, 196k init, 0k highmem)
virtual kernel memory layout:
fixmap : 0xffff6000 - 0xfffff000 ( 36 kB)
vmalloc : 0xf8800000 - 0xffff4000 ( 119 MB)
lowmem : 0xc0000000 - 0xf8000000 ( 896 MB)
.init : 0xc04c2000 - 0xc04f3000 ( 196 kB)
.data : 0xc03d3a36 - 0xc04bf918 ( 943 kB)
.text : 0xc0100000 - 0xc03d3a36 (2894 kB)
Checking if this processor honours the WP bit even in supervisor mode...Ok.
CPA: page pool initialized 1 of 1 pages preallocated
Calibrating delay using timer specific routine.. 3663.11 BogoMIPS (lpj=7326232)
Mount-cache hash table entries: 512
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Compat vDSO mapped to ffffe000.
CPU: AMD Athlon(tm) XP 2500+ stepping 00
Checking 'hlt' instruction... OK.
Freeing SMP alternatives: 0k freed
ACPI: Core revision 20070126
ACPI: setting ELCR to 0200 (from 0820)
net_namespace: 440 bytes
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: PCI BIOS revision 2.10 entry at 0xfb4a0, last bus=2
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: EC: Look up EC in DSDT
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S5)
ACPI: Using PIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
pci 0000:00:00.0: nForce2 C1 Halt Disconnect fixup
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.HUB0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGPB._PRT]
ACPI: PCI Interrupt Link [LNK1] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK2] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNK3] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNK4] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNK5] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LUBA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LUBB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMAC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LAPU] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LACI] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LMCI] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LSMB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LUB2] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LFIR] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [L3CM] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LIDE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [APC1] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APC2] (IRQs *17), disabled.
ACPI: PCI Interrupt Link [APC3] (IRQs *18)
ACPI: PCI Interrupt Link [APC4] (IRQs *19)
ACPI: PCI Interrupt Link [APC5] (IRQs *16), disabled.
ACPI: PCI Interrupt Link [APCF] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCG] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCH] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCI] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCJ] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCK] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCS] (IRQs *23)
ACPI: PCI Interrupt Link [APCL] (IRQs 20 21 22) *0
ACPI: PCI Interrupt Link [APCM] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [AP3C] (IRQs 20 21 22) *0, disabled.
ACPI: PCI Interrupt Link [APCZ] (IRQs 20 21 22) *0, disabled.
Linux Plug and Play Support v0.97 (c) Adam Belay
pnp: PnP ACPI init
ACPI: bus type pnp registered
pnp: PnP ACPI: found 17 devices
ACPI: ACPI bus type pnp unregistered
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a report
system 00:00: ioport range 0x4000-0x407f has been reserved
system 00:00: ioport range 0x4080-0x40ff has been reserved
system 00:00: ioport range 0x4400-0x447f has been reserved
system 00:00: ioport range 0x4480-0x44ff has been reserved
system 00:00: ioport range 0x4200-0x427f has been reserved
system 00:00: ioport range 0x4280-0x42ff has been reserved
system 00:01: ioport range 0x5000-0x503f has been reserved
system 00:01: ioport range 0x5500-0x553f has been reserved
system 00:02: iomem range 0xd1800-0xd3fff has been reserved
system 00:02: iomem range 0xf0000-0xf7fff could not be reserved
system 00:02: iomem range 0xf8000-0xfbfff could not be reserved
system 00:02: iomem range 0xfc000-0xfffff could not be reserved
system 00:02: iomem range 0x3fff0000-0x3fffffff could not be reserved
system 00:02: iomem range 0xffff0000-0xffffffff could not be reserved
system 00:02: iomem range 0x0-0x9ffff could not be reserved
system 00:02: iomem range 0x100000-0x3ffeffff could not be reserved
system 00:02: iomem range 0xfec00000-0xfec00fff could not be reserved
system 00:02: iomem range 0xfee00000-0xfee00fff could not be reserved
system 00:04: ioport range 0x4d0-0x4d1 has been reserved
PCI: Bridge: 0000:00:08.0
IO window: 9000-9fff
MEM window: disabled.
PREFETCH window: disabled.
PCI: Bridge: 0000:00:1e.0
IO window: a000-afff
MEM window: 0xe4000000-0xe5ffffff
PREFETCH window: 0x00000000c0000000-0x00000000dfffffff
PCI: Setting latency timer of device 0000:00:08.0 to 64
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
Machine check exception polling timer started.
audit: initializing netlink socket (disabled)
type=2000 audit(1215036259.316:1): initialized
NTFS driver 2.1.29 [Flags: R/O].
io scheduler noop registered (default)
pci 0000:02:00.0: Boot video device
lp: driver loaded but no devices found
input: Power Button (FF) as /class/input/input0
ACPI: Power Button (FF) [PWRF]
input: Power Button (CM) as /class/input/input1
ACPI: Power Button (CM) [PWRB]
ACPI: ACPI0007:00 is registered as cooling_device0
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
00:0a: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:0b: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport_pc 00:0c: reported by Plug and Play ACPI
parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP(,...)]
lp0: using parport0 (interrupt-driven).
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: module loaded
Uniform Multi-Platform E-IDE driver
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE2: 0000:00:09.0 (rev a2) UDMA133 controller
NFORCE2: IDE controller (0x10de:0x0065 rev 0xa2) at PCI slot 0000:00:09.0
NFORCE2: not 100% native mode: will probe irqs later
NFORCE2: BIOS didn't set cable bits correctly. Enabling workaround.
ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: Maxtor 6Y080L0, ATA DISK drive
hdb: ST340016A, ATA DISK drive
hda: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hda: UDMA/133 mode selected
hdb: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdb: UDMA/100 mode selected
Probing IDE interface ide1...
hdc: TSSTcorpCD/DVDW SH-S182D, ATAPI CD/DVD-ROM drive
hdd: LITE-ON LTR-52327S, ATAPI CD/DVD-ROM drive
hdc: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdc: UDMA/33 mode selected
hdd: host max PIO5 wanted PIO255(auto-tune) selected PIO4
hdd: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63
hda: cache flushes supported
hda: hda1 hda2 < hda5 >
hdb: max request size: 128KiB
hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63
hdb: cache flushes not supported
hdb: hdb1 hdb2 hdb3
hdc: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
hdd: ATAPI 52X CD-ROM CD-R/RW drive, 2048kB Cache
Driver 'sd' needs updating - please use bus_type methods
ACPI: PCI Interrupt Link [LUB2] enabled at IRQ 11
PCI: setting IRQ 11 as level-triggered
ACPI: PCI Interrupt 0000:00:02.2[C] -> Link [LUB2] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:02.2 to 64
ehci_hcd 0000:00:02.2: EHCI Host Controller
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:02.2: debug port 1
PCI: cache line size of 64 is not supported by device 0000:00:02.2
ehci_hcd 0000:00:02.2: irq 11, io mem 0xe6000000
ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 6 ports detected
ohci_hcd: 2006 August 04 USB 1.1 'Open' Host Controller (OHCI) Driver
ACPI: PCI Interrupt Link [LUBA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:02.0[A] -> Link [LUBA] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:02.0 to 64
ohci_hcd 0000:00:02.0: OHCI Host Controller
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
ohci_hcd 0000:00:02.0: irq 11, io mem 0xe6004000
usb usb2: configuration #1 chosen from 1 choice
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
ACPI: PCI Interrupt Link [LUBB] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:02.1[B] -> Link [LUBB] -> GSI 5 (level, low) -> IRQ 5
PCI: Setting latency timer of device 0000:00:02.1 to 64
ohci_hcd 0000:00:02.1: OHCI Host Controller
ohci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 3
ohci_hcd 0000:00:02.1: irq 5, io mem 0xe6005000
hub 1-0:1.0: unable to enumerate USB device on port 4
usb usb3: configuration #1 chosen from 1 choice
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 3 ports detected
Initializing USB Mass Storage driver...
usb 1-5: new high speed USB device using ehci_hcd and address 3
usb 1-5: configuration #1 chosen from 1 choice
usb 3-2: new low speed USB device using ohci_hcd and address 2
usb 3-2: configuration #1 chosen from 1 choice
scsi0 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
input: AT Translated Set 2 keyboard as /class/input/input2
i2c /dev entries driver
i2c-adapter i2c-0: nForce2 SMBus adapter at 0x5000
i2c-adapter i2c-1: nForce2 SMBus adapter at 0x5500
input: ImExPS/2 Generic Explorer Mouse as /class/input/input3
scsi 0:0:0:0: Direct-Access Maxtor 6 L200P0 0000 PQ: 0 ANSI: 0
sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors (203928 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 27 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sd 0:0:0:0: [sda] 398297088 512-byte hardware sectors (203928 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 27 00 00 00
sd 0:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
usb-storage: device scan complete
drivers/hid/usbhid/hid-core.c: usb_submit_urb(ctrl) failed
drivers/hid/usbhid/hid-core.c: timeout initializing reports
input: Logitech Inc. WingMan Extreme Digital 3D as /class/input/input4
input: USB HID v1.00 Joystick [Logitech Inc. WingMan Extreme Digital 3D] on usb-0000:00:02.1-2
usbcore: registered new interface driver usbhid
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
Using IPI Shortcut mode
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 196k freed
Linux agpgart interface v0.103
agpgart: Detected NVIDIA nForce2 chipset
agpgart: AGP aperture is 64M @ 0xe0000000
forcedeth: Reverse Engineered nForce ethernet driver. Version 0.61.
ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 11
ACPI: PCI Interrupt 0000:00:04.0[A] -> Link [LMAC] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:00:04.0 to 64
forcedeth 0000:00:04.0: ifname eth0, PHY OUI 0x20 @ 1, addr 00:0c:6e:2b:95:8f
forcedeth 0000:00:04.0: timirq lnktim desc-v1
EXT3 FS on hdb3, internal journal
NTFS volume version 3.1.
eth0: no link during initialization.
Adding 500464k swap on /dev/hdb2. Priority:-1 extents:1 across:500464k
usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: configuration #1 chosen from 1 choice
ILM: net2280 uploading...
p54: LM86 firmware
p54: FW rev 2.5.6.0 - Softmac protocol 3.0
ILM: request_firmware + parse_firmware OK
ILM: power up bridge OK
ILM: still OK
ILM: bridge setup OK
ILM: boot device OK
ILM: upload firmware OK
ILM: ramboot OK
ILM: usb_interrupt...
ehci_hcd 0000:00:02.2: HC died; cleaning up
usb 1-1: USB disconnect, address 4
ILM: call finished (error 0) (sizeof(__le32)=4=4)...
ILM: done uploading (error -19)
usb 1-5: USB disconnect, address 3
usbcore: registered new interface driver prism54usb
^ permalink raw reply [flat|nested] 13+ messages in thread* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-07-02 20:31 ` Ivo Couckuyt
@ 2008-07-04 17:56 ` Chr
2008-07-04 18:21 ` Alan Stern
0 siblings, 1 reply; 13+ messages in thread
From: Chr @ 2008-07-04 17:56 UTC (permalink / raw)
To: Ivo Couckuyt, linux-usb; +Cc: linux-wireless
On Wednesday 02 July 2008 22:31:14 Ivo Couckuyt wrote:
(Please keep the CC if you want to answer, Thanks!)
> Chr wrote:
> > On Wednesday 02 July 2008 19:07:32 Ivo Couckuyt wrote:
> [...]
> >> 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), [...]
> I also added some prints to narrow it down (tedious work, have to
> restart everytime i make a change). dmesg log is attached (ILM:
> statements were added).
>
> snippet of changed code where it seems to fail, it is in p54usc.c
> function p54u_upload_firmware_net2280:
> ...
> printk(KERN_INFO "ILM: usb_interrupt...\n" );
>
> err = usb_interrupt_msg(priv->udev,
> usb_rcvbulkpipe(priv->udev, P54U_PIPE_INT),
> buf, sizeof(__le32), &alen, 1000);
> printk(KERN_INFO "ILM: call finished (error %i)
> (sizeof(__le32)=%i=%i)...\n", err, sizeof(__le32), alen );
> if (err || alen != sizeof(__le32))
> goto fail;
> [...]
>-> dmesg output: <-
>ILM: usb_interrupt...
>ehci_hcd 0000:00:02.2: HC died; cleaning up
>usb 1-1: USB disconnect, address 4
> ...
>
> so the usb_interrupt thing might be related somehow (causes the HC
> failed), or it is just that the usb stick should send 'keep-alive' irq's
> but doesn't because initialization before that has actually failed ?
> (don't know anything about kernel dev, just guessing here).
>
Well, since the USB stack from 2.6.9 differs a lot from the current 2.6.25
and the p54usb is a _copy_ of islsm (in that regard) and unless my eyes are
really that bad. the p54usb driver "should" work as good as islsm/ndiswrapper.
So, maybe someone of the linux-usb people knows why this happens?!
How to fix it, or how to DEBUG?! (any tips/hints? or is there a util like
strace/usbsnopper which can monitor/compare the function-calls and
the resulting traffic of ndiswrapper AND the p54usb driver?)
(Chipset seems to be a nForce 2 OHCI/EHCI):
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
[...]
handlers:
[<c02fef00>] (usb_hcd_irq+0x0/0x60)
[<c02fef00>] (usb_hcd_irq+0x0/0x60) Disabling IRQ #11
(full: http://article.gmane.org/gmane.linux.kernel.wireless.general/15841)
"
More References (including lsusb -v, lspci -v and many more):
http://www.spinics.net/lists/linux-wireless/msg15834.html
http://article.gmane.org/gmane.linux.kernel.wireless.general/11525
http://article.gmane.org/gmane.linux.kernel.wireless.general/17170
Regards,
Chr.
^ permalink raw reply [flat|nested] 13+ messages in thread
* Re: PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter
2008-07-04 17:56 ` Chr
@ 2008-07-04 18:21 ` Alan Stern
0 siblings, 0 replies; 13+ messages in thread
From: Alan Stern @ 2008-07-04 18:21 UTC (permalink / raw)
To: Chr; +Cc: Ivo Couckuyt, linux-usb, linux-wireless
On Fri, 4 Jul 2008, Chr wrote:
> So, maybe someone of the linux-usb people knows why this happens?!
> How to fix it, or how to DEBUG?! (any tips/hints? or is there a util like
> strace/usbsnopper which can monitor/compare the function-calls and
> the resulting traffic of ndiswrapper AND the p54usb driver?)
> (Chipset seems to be a nForce 2 OHCI/EHCI):
See Documentation/usb/usbmon.txt.
Alan Stern
^ permalink raw reply [flat|nested] 13+ messages in thread
end of thread, other threads:[~2008-07-04 18:21 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-02-10 22:25 PROBLEM: p54usb doesn't work with my Philips CPWUA054 usb adapter Ivo Couckuyt
2008-02-20 18:40 ` Johannes Berg
2008-06-06 21:06 ` Ivo Couckuyt
2008-06-08 11:54 ` Johannes Berg
2008-06-08 20:03 ` Chr
2008-06-08 21:23 ` Ivo Couckuyt
2008-02-20 20:09 ` John W. Linville
2008-02-11 2:04 ` Ivo Couckuyt
-- strict thread matches above, loose matches on Subject: below --
2008-07-02 17:07 Ivo Couckuyt
2008-07-02 17:26 ` Chr
2008-07-02 20:31 ` Ivo Couckuyt
2008-07-04 17:56 ` Chr
2008-07-04 18:21 ` Alan Stern
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).