From: Kalle Valo <kvalo@codeaurora.org>
To: Mark Herbert <mark.herbert42@gmail.com>
Cc: ath11k@lists.infradead.org
Subject: Re: Can not unload ath11k_pci and load it back
Date: Thu, 07 Oct 2021 09:22:49 +0300 [thread overview]
Message-ID: <875yu9e4li.fsf@codeaurora.org> (raw)
In-Reply-To: <190a1b14-0a8c-f1fb-9f0d-e25cc57034a7@gmail.com> (Mark Herbert's message of "Tue, 5 Oct 2021 22:32:43 +0300")
Mark Herbert <mark.herbert42@gmail.com> writes:
> Dear ath11k team,
>
> The main issue is I can not hibernate and wake up my XPS 13 9310. If
> I keep module loaded it hibernate. Bu hangs on resume.
Just to avoid confusions with terminology, with hibernate you mean
storing the system state to a disk and completely powering off the
laptop?
I assume hibernation fails because ath11k keeps the firmware running
during suspend and ath11k is not able to recover if the firmware is dead
during resume.
Can you file a bug about this, instructions here:
https://wireless.wiki.kernel.org/en/users/drivers/ath11k/bugreport
> If I unload module - it resumes OK but there is no chance to have WIFI
> back without reboot.
>
> If I do rmmod ath11k_pci - it shows errors in dmesg:
>
> [ 48.801504] ath11k_pci 0000:72:00.0: link down error during global reset
> [ 48.801700] DMAR: DRHD: handling fault status reg 2
> [ 48.801709] DMAR: [INTR-REMAP] Request device [0x72:0x00.0] fault
> index 0x60 [fault reason 0x22] Present field in the IRTE entry is
> clear
>
> If I do modprobe immediately it does load module but card will not
> come back again.
>
> In Arch wiki reloading modules was explained as a workaround to
> suspend-resume 9310, but looks like it does not work anymore. Suspend
> to idle works fine - no module unloading needed.
I have an XPS 13 9310 as well but I can't test this right now. Can you
provide more information about the card not getting back after modprobe?
What exact kernel and BIOS versions are you using? What log messages you
get from ath11k? Preferably the exact commands you use and the output
you get from ath11k would help a lot to understand what's happening.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2021-10-07 6:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 19:32 Can not unload ath11k_pci and load it back Mark Herbert
2021-10-07 6:22 ` Kalle Valo [this message]
2021-10-07 7:31 ` Mark Herbert
2021-10-07 7:48 ` Kalle Valo
2021-10-07 8:00 ` Mark Herbert
2021-10-07 8:51 ` Mark Herbert
2021-10-08 13:28 ` Mark Herbert
2021-10-24 5:22 ` Mark Herbert
2021-10-30 19:23 ` Mark Herbert
2021-10-07 7:35 ` Mark Herbert
-- strict thread matches above, loose matches on Subject: below --
2021-10-31 7:43 Mark Herbert
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=875yu9e4li.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=mark.herbert42@gmail.com \
/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