prism54: Out of memory, cannot handle oid, card/socket may be faulty, or IRQ line too busy
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I used the card in an ASUS WL-500gP router (mipsel).
Any ideas what it might be?
I used 2.6.23.1 kernel, below full data.
# lspci -vv -nn
00:02.0 Network controller [0280]: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] [1260:3890] (rev 01)
Subsystem: Intersil Corporation Unknown device [1260:0000]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium Quoted 1 line
TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 80 (2500ns min, 7000ns max), Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 6
Region 0: Memory at 40004000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [dc] Power Management version 1
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mAPME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
# ifconfig eth2
eth2 Link encap:Ethernet HWaddr 00:30:B4:00:00:00
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:6 Base address:0x4000# iwconfig (...) Warning: Driver for device eth2 has been compiled with version 22 of Wireless Extension, while this program supports up to version 20. Some things may be broken...
eth2 NOT READY! ESSID:off/any
Mode:Managed Channel:0 Access Point: Not-Associated
Tx-Power=31 dBm Sensitivity=0/200
Retry limit:0 RTS thr=0 B Fragment thr=0 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
# ifconfig eth2 up eth2: Out of memory, cannot handle oid 0x080002ff eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=19000001 err=-145 eth2: Out of memory, cannot handle oid 0x04000019 eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=12000004 err=-145 eth2: Out of memory, cannot handle oid 0x06000012 eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff02000c err=-145 eth2: interface reset failure prism54: Your card/socket may be faulty, or IRQ line too busy :( SIOCSIFFLAGS: Connection timed out
# dmesg -c Loaded prism54 driver, version 1.2 PCI: Fixing up device 0000:00:02.0 eth2: resetting device... eth2: uploading firmware... eth2: firmware version: 1.0.4.3 eth2: firmware upload complete eth2: Out of memory, cannot handle oid 0x080002ff eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=19000001 err=-145 eth2: Out of memory, cannot handle oid 0x04000019 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=12000004 err=-145 eth2: Out of memory, cannot handle oid 0x06000012 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff02000c err=-145 eth2: mgt_commit: failure eth2: interface reset failure prism54: Your card/socket may be faulty, or IRQ line too busy :(
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Quoted 3 lines · Tomasz Chmielewski
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I vaguely recall seeing an error like that when I used the wrong firmware. What firmware are you using?
John
Signature · 2 lines
John W. Linville [email protected]
Quoted 5 lines · John W. Linville
Quoted 1 line · Tomasz Chmielewski
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I vaguely recall seeing an error like that when I used the wrong firmware. What firmware are you using?
As specified here:
http://prism54.org/fullmac.html
Only PCI cards with an ISL3877, ISL3880 and ISL3890 work -> I used Version 1.0.4.3 (for ISL3880 and ISL3890)
My card is:
Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886
Is it ISL3890 or ISL3886?
Maybe I should use "Version 2.7.0.0 for PCI devices" firmware?
Will check tomorrow.
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Quoted 5 lines · John W. Linville
Quoted 1 line · Tomasz Chmielewski
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I vaguely recall seeing an error like that when I used the wrong firmware. What firmware are you using?
So, I tried with 2.7.0.0.arm firmware, and it's the same:
# dmesg Loaded prism54 driver, version 1.2 PCI: Fixing up device 0000:00:02.0 eth2: resetting device... eth2: uploading firmware... eth2: firmware version: 2.7.0.0 eth2: firmware upload complete eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff020008 err=-145 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=ff020003 err=-145 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=10000000 err=-145 eth2: timeout waiting for mgmt response 250, triggering device eth2: timeout waiting for mgmt response 225, triggering device eth2: timeout waiting for mgmt response 200, triggering device eth2: timeout waiting for mgmt response 175, triggering device eth2: timeout waiting for mgmt response 150, triggering device eth2: timeout waiting for mgmt response 125, triggering device eth2: timeout waiting for mgmt response 100, triggering device eth2: timeout waiting for mgmt response 75, triggering device eth2: timeout waiting for mgmt response 50, triggering device eth2: timeout waiting for mgmt response 25, triggering device eth2: timeout waiting for mgmt response eth2: mgt_commit_list: failure. oid=17000007 err=-145 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=19000001 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=10000002 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=19000004 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000000 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000001 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000002 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000004 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000005 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000006 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000007 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=12000003 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=150007e0 err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=ff02000c err=-12 eth2: mgmt tx queue is still full eth2: mgt_commit_list: failure. oid=ff020003 err=-12 eth2: mgmt tx queue is still full eth2: mgt_update_addr: failure eth2: mgt_commit: failure eth2: interface reset failure prism54: Your card/socket may be faulty, or IRQ line too busy :(
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Quoted 5 lines · John W. Linville
Quoted 1 line · Tomasz Chmielewski
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I vaguely recall seeing an error like that when I used the wrong firmware. What firmware are you using?
This is my card:
# lspci -nn (...) 00:02.0 Network controller [0280]: Intersil Corporation ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] [1260:3890] (rev 01)
According to http://prism54.org/newdrivers.html, my card is among the supported devices, and I should use version 2.7.0.0 for PCI devices firmware:
PCI Vendor (hex) PCI Product (hex) Common name
1260 3890 Generic ISL3890
It doesn't work and says "Your card/socket may be faulty, or IRQ line too busy". With 2.7.0.0 firmware, it doesn't say "out of memory" anymore.
Are there more things to be done to make this card work?
Signature · 2 lines
Tomasz Chmielewski http://wpkg.org
Hi,
I'm having the same problem with my Netgear WG511 (PCMCIA, SoftMAC version) and Kernel 2.6.24.
With 2.6.23 and the drivers from www.linuxwireless.org (compat-wireless-2.6) it works. At least most of the time. More or less regulary there is an ACPI error message telling me that the IRQ of the card has been disabled. Then I have to replug it to get it up again. I'm using the same firmware with both kernels/drivers (v2.7.0.0).
Regards,
Reinhard Biegel
Quoted 9 lines · On Friday, 8. February 2008 23:10:09 you wrote:
Quoted 3 lines · Tomasz Chmielewski
I just wanted to use a mini-PCI card using a prism54 module - however, it fails to bring the interface up with "Out of memory, cannot handle oid" and "Your card/socket may be faulty, or IRQ line too busy" messages.
I vaguely recall seeing an error like that when I used the wrong firmware. What firmware are you using?
John