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: (...) > > $ uname -a > Linux s2 3.9.4-301.local.fc19.i686 > > I have just made a clean boot (as in, this has not happened after a > resume for suspend or hibernation). > > May it be related to the patch? Or may heavy IO with out-of-tree CPU > scheduler BFS and out-of-tree IO scheduler BFQ be responsible for the > warnings? I also got a SYSASSERT: [Jun 9 10:35] iwl3945 0000:02:00.0: Read idx for DMA queue txq_id (2) idx 186 is out of range [0-256] 186 186 (...) [ +0,000164] iwl3945 0000:02:00.0: Read idx for DMA queue txq_id (2) idx 185 is out of range [0-256] 186 186 [Jun 9 10:36] iwl3945 0000:02:00.0: Microcode SW error detected. Restarting 0x82000008. [ +0,000008] iwl3945 0000:02:00.0: Loaded firmware version: 15.32.2.9 [ +0,000034] iwl3945 0000:02:00.0: Start IWL Error Log Dump: [ +0,000004] iwl3945 0000:02:00.0: Status: 0x000302E4, count: 1 [ +0,000004] iwl3945 0000:02:00.0: Desc Time asrtPC blink2 ilink1 nmiPC Line [ +0,000224] iwl3945 0000:02:00.0: SYSASSERT (0x5) 0228106348 0x008B6 0x0035E 0x0031C 0x00000 267 [ +0,000010] iwl3945 0000:02:00.0: Error Reply type 0x00000001 cmd UNKNOWN (0xFC) seq 0x2099 ser 0x00FC0000 [ +0,000466] iwl3945 0000:02:00.0: Can't stop Rx DMA. [ +0,001647] ieee80211 phy0: Hardware restart was requested [Jun 9 10:38] iwl3945 0000:02:00.0: Read idx for DMA queue txq_id (2) idx 186 is out of range [0-256] 186 186 (...) I disabled powersave (but kept running the same kernel) and none of the errors appeared again. -- 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
