unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: help-guix@gnu.org
Subject: Re: ath wireless power management failure
Date: Tue, 7 Feb 2017 22:39:28 +0100	[thread overview]
Message-ID: <20170207223928.40e04367@alma-ubu> (raw)
In-Reply-To: <87h9461ko4.fsf@elephly.net>

Hi Ricardo,

On Sun 05 Feb 2017 04:43:26 AM CET
Ricardo Wurmus <rekado@elephly.net> wrote:

> GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> https://elephly.net
> Hi Guix,
> 
> since a couple of days I’m experiencing problems with my wireless card
> after waking up from suspend.  I suspend the laptop very often, so
> this is really important to me.
> 
> Upon waking up from suspend the wireless card cannot be initialised
> any more.  This results in a constant stream of error messages, which
> can be seen in dmesg.  The messages disappear when unloading all
> ath-related kernel modules.  Reloading the modules does not return
> the network card to a workable state, so I have to reboot if I want
> to connect to a wireless network (and I usually want to do that).
> 
> The error messages that appear in the log look like this:
> 
> --8<---------------cut here---------------start------------->8---
> [ 1210.998408] ath: phy0: Unable to reset channel, reset status -22
> [ 1211.078027] ath: phy0: DMA failed to stop in 10 ms
> AR_CR=0xffffffff AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
> [ 1211.078038] ath: phy0: Could not stop RX, we could be confusing
> the DMA engine when we start RX up --8<---------------cut
> here---------------end--------------->8---
> 
> (Repeat ad infinitum.)
> 
> According to ancient bug reports these messages relate to power
> management problems and have been reported as fixed a long time ago.
> I confirmed with “iw” and “iwconfig” that power management for my WiFi
> card is in fact disabled (I didn’t do this myself).
> 
> I see these errors with linux-libre-4.1 and linux-libre.  I’m using
> a somewhat dated Libreboot (planning to upgrade *after* FOSDEM to be
> sure that my machine is usable for the presentation).
> 
> Has anyone else experienced the same behaviour?  Any ideas how to fix
> this?  Does this just mean that my WiFi card is dying?

Just curious:

Is you operating system GuixSD? Do you still have an old system generation of
the time "where it worked"? Have you tried to boot into that?

Björn

  parent reply	other threads:[~2017-02-07 21:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-05  3:43 ath wireless power management failure Ricardo Wurmus
2017-02-07 14:46 ` Ludovic Courtès
2017-02-07 15:22   ` Tiberiu
2017-02-07 15:30     ` Ricardo Wurmus
2017-02-07 15:36       ` Tiberiu
2017-02-07 16:03         ` Ricardo Wurmus
2017-02-07 16:17           ` Tiberiu
2017-02-17  9:24             ` Ricardo Wurmus
2017-02-07 21:39 ` Björn Höfling [this message]
2017-02-07 22:05   ` Ricardo Wurmus

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170207223928.40e04367@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).