mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Kalle Valo <kvalo@kernel.org>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Garry Williams <gtwilliams@gmail.com>
Cc: Linux Atheros 10K <ath10k@lists.infradead.org>,
	Linux Wireless <linux-wireless@vger.kernel.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Fwd: Dell XPS 13 ath10k_pci firmware crashed!
Date: Sat, 24 Jun 2023 08:13:26 +0700	[thread overview]
Message-ID: <0e85ca99-d1d6-097b-2e04-4cd6492098a1@gmail.com> (raw)
In-Reply-To: <2db51694-aa57-cbfd-096e-4925b76232b0@gmail.com>

On 6/14/23 08:15, Bagas Sanjaya wrote:
> Hi,
> 
> I notice a regression report on Bugzilla [1]. Quoting from it:
> 
>> Beginning with kernel 6.2.15-300.fc38.x86_64 and continuing through 6.3.7-200.fc38.x86_64, the wifi connection fails periodically with these log messages:
>>
>> ath10k_pci 0000:02:00.0: firmware crashed! (guid 6c545da0-593c-4a0e-b5ad-3ef2b91cdebf)
>> ath10k_pci 0000:02:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:143a
>> ath10k_pci 0000:02:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
>> ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.4.4.1-00288- api 6 features wowlan,ignore-otp,mfp crc32 bf907c7c
>> ath10k_pci 0000:02:00.0: board_file api 2 bmi_id N/A crc32 d2863f91
>> ath10k_pci 0000:02:00.0: htt-ver 3.87 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
>> ath10k_pci 0000:02:00.0: failed to get memcpy hi address for firmware address 4: -16
>> ath10k_pci 0000:02:00.0: failed to read firmware dump area: -16
>> ath10k_pci 0000:02:00.0: Copy Engine register dump:
>> ath10k_pci 0000:02:00.0: [00]: 0x00034400  12  12   3   3
>> ath10k_pci 0000:02:00.0: [01]: 0x00034800  14  14 347 348
>> ath10k_pci 0000:02:00.0: [02]: 0x00034c00   8   2   0   1
>> ath10k_pci 0000:02:00.0: [03]: 0x00035000  16  15  16  14
>> ath10k_pci 0000:02:00.0: [04]: 0x00035400 2995 2987  22 214
>> ath10k_pci 0000:02:00.0: [05]: 0x00035800   0   0  64   0
>> ath10k_pci 0000:02:00.0: [06]: 0x00035c00   0   0  18  18
>> ath10k_pci 0000:02:00.0: [07]: 0x00036000   1   1   1   0
>> ath10k_pci 0000:02:00.0: could not request stats (-108)
>> ath10k_pci 0000:02:00.0: could not request peer stats info: -108
>> ath10k_pci 0000:02:00.0: failed to read hi_board_data address: -28
>> ieee80211 phy0: Hardware restart was requested
>> ath10k_pci 0000:02:00.0: could not request stats (-108)
>> ath10k_pci 0000:02:00.0: device successfully recovered
>>
>>
>> If I disconnect and reconnect using network manager, the connection is restored.  But this same failure recurs over and over after some few minutes to a few hours.
>>
>> This is a regression.  The error was not reported with any previous kernel since 6.2.14-300.fc38.x86_64
> 
> See Bugzilla for the full thread.
> 
> Unfortunately, the reporter can't bisect this regression (he only tries
> distribution kernels instead).
> 
> Anyway, I'm adding it to regzbot (as mainline regression because v6.2.x
> has already EOL):
> 
> #regzbot introduced: v6.2..v6.3 https://bugzilla.kernel.org/show_bug.cgi?id=217549
> #regzbot title: ath10k_pci firmware crashed on Dell XPS 13
> 

It comes out that the regression is due to Fedora patches (see Bugzilla thread),
thus:

#regzbot invalid: regression caused by downstream patch

Thanks.

-- 
An old man doll... just what I always wanted! - Clara


      reply	other threads:[~2023-06-24  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14  1:15 Bagas Sanjaya
2023-06-24  1:13 ` Bagas Sanjaya [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=0e85ca99-d1d6-097b-2e04-4cd6492098a1@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=ath10k@lists.infradead.org \
    --cc=gtwilliams@gmail.com \
    --cc=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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

all inboxes | Powered by JetHome®