From: Vincent Danjean <vdanjean@debian.org>
To: James <bjlockie@lockie.ca>, linux-wireless@vger.kernel.org
Subject: Re: Bug report about ath9k
Date: Wed, 5 Apr 2023 13:59:21 +0200 [thread overview]
Message-ID: <d055fe8e-0bf7-7e6d-4404-382697753a66@debian.org> (raw)
In-Reply-To: <f3039ab6-25f4-d003-059a-c0a75aa24127@lockie.ca>
Hi,
Le 22/02/2023 à 01:32, James a écrit :
> Try disabling power saving.
> w dev wlanX set power_save off
> Maybe that command.
For the record, this did not change anything. The problem seemed
triggered by an external event : no log during the week I was not at
home (but the server was still online and used for regular backup,
asterisk, etc. with a few domotic object still connected via wifi)
However, when present, I saw an error just after midnight nearly
all days (with some few exceptions) and sometimes at other
times (5 PM, 8 AM, etc.)
I did not succeeded at finding the external cause. But I "fixed"
the problem by adding the "iommu=pt" kernel parameter.
As I'm using the network card on the host, if I'm correct, this
parameter just tells linux to *not* use iommu for this device in
this case.
So, I think that the ath9k has a bug wrt iommu. If you ever want
I tried some things (debug, new versions, etc.), I can do it.
Just tell me.
I did not tried to manager the device in a VM (that would
require the use of iommu for this device)
Regards
Vincent
prev parent reply other threads:[~2023-04-05 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:20 Bug report about ath9k Vincent Danjean
2023-02-22 0:32 ` James
2023-02-22 0:33 ` James
2023-04-05 11:59 ` Vincent Danjean [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=d055fe8e-0bf7-7e6d-4404-382697753a66@debian.org \
--to=vdanjean@debian.org \
--cc=bjlockie@lockie.ca \
--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