linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: korgman <korgie@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwl3945 bug report (occasionally crashing after suspend)
Date: Sat, 18 Mar 2017 09:28:24 +0100	[thread overview]
Message-ID: <20170318082823.GA7356@redhat.com> (raw)
In-Reply-To: <7ae0bf4f-6ea2-1a4c-2e6d-e793cf800c4a@gmail.com>

On Thu, Mar 16, 2017 at 04:26:10PM +0200, korgman wrote:
> Hello there,
> 
> I have the same problem as reported here.
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627828
> 
> and here
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629603

This could be caused by power save, which is disable by default
in the driver but some programs/distribution seems to enable
it without user knowlage. First check: 

$ iw dev wlan0 get power_save

and if PS is enabled, disable by:

$ iw dev wlan0 set power_save off

and check if problem still happen.

> If I understood correctly (form 2nd link) the latest good kernel was 4.4.4 after 4.4.6 we have the problem. (see message #5)
> 
> I quote:
> "Not a full bisection yet but I have narrowed it down:
> 
> I looked at all kernel versions that had changes committed to iwlwifi and tested between them.
> 
> I now have determined that I do not have this issue in the kernel version 4.4.4.
> 
> I do have the issue in 4.4.6 and that is the next kernel version that has changes to iwlwifi so I guess that is the first bad version."

This does not make sense as 3945 device is handled by
iwl3495 (iwlegacy) driver, not by iwlwifi.

Stanislaw

      reply	other threads:[~2017-03-18  8:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 14:26 iwl3945 bug report (occasionally crashing after suspend) korgman
2017-03-18  8:28 ` Stanislaw Gruszka [this message]

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=20170318082823.GA7356@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=korgie@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    /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).