[have to re-open this issue again] On 21.10.2012 16:16, Andrei Emeltchenko wrote: > I have the same board and see this problem sometimes. Reloading modules > might help, if not reboot always works :). I thought I solved this issue, but I can't reproduce the running version anymore unfortunately. It constantly fails with the error I described, even though the clock and all voltages etc are definitely stable. I can also rule out hardware issues as the BSP kernel (3.2.18) works just fine with the same setup including the firmware image. Andrei, may I ask which board you have exactly? What kernel version are you based on? I wonder if the firmware is actually transferred correctly, or which reason there could be for it not to start up. Could that be related to the recent AM33xx/omap_hsmmc DMA reworks? [copied Matt] Bing, FWIW here are some more complete logs with CONFIG_MMC_DEBUG=y. This is the detection of the SDIO card: http://pastebin.com/h9VDaExh And this is what happens after "modprobe mwifiex_sdio": http://pastebin.com/w5bcz6Aa (part 1/2) http://pastebin.com/G5wfnPrg (part 2/2) Can anyone see what's wrong here? Thanks again, Daniel > 18.10.2012 18:09 пользователь "Daniel Mack" <zonque@xxxxxxxxx > <mailto:zonque@xxxxxxxxx>> написал: >> >> Hi Bing, >> >> thanks for your time. >> >> On 18.10.2012 02:20, Bing Zhao wrote: >> >> we're trying to get a SD8787 to play which is connected via SDIO to an >> >> OMAP hsmmc (AM33xx hardware). This fails with the following message: >> >> >> >> # modprobe mwifiex_sdio >> >> [ 13.984779] [sched_delayed] sched: RT throttling activated >> >> [ 22.401700] mwifiex_sdio mmc0:0001:1: FW failed to be active in time >> >> >> >> The firmware sd8787_uapsta.bin was taken from the > linux-firmware.git and >> >> apparently is transferred successfully, but then consequently fails to >> >> do start up. When compiled with CONFIG_MMC_CONFIG=y, tons of successful >> >> messages are logged like this: >> >> >> >> [ 2607.867660] mmc0: starting CMD52 arg 00000a00 flags 00000195 >> >> [ 2607.867713] mmc0: req done (CMD52): 0: 00001000 00000000 00000000 >> >> 00000000 >> >> [ 2607.883273] mmc0: starting CMD52 arg 00000a00 flags 00000195 >> >> [ 2607.883327] mmc0: req done (CMD52): 0: 00001000 00000000 00000000 >> >> 00000000 >> >> [ 2607.898905] mmc0: starting CMD52 arg 00000a00 flags 00000195 >> > >> > It keeps reading Int_Pending (CCCR register 0x05). Perhaps you have > interrupt storm here? >> > Could you please check if your controller clears interrupt properly? >> >> The reason for this issue was a different one: the 32KHz clock was not >> running. I just learned that the firmware download will succeed >> nevertheless, but the firmware won't start. Note to myself: make sure to >> rule out any hardware issue before bordering developers :-/ But that >> posting may be a help to someone with similar issues one day ... >> >> >> The kernel we're based on is Linus' current merge tree (3.7-rc1), but >> >> earlier version (3.6) have shown the same issue. >> >> >> >> Before we start digging into this, I want to ask whether there are any >> >> common pitfalls we should be aware of and that could cause this? >> > >> > You may want to get a newer firmware release from here: >> > >> > http://git.marvell.com/?p=mwifiex-firmware.git;a=summary >> > git://git.marvell.com/mwifiex-firmware.git > <http://git.marvell.com/mwifiex-firmware.git> >> >> Note that contains the same firmware binary than the linux-firmware >> repository. >> >> >> Please let me know whether you need any further information. >> > >> > It might be helpful if you post messages before this line: >> > >> > [ 2607.867660] mmc0: starting CMD52 arg 00000a00 flags 00000195 >> >> >> Thanks again! >> >> Daniel >> >> -- >> To unsubscribe from this list: send the line "unsubscribe > linux-wireless" in >> the body of a message to majordomo@xxxxxxxxxxxxxxx > <mailto:majordomo@xxxxxxxxxxxxxxx> >> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
