On Fri, Jun 14, 2013 at 01:50:58PM +0100, Pedro Francisco wrote: > >> >> Could you try this experimental patch? (...) > >> > > >> > I am trying the iwlegacy powersave patch along with CPU scheduler BFS > >> > and IO scheduler BFQ. > >> > > >> > I've got this today: (...) > >> > > >> > (...) > >> I also got a SYSASSERT: > >> (...) > >> > >> I disabled powersave (but kept running the same kernel) and none of > >> the errors appeared again. > > > > Yes, this seems to be iwlegacy PS issue and has to be fixed before > > this patch could be applied. > > But is it a driver-only issue? I had assumed it was some sort of > fireware+driver issue... Looks like driver issue or firmware issue that can be workaround in the driver. > Will running with debug on help? Or is it easily reproducible on any > iwl3945 / iwl4465 ? > > Because in my case (iwl3945) it happens after boot, no prior suspend > to RAM is required to trigger the issues. I can reproduce microcode error on iwl4965 by reloading modules. Looks like we put device in sleep mode and it can not be properly booted when driver initalize. I did not yet test patch on iwl3945. When I'll do this, I think I'll be able to reproduce problems you discovered. If not I'll ask for more debug info. Thanks Stanislaw -- 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
