From: Kalle Valo <kvalo@codeaurora.org>
To: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Anthony Wong <anthony.wong@canonical.com>,
ath10k@lists.infradead.org
Subject: Re: Ath10k on XPS 9380 regularly disconnects
Date: Thu, 21 Mar 2019 19:05:59 +0200 [thread overview]
Message-ID: <87pnqknonc.fsf@codeaurora.org> (raw)
In-Reply-To: <042C2903-585B-47BA-8657-8819D225EEA8@canonical.com> (Kai-Heng Feng's message of "Tue, 19 Mar 2019 13:35:07 +0800")
+ ath10k list
- netdev & linux-kernel
Kai-Heng Feng <kai.heng.feng@canonical.com> writes:
> There’s an issue that ath10k disconnects at regular basis [1], on
> Linux kernel 4.18.
>
> Unfortunately I can’t reproduce the issue on XPS 9380 at my hand.
>
> Is there already a fix in upstream kernel?
I'm not aware of any fixes related to this. Is this a regression? In
other words, is there a known version of ath10k or firmware which didn't
have this problem?
> [1] https://bugs.launchpad.net/bugs/1818881
Relevant information from dmesg:
[ 19.346810] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[ 19.346812] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 19.347136] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00132-QCARMSWP-1 api 6 features wowlan,ignore-otp,mfp crc32 79f4db86
[...]
[77451.338339] WARNING: CPU: 4 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
[...]
[81254.857667] WARNING: CPU: 1 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
[...]
[81390.186167] WARNING: CPU: 2 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
--
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: Kai-Heng Feng <kai.heng.feng@canonical.com>
Cc: Anthony Wong <anthony.wong@canonical.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: Re: Ath10k on XPS 9380 regularly disconnects
Date: Thu, 21 Mar 2019 19:05:59 +0200 [thread overview]
Message-ID: <87pnqknonc.fsf@codeaurora.org> (raw)
In-Reply-To: <042C2903-585B-47BA-8657-8819D225EEA8@canonical.com> (Kai-Heng Feng's message of "Tue, 19 Mar 2019 13:35:07 +0800")
+ ath10k list
- netdev & linux-kernel
Kai-Heng Feng <kai.heng.feng@canonical.com> writes:
> There’s an issue that ath10k disconnects at regular basis [1], on
> Linux kernel 4.18.
>
> Unfortunately I can’t reproduce the issue on XPS 9380 at my hand.
>
> Is there already a fix in upstream kernel?
I'm not aware of any fixes related to this. Is this a regression? In
other words, is there a known version of ath10k or firmware which didn't
have this problem?
> [1] https://bugs.launchpad.net/bugs/1818881
Relevant information from dmesg:
[ 19.346810] ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
[ 19.346812] ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 19.347136] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00132-QCARMSWP-1 api 6 features wowlan,ignore-otp,mfp crc32 79f4db86
[...]
[77451.338339] WARNING: CPU: 4 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
[...]
[81254.857667] WARNING: CPU: 1 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
[...]
[81390.186167] WARNING: CPU: 2 PID: 0 at /build/linux-hwe-9KJ07q/linux-hwe-4.18.0/drivers/net/wireless/ath/ath10k/htt_rx.c:46 ath10k_htt_rx_pop_paddr.isra.29+0xd9/0xf0 [ath10k_core]
--
Kalle Valo
next prev parent reply other threads:[~2019-03-21 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 5:35 Ath10k on XPS 9380 regularly disconnects Kai-Heng Feng
2019-03-21 17:05 ` Kalle Valo [this message]
2019-03-21 17:05 ` Kalle Valo
2019-03-22 15:43 ` Kai-Heng Feng
2019-03-22 15:43 ` Kai-Heng Feng
2019-04-01 8:03 ` Kai-Heng Feng
2019-04-01 8:03 ` Kai-Heng Feng
2019-04-01 8:37 ` Kalle Valo
2019-04-01 8:37 ` Kalle Valo
2019-04-01 9:10 ` Kai-Heng Feng
2019-04-01 9:10 ` Kai-Heng Feng
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=87pnqknonc.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=anthony.wong@canonical.com \
--cc=ath10k@lists.infradead.org \
--cc=kai.heng.feng@canonical.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 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.