On Tue, 2012-04-03 at 18:26 -0700, Troy Kisky wrote: > On 4/2/2012 1:39 AM, Luciano Coelho wrote: > >>> wl12xx: ERROR watchdog interrupt received! starting recovery. > >>> wl12xx: Reading FW panic log > >>> wl12xx: ERROR command complete timeout > > This is a firmware bug. Can you please take the contents > > of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to > > us so we can take a look at what's going on? > Sorry, it isn't a firmware bug. It was a configuration problem on my > part. The defconfig > file I was using was enabling a TVOUT driver which this board doesn't > have. When > the driver wanted to blank the screen, it was turning off my slow clock > to my WL1271. > > When the WL1271 later becomes idle, it goes into a low power state which > depends upon > slow clock. So please tell your firmware guys, "never mind." Okay, cool that you found the reason for the problem. :) I thought it was a firmware problem because all the symptoms show that the chip stopped responding. :) > >> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923 > > This tells us where the PC was when the crash happened. I'll ask our > > firmware team to analyze this. > "Never mind...." Cool! Now, Gary, do you still have the same (or a similar) problem with your setup? -- Cheers, Luca. -- 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
