On Wed, 2020-09-23 at 11:16 +0300, Luciano Coelho wrote: > On Thu, 2020-09-17 at 03:01 +0530, Krishna Chaitanya wrote: > > On Sat, Sep 12, 2020 at 12:56 AM Krishna Chaitanya > > <chaitanya.mgit@xxxxxxxxx> wrote: > > > On Fri, Sep 11, 2020 at 10:41 PM Johannes Berg > > > <johannes@xxxxxxxxxxxxxxxx> wrote: > > > > On Fri, 2020-09-11 at 20:37 +0530, Krishna Chaitanya wrote: > > > > > > > > > > [ 228.315290] iwlwifi 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT > > > > > > [ 228.315294] iwlwifi 0000:03:00.0: 0x00A0A200 | trm_hw_status0 > > > > > > [ 228.315297] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1 > > > > > > [ 228.315300] iwlwifi 0000:03:00.0: 0x004F8E3C | branchlink2 > > > > > > [ 228.315303] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink1 > > > > > > [ 228.315307] iwlwifi 0000:03:00.0: 0x004E4FF4 | interruptlink2 > > > > > > [ 228.315310] iwlwifi 0000:03:00.0: 0x07000101 | data1 > > > > > > [ 228.315313] iwlwifi 0000:03:00.0: 0x48308403 | data2 > > > > > > [ 228.315316] iwlwifi 0000:03:00.0: 0x00000005 | data3 > > > > > > > > This means that we got an invalid TX rate, notably an HE rate was > > > > requested/configured on a MAC configuration that didn't have HE. > > > > > > > > I think I saw some patches in this area (configuring the MAC to be HE) > > > > fly by internally recently, but not sure... Luca probably knows. > > > Ah okay. This was reported on 5.4 kernel, do you think is it worth > > > trying on latest iwlwifi-next tree? Or as you are referring to the internal tree > > > the issue is present in the latest as well? > > Hi Luca, > > > > Can you please take a look? Any help is appreciated. > > Hi, > > There have been some new patches in this area, but after a quick look I > didn't find anything specific that jumps out. I'll take a closer look > and let you know if I find anything. In the meantime, you could try our public backport-iwlwifi tree, where most of the internal tree is published: https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/ This is an out-of-tree driver, based on the linux-backports project. You could try the core56 branch, for instance, or even master and check if the problem is still there. If not, we can try to look for the patch that fixes it and push it to stable. -- Cheers, Luca.
