Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
You might find this thread useful if it is just a case of messed up firmware: http://sourceforge.net/mailarchive/message.php?msg_id=2970511 The gist of it is that sometimes DOS utilities work when all else fails. ben --- Ivan Matveich [EMAIL PROTECTED] wrote: On 11/2/06, Dan Williams [EMAIL PROTECTED] wrote: Do you know which kernel version that patch first appeared in? It was committed on 1 Dec 2005, and 2.6.15 was released on 3 Jan 2006. That would be a great idea, let us know what the results are, especially if you cna figure out which firmware version you have, or if the card itself is really just dead. No luck with freebsd: error resetting card. I'll try my luck with Cisco's Windows utility---probably tomorrow---but I'd now wager that my card has simply croaked. (I've even taken it out and re-seated it in its slot, just in case that helped.) In any case, thanks for the help. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
On Wed, 2006-11-01 at 22:14 -0500, Ivan Matveich wrote: hardware: ibm thinkpad t30 kernel: 2.6.18 problem: airo(): Probing for PCI adapters ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI Interrupt :02:02.0[A] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 airo(eth1): Found an MPI350 card airo(eth1): Max tries exceeded when issueing command airo(eth1): Couldn't allocate RX FID airo(eth1): Could not map memory airo(): Finished probing for PCI adapters It appears that the driver cannot talk to your card; see the max tries exceeded when issueing command. Did this card work previously with a kernel? Can narrow down which kernels have problems and which don't? Any ideas? 1) Firmware upgrade/downgrade? (How?) It's a bit hard to figure out what firmware you have because the driver can't talk to the card; can you boot under Windows and determine that using the Cisco wireless utility? You also need to flash the card under Windows, not Linux, ideally to a version of firmware greater than 5.60.08. 2) Command sequence to better reset the card? Documentation? reloading the driver (rmmod airo; modprobe airo) should reset the card. Dan - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
On 11/2/06, Dan Williams [EMAIL PROTECTED] wrote: It appears that the driver cannot talk to your card; see the max tries exceeded when issueing command. Did this card work previously with a kernel? Can narrow down which kernels have problems and which don't? It spontaneously stopped working about a week after I bought the laptop and installed Linux. I tried kernel 2.6.12 and it had the same problem. (Let me know if you'd like me to try a specific version.) I'm hoping that the card has simply got itself into some kind of invalid state, and not failed altogether. It's a bit hard to figure out what firmware you have because the driver can't talk to the card; can you boot under Windows and determine that using the Cisco wireless utility? You also need to flash the card under Windows, not Linux, ideally to a version of firmware greater than 5.60.08. I haven't run Windows in many years, so that's problematic. What's the most straightforward way to boot into a Windows environment sufficient to run the Cisco wireless utility? reloading the driver (rmmod airo; modprobe airo) should reset the card. Yeah, it unfortunately doesn't help. (Nor does rebooting or resetting the bios.) I noticed a suspiciously relevant commit in the airo.c git log: [wireless airo] reset card in init without this patch after an rmmod, modprobe the card won't work anymore until the next reboot. This patch seem safe to apply for all cards as the bsd driver already do that. I had to add a timeout because strange things happen (issuecommand will fail) if the card is already reseted (after a reboot). PS : it seems there are missing reset when leaving monitor mode... Signed-off-by: Matthieu CASTET [EMAIL PROTECTED] and that makes me wonder if there might be some kind of subtle bug in the card initialization sequence that manifests itself with my particular card/firmware. I think I'll burn a freebsd livecd today and see if their kernel works. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
On Thu, 2006-11-02 at 13:30 -0500, Ivan Matveich wrote: On 11/2/06, Dan Williams [EMAIL PROTECTED] wrote: It appears that the driver cannot talk to your card; see the max tries exceeded when issueing command. Did this card work previously with a kernel? Can narrow down which kernels have problems and which don't? It spontaneously stopped working about a week after I bought the That does not bode well for the card itself. laptop and installed Linux. I tried kernel 2.6.12 and it had the same problem. (Let me know if you'd like me to try a specific version.) 2.6.12 should be old enough, but maybe if you could try 2.6.9 that would definitely be old enough to rule out recent airo changes. I'm hoping that the card has simply got itself into some kind of invalid state, and not failed altogether. It's a bit hard to figure out what firmware you have because the driver can't talk to the card; can you boot under Windows and determine that using the Cisco wireless utility? You also need to flash the card under Windows, not Linux, ideally to a version of firmware greater than 5.60.08. I haven't run Windows in many years, so that's problematic. What's the most straightforward way to boot into a Windows environment sufficient to run the Cisco wireless utility? You get to either install windows on your laptop, or pull the card (pcmcia or minipci, either way) and put it into a windows computer. reloading the driver (rmmod airo; modprobe airo) should reset the card. Yeah, it unfortunately doesn't help. (Nor does rebooting or resetting the bios.) I noticed a suspiciously relevant commit in the airo.c git log: [wireless airo] reset card in init without this patch after an rmmod, modprobe the card won't work anymore until the next reboot. This patch seem safe to apply for all cards as the bsd driver already do that. I had to add a timeout because strange things happen (issuecommand will fail) if the card is already reseted (after a reboot). PS : it seems there are missing reset when leaving monitor mode... Signed-off-by: Matthieu CASTET [EMAIL PROTECTED] Do you know which kernel version that patch first appeared in? and that makes me wonder if there might be some kind of subtle bug in the card initialization sequence that manifests itself with my particular card/firmware. Could be, it would be quite helpful to get the version of firmware you are using. Versions earlier than 5.30.17 are known not be flaky or even not work with newer Linux kernel drivers since Cisco changed the firmware interface in that version. That said, I've seen cards in the 5.00.xx range work with the latest drivers, but not well. These older firmware versions sometimes lock up sponaneously and require a reboot, updating to later firmware post-5.30.17 fixes that problem. I think I'll burn a freebsd livecd today and see if their kernel works. That would be a great idea, let us know what the results are, especially if you cna figure out which firmware version you have, or if the card itself is really just dead. Thanks, Dan - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
On 11/2/06, Dan Williams [EMAIL PROTECTED] wrote: Do you know which kernel version that patch first appeared in? It was committed on 1 Dec 2005, and 2.6.15 was released on 3 Jan 2006. That would be a great idea, let us know what the results are, especially if you cna figure out which firmware version you have, or if the card itself is really just dead. No luck with freebsd: error resetting card. I'll try my luck with Cisco's Windows utility---probably tomorrow---but I'd now wager that my card has simply croaked. (I've even taken it out and re-seated it in its slot, just in case that helped.) In any case, thanks for the help. - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
On Thu, Nov 02, 2006 at 04:21:16PM -0500, Ivan Matveich wrote: On 11/2/06, Dan Williams [EMAIL PROTECTED] wrote: Do you know which kernel version that patch first appeared in? It was committed on 1 Dec 2005, and 2.6.15 was released on 3 Jan 2006. That would be a great idea, let us know what the results are, especially if you cna figure out which firmware version you have, or if the card itself is really just dead. No luck with freebsd: error resetting card. I'll try my luck with Cisco's Windows utility---probably tomorrow---but I'd now wager that my card has simply croaked. (I've even taken it out and re-seated it in its slot, just in case that helped.) In any case, thanks for the help. Just remembered... Check the IRQ allocation. I remmeber having issues with the BIOS not doing the right stuff. Jean - To unsubscribe from this list: send the line unsubscribe netdev in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[airo.c bug] Couldn't allocate RX FID / Max tries exceeded when issueing command
hardware: ibm thinkpad t30 kernel: 2.6.18 problem: airo(): Probing for PCI adapters ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 ACPI: PCI Interrupt :02:02.0[A] - Link [LNKC] - GSI 11 (level, low) - IRQ 11 airo(eth1): Found an MPI350 card airo(eth1): Max tries exceeded when issueing command airo(eth1): Couldn't allocate RX FID airo(eth1): Could not map memory airo(): Finished probing for PCI adapters Any ideas? 1) Firmware upgrade/downgrade? (How?) 2) Command sequence to better reset the card? Documentation? My complete dmesg log (at loglevel=8) follows. TIA. Linux version 2.6.18 ([EMAIL PROTECTED]) (gcc version 4.1.2 20060901 (prerelease) (Debian 4.1.1-13)) #10 PREEMPT Wed Nov 1 21:15:56 EST 2006 BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000d2000 - 000d4000 (reserved) BIOS-e820: 000dc000 - 0010 (reserved) BIOS-e820: 0010 - 0ff6 (usable) BIOS-e820: 0ff6 - 0ff7a000 (ACPI data) BIOS-e820: 0ff7a000 - 0ff7c000 (ACPI NVS) BIOS-e820: 0ff7c000 - 1000 (reserved) BIOS-e820: ff80 - 0001 (reserved) 255MB LOWMEM available. On node 0 totalpages: 65376 DMA zone: 4096 pages, LIFO batch:0 Normal zone: 61280 pages, LIFO batch:15 DMI present. ACPI: RSDP (v002 IBM ) @ 0x000f7010 ACPI: XSDT (v001 IBMTP-1I0x2010 LTP 0x) @ 0x0ff6f3a8 ACPI: FADT (v001 IBMTP-1I0x2010 IBM 0x0001) @ 0x0ff6f3f4 ACPI: SSDT (v001 IBMTP-1I0x2010 MSFT 0x010d) @ 0x0ff6f4a8 ACPI: ECDT (v001 IBMTP-1I0x2010 IBM 0x0001) @ 0x0ff79f55 ACPI: TCPA (v001 IBMTP-1I0x2010 PTL 0x0001) @ 0x0ff79fa6 ACPI: BOOT (v001 IBMTP-1I0x2010 LTP 0x0001) @ 0x0ff79fd8 ACPI: DSDT (v001 IBMTP-1I0x2010 MSFT 0x010d) @ 0x ACPI: PM-Timer IO Port: 0x1008 Allocating PCI resources starting at 2000 (gap: 1000:ef80) Detected 1794.240 MHz processor. Built 1 zonelists. Total pages: 65376 Kernel command line: root=/dev/hda1 video=radeonfb:1400x1050 resume=/dev/hda2 loglevel=8 Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 1024 (order: 10, 4096 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 251508k/261504k available (3644k kernel code, 9564k reserved, 2105k data, 196k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 3590.11 BogoMIPS (lpj=1795059) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: After generic identify, caps: 3febf9ff CPU: After vendor identify, caps: 3febf9ff CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K CPU: After all inits, caps: 3febf9ff 0080 Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU0: Intel P4/Xeon Extended MCE MSRs (12) available CPU: Intel(R) Pentium(R) 4 Mobile CPU 1.80GHz stepping 04 Checking 'hlt' instruction... OK. ACPI: Core revision 20060707 ACPI: setting ELCR to 0200 (from 0800) PM: Adding info for No Bus:platform NET: Registered protocol family 16 ACPI: ACPI Dock Station Driver ACPI: bus type pci registered PCI: PCI BIOS revision 2.10 entry at 0xfd8fe, last bus=8 PCI: Using configuration type 1 Setting up standard PCI resources ACPI: Found ECDT ACPI: Could not use ECDT ACPI Error (evregion-0317): No handler for Region [ECOR] (cff4e72c) [EmbeddedControl] [20060707] ACPI Error (exfldio-0290): Region EmbeddedControl(3) has no handler [20060707] ACPI Exception (dswexec-0458): AE_NOT_EXIST, While resolving operands for [OpcodeName unavailable] [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC_.FDC_._INI] (Node cff5a888), AE_NOT_EXIST ACPI Error (evregion-0317): No handler for Region [ECOR] (cff4e72c) [EmbeddedControl] [20060707] ACPI Error (exfldio-0290): Region EmbeddedControl(3) has no handler [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.LPC_.EC__._INI] (Node cff56b6c), AE_NOT_EXIST ACPI: Interpreter enabled ACPI: Using PIC for interrupt routing PM: Adding info for acpi:acpi ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 9 10
