From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Pedro Francisco <pedrogfrancisco@gmail.com>
Cc: Tino Keitel <tino.keitel@tikei.de>,
ML linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Power saving features for iwl4965
Date: Tue, 11 Jun 2013 18:19:24 +0200 [thread overview]
Message-ID: <20130611161924.GB1696@redhat.com> (raw)
In-Reply-To: <CAJZjf_xGdvStOG0=FR2+2WsVcjyizQukH+RxysZf8f9-Tk9L9w@mail.gmail.com>
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@gmail.com> wrote:
> > On Mon, Jun 3, 2013 at 3:18 PM, Stanislaw Gruszka <sgruszka@redhat.com> 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.
Yes, this seems to be iwlegacy PS issue and has to be fixed before
this patch could be applied.
Thanks for testing.
Stanislaw
next prev parent reply other threads:[~2013-06-11 16:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 20:35 Power saving features for iwl4965 Tino Keitel
2012-04-19 14:25 ` Johannes Berg
2012-04-19 18:50 ` tino
2012-04-25 12:25 ` Stanislaw Gruszka
2012-05-03 18:28 ` Tino Keitel
2012-12-26 18:54 ` Tino Keitel
2013-01-07 11:08 ` Stanislaw Gruszka
2013-01-08 1:48 ` Pedro Francisco
2013-01-08 8:47 ` Stanislaw Gruszka
2013-06-03 8:52 ` Tino Keitel
2013-06-03 14:18 ` Stanislaw Gruszka
2013-06-09 0:28 ` Pedro Francisco
2013-06-10 19:31 ` Pedro Francisco
2013-06-11 16:19 ` Stanislaw Gruszka [this message]
2013-06-11 18:55 ` Tino Keitel
2013-06-14 12:50 ` Pedro Francisco
2013-06-14 13:18 ` Stanislaw Gruszka
2013-06-25 14:25 ` Stanislaw Gruszka
2013-07-11 21:02 ` Pedro Francisco
2013-07-16 10:27 ` Stanislaw Gruszka
2013-07-16 11:02 ` Pedro Francisco
2013-07-17 11:48 ` Pedro Francisco
2013-07-31 12:08 ` Stanislaw Gruszka
2013-08-04 14:24 ` Pedro Francisco
2013-08-04 14:53 ` Pedro Francisco
2013-10-17 9:06 ` Stanislaw Gruszka
2013-10-17 13:32 ` Stanislaw Gruszka
2013-06-11 18:51 ` Tino Keitel
2014-02-18 10:57 ` Stanislaw Gruszka
2014-02-18 11:32 ` Emmanuel Grumbach
2014-02-18 11:59 ` Stanislaw Gruszka
2014-02-20 12:08 ` Pedro Francisco
2014-02-25 16:16 ` Pedro Francisco
-- strict thread matches above, loose matches on Subject: below --
2012-10-01 16:06 Tino Keitel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130611161924.GB1696@redhat.com \
--to=sgruszka@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pedrogfrancisco@gmail.com \
--cc=tino.keitel@tikei.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).