On Tue, Jun 11, 2013 at 5:19 PM, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: > On Mon, Jun 10, 2013 at 08:31:33PM +0100, Pedro Francisco wrote: >> On Sun, Jun 9, 2013 at 1:28 AM, Pedro Francisco >> <pedrogfrancisco@xxxxxxxxx> wrote: >> > On Mon, Jun 3, 2013 at 3:18 PM, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: >> >> On Mon, Jun 03, 2013 at 10:52:39AM +0200, Tino Keitel wrote: >> >>> (...) >> >>> It would be really nice to have proper power management in a current >> >>> kernel, as the laptop gets noticeably hotter with the current iwlegacy >> >>> driver. That's why I still use a 3.1.10 kernel with an old >> >>> forward-ported iwlagn driver. >> >> >> >> 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... 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. P.S.: the demise of bugzilla.intellinuxwireless.org it's very difficult to find useful info about this. It would appear 4465 is just affected after suspend, believing the patch which disabled PS in 2009. -- 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
