From: Kalle Valo <kvalo@codeaurora.org>
To: Gabriel C <nix.or.die@gmail.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: Re: Warning at drivers/net/wireless/ath/ath10k/mac.c:5625 ath10k_bss_info_changed
Date: Mon, 04 Mar 2019 13:59:03 +0200 [thread overview]
Message-ID: <874l8ic0l4.fsf@codeaurora.org> (raw)
In-Reply-To: <CAEJqkggKGTn0ojWzuYGfoYehDnOf=je5L-7-M1kWogutPGMg3g@mail.gmail.com> (Gabriel C.'s message of "Mon, 4 Mar 2019 12:47:40 +0100")
Gabriel C <nix.or.die@gmail.com> writes:
> Am Mo., 4. März 2019 um 12:28 Uhr schrieb Paul Menzel <pmenzel@molgen.mpg.de>:
>
>> Resuming from ACPI S3 on the Dell XPS 13 9370 with Debian Sid/unstable,
>> Linux 4.19.20 showed the warning below. It’s not reproducible.
[...]
>> [ 3018.992916] Call Trace:
>> [ 3018.992921] ? ath10k_conf_tx+0x7a/0x4b0 [ath10k_core]
>> [ 3018.992937] ieee80211_bss_info_change_notify+0xab/0x1a0 [mac80211]
>> [ 3018.992946] ieee80211_reconfig+0x661/0x12a0 [mac80211]
>> [ 3018.992962] wiphy_resume+0x7f/0x120 [cfg80211]
>> [ 3018.992969] ? wiphy_suspend+0x270/0x270 [cfg80211]
>> [ 3018.992971] dpm_run_callback+0x59/0x150
>> [ 3018.992972] device_resume+0x97/0x190
>> [ 3018.992973] async_resume+0x19/0x30
>> [ 3018.992974] async_run_entry_fn+0x39/0x160
>> [ 3018.992976] process_one_work+0x1a7/0x3a0
>> [ 3018.992978] worker_thread+0x30/0x390
>> [ 3018.992979] ? pwq_unbound_release_workfn+0xd0/0xd0
>> [ 3018.992980] kthread+0x112/0x130
>> [ 3018.992981] ? kthread_bind+0x30/0x30
>> [ 3018.992983] ret_from_fork+0x35/0x40
>> [ 3018.992984] ---[ end trace 3af618ca97bd4a0a ]---
>> ```
>>
>> Please find all Linux messages attached.
>
> I reported that twice and no one seems to care about.
>
> http://lists.infradead.org/pipermail/ath10k/2018-November/012398.html
> http://lists.infradead.org/pipermail/ath10k/2018-December/012658.html
Does this patch help:
ath10k: Drop WARN_ON()s that always trigger during system resume
https://patchwork.kernel.org/patch/10837139/
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Gabriel C <nix.or.die@gmail.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
ath10k@lists.infradead.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Warning at drivers/net/wireless/ath/ath10k/mac.c:5625 ath10k_bss_info_changed
Date: Mon, 04 Mar 2019 13:59:03 +0200 [thread overview]
Message-ID: <874l8ic0l4.fsf@codeaurora.org> (raw)
In-Reply-To: <CAEJqkggKGTn0ojWzuYGfoYehDnOf=je5L-7-M1kWogutPGMg3g@mail.gmail.com> (Gabriel C.'s message of "Mon, 4 Mar 2019 12:47:40 +0100")
Gabriel C <nix.or.die@gmail.com> writes:
> Am Mo., 4. März 2019 um 12:28 Uhr schrieb Paul Menzel <pmenzel@molgen.mpg.de>:
>
>> Resuming from ACPI S3 on the Dell XPS 13 9370 with Debian Sid/unstable,
>> Linux 4.19.20 showed the warning below. It’s not reproducible.
[...]
>> [ 3018.992916] Call Trace:
>> [ 3018.992921] ? ath10k_conf_tx+0x7a/0x4b0 [ath10k_core]
>> [ 3018.992937] ieee80211_bss_info_change_notify+0xab/0x1a0 [mac80211]
>> [ 3018.992946] ieee80211_reconfig+0x661/0x12a0 [mac80211]
>> [ 3018.992962] wiphy_resume+0x7f/0x120 [cfg80211]
>> [ 3018.992969] ? wiphy_suspend+0x270/0x270 [cfg80211]
>> [ 3018.992971] dpm_run_callback+0x59/0x150
>> [ 3018.992972] device_resume+0x97/0x190
>> [ 3018.992973] async_resume+0x19/0x30
>> [ 3018.992974] async_run_entry_fn+0x39/0x160
>> [ 3018.992976] process_one_work+0x1a7/0x3a0
>> [ 3018.992978] worker_thread+0x30/0x390
>> [ 3018.992979] ? pwq_unbound_release_workfn+0xd0/0xd0
>> [ 3018.992980] kthread+0x112/0x130
>> [ 3018.992981] ? kthread_bind+0x30/0x30
>> [ 3018.992983] ret_from_fork+0x35/0x40
>> [ 3018.992984] ---[ end trace 3af618ca97bd4a0a ]---
>> ```
>>
>> Please find all Linux messages attached.
>
> I reported that twice and no one seems to care about.
>
> http://lists.infradead.org/pipermail/ath10k/2018-November/012398.html
> http://lists.infradead.org/pipermail/ath10k/2018-December/012658.html
Does this patch help:
ath10k: Drop WARN_ON()s that always trigger during system resume
https://patchwork.kernel.org/patch/10837139/
--
Kalle Valo
next prev parent reply other threads:[~2019-03-04 11:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 11:27 Warning at drivers/net/wireless/ath/ath10k/mac.c:5625 ath10k_bss_info_changed Paul Menzel
2019-03-04 11:27 ` Paul Menzel
2019-03-04 11:47 ` Gabriel C
2019-03-04 11:47 ` Gabriel C
2019-03-04 11:59 ` Kalle Valo [this message]
2019-03-04 11:59 ` Kalle Valo
2019-03-04 13:00 ` Gabriel C
2019-03-04 13:00 ` Gabriel C
2019-03-08 10:58 ` Kalle Valo
2019-03-08 10:58 ` Kalle Valo
2019-03-25 16:49 ` Brian Norris
2019-03-25 16:49 ` Brian Norris
2019-03-26 3:46 ` Claire Chang
2019-03-26 3:46 ` Claire Chang
2019-04-02 23:01 ` Brian Norris
2019-04-02 23:01 ` Brian Norris
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=874l8ic0l4.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@gmail.com \
--cc=pmenzel@molgen.mpg.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.