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, 16 Jul 2013 12:27:44 +0200 [thread overview]
Message-ID: <20130716102743.GA8321@redhat.com> (raw)
In-Reply-To: <CAJZjf_z=+QW_Y3yuz6nJ+muVA_6bGRut8EQ7fCopDqqj2Fn9Yw@mail.gmail.com>
On Thu, Jul 11, 2013 at 10:02:22PM +0100, Pedro Francisco wrote:
> > Pedro, please do the fallowing:
> >
> > Add this line in /etc/rsyslog.conf:
> > kern.* /var/log/kernel
> >
> > Restart rsyslog services:
> > # systemctl restart rsyslog.service
> >
> > Restart iwl3945 module with verbose debug enabled:
> > modprobe -r iwl3945
> > modprobe iwl3945 debug=0x47ffffff
> >
> > Reproduce the problem.
> >
> > Unload module:
> > modprobe -r iwl3945
> >
> > Then provide me generated /var/log/kernel file (compressed if needed).
>
> I seem only to be able to trigger it with disable_hw_scan=0, I need
> further testing with disable_hw_scan=1 (I use disable_hw_scan=0
> because it prevents me from getting disconnected from eduroam Cisco
> APs -- haven't tested disable_hw_scan=0 since the VOIP-friendly SW
> scanning patch, however).
>
> Do you want the log anyway? (modprobe iwl3945 debug=0x47ffffff
> disable_hw_scan=0 and runtime PCI powersave also enabled -- I don't
> know if it matters).
To test that patch powersave has to be explicitly enabled, since
it is disabled by default.
As this is not causing troubles with default disable_hw_scan option,
I'll post that patch.
You can provide me logs with disable_hw_scan=0, if you manage to
trigger a Microcode error.
Thanks
Stanislaw
> --
> Pedro
next prev parent reply other threads:[~2013-07-16 10:24 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
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 [this message]
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=20130716102743.GA8321@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.