[Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on wireless [8086:a0f0]

[Steve Barriault]

Whenever I am using a wireless connection, the image freezes roughly every two minutes. Sometimes, email cannot be retrieved / computer complains the connection was momentarily lost.

- If I am on a wire, this problem does NOT occur.
- This problems occurs on wireless independent of the platform used (behavior seen in both Google Hangout and Zoom)
- This problem does NOT occur on Windows. I did a meeting where both my Linux and Windows machines were connected to the same meeting and using the same wifi router, and while the performance on Windows was flawless, unfortunately it was not so on the Ubuntu box. So I don't think my wifi router or network is to blame.
- As far as I can recall, the problem used not to be there 2 weeks ago. So it may have been introduced by a recent update.
- As communicated before, I am on a certified machine from Dell, recently purchased with Ubuntu already on board from factory (I assume the logs there were sent to you would contain the information).
- I tried to generate a log on the wireless, but the process did not let me do this very easily. I am more than happy to send you additional information - but please let me know which package you want me to spy upon exactly, as I am not sure what would be helpful in this matter.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
Uname: Linux 5.10.0-1029-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 18 09:47:58 2021
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
DistroCodename: focal
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0991]
InstallationDate: Installed on 2021-04-24 (54 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
MachineType: Dell Inc. XPS 13 9310
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1029-oem root=UUID=28dc4511-d4dc-4dec-8abb-64e06b4e9d1e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2021
dmi.bios.release: 2.1
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.1.1
dmi.board.name: 08607K
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr2.1.1:bd03/25/2021:br2.1:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Daniel van Vugt (vanvugt)]

It appears the offending kernel is indeed about two weeks old:

https://launchpad.net/ubuntu/+source/linux-oem-5.10/5.10.0-1029.30

[Alex Tu (alextu)]

pick out some key information:
# the bios vesion is 2.1.1
the bios verison of XPS 9310 in the certification pool is 1.0.1

# from lspci the wifi device is:
00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)
 Subsystem: Bigfoot Networks, Inc. Device [1a56:1651]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at 60531dc000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

# the latest available is 5.10.0-1033
 - https://qa.debian.org/madison.php?package=linux-image-oem-20.04&table=ubuntu&a=&c=&s=#

[Kai-Chuan Hsieh (kchsieh)]

Hello,

I check the log, there are two questions?

1. have you tried to disable ufw? does it help?
2. did you run iperf test to check the wireless throughput?

I found there is a Wi-Fi firmware crash inside the log, but I am not sure if it is the root cause, Generally, the driver should have recovery mechanism after the micorcode crash. There is a newer iwlwifi-QuZ-a0-hr-b0-59.ucode firmware in https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware.git/, would you mind to have it a try?

About the firmware crash:
[105396.990450] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[105396.990539] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[105396.990541] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
[105396.990543] iwlwifi 0000:00:14.3: Loaded firmware version: 55.d9698065.0 QuZ-a0-hr-b0-55.ucode
[105396.990545] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[105396.990547] iwlwifi 0000:00:14.3: 0x000022F0 | trm_hw_status0
[105396.990548] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[105396.990549] iwlwifi 0000:00:14.3: 0x004CA3DE | branchlink2
[105396.990551] iwlwifi 0000:00:14.3: 0x000007F6 | interruptlink1
[105396.990552] iwlwifi 0000:00:14.3: 0x000007F6 | interruptlink2
[105396.990553] iwlwifi 0000:00:14.3: 0x00016504 | data1
[105396.990554] iwlwifi 0000:00:14.3: 0x00001000 | data2
[105396.990555] iwlwifi 0000:00:14.3: 0x00000000 | data3
[105396.990557] iwlwifi 0000:00:14.3: 0x900148E4 | beacon time
[105396.990558] iwlwifi 0000:00:14.3: 0x0C6FF71A | tsf low
[105396.990559] iwlwifi 0000:00:14.3: 0x000001B4 | tsf hi
[105396.990560] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[105396.990562] iwlwifi 0000:00:14.3: 0x58CF3E54 | time gp2
[105396.990563] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[105396.990564] iwlwifi 0000:00:14.3: 0x00000037 | uCode version major
[105396.990565] iwlwifi 0000:00:14.3: 0xD9698065 | uCode version minor
[105396.990567] iwlwifi 0000:00:14.3: 0x00000351 | hw version
[105396.990568] iwlwifi 0000:00:14.3: 0x00C89004 | board version
[105396.990569] iwlwifi 0000:00:14.3: 0x800FFC03 | hcmd
[105396.990570] iwlwifi 0000:00:14.3: 0x00020000 | isr0
[105396.990572] iwlwifi 0000:00:14.3: 0x00400000 | isr1
[105396.990573] iwlwifi 0000:00:14.3: 0x08F00002 | isr2
[105396.990574] iwlwifi 0000:00:14.3: 0x04C338C8 | isr3
[105396.990575] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[105396.990577] iwlwifi 0000:00:14.3: 0x05D6001C | last cmd Id
[105396.990578] iwlwifi 0000:00:14.3: 0x00016504 | wait_event
[105396.990579] iwlwifi 0000:00:14.3: 0x000000C4 | l2p_control
[105396.990580] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
[105396.990582] iwlwifi 0000:00:14.3: 0x00000007 | l2p_mhvalid
[105396.990583] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
[105396.990584] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[105396.990585] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[105396.990586] iwlwifi 0000:00:14.3: 0x0000C0D4 | flow_handler
[105396.990628] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[105396.990629] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
[105396.990631] iwlwifi 0000:00:14.3: 0x2000307C | ADVANCED_SYSASSERT
[105396.990632] iwlwifi 00...

[Steve Barriault (skidooman)]

Hi Kai-chuan:

1. On UFW, I disabled it, but it did not work.

2. For iperf, I did not know this tool existed, and I am not sure how to
generate the right data. Please advise here.

3. I also tried the new ucode file. This is what I did: I cloned the git
repo and copied the file into /usr/lib/firmware. Good news is that after
reboot the Internet connection worked. But I did not have the opportunity
to test this during a meeting yet though.

4. Stéphane Verdy, who you probably know, gave me the "decoding ring". When
Daniel van Vugt said "the kernel is about two weeks old", this newbie had
no idea if this was a good thing. I thought the kernel got updated
automatically - I was probably mistaken. So I updated it manually.

So, interestingly, it solved PART of the problem. When I am in a 1:1
discussion, it works flawlessly on wireless. But if there are multiple
people in the call, then it started having issues again.

Give me a few days here. I have a few calls upcoming, I will give the wifi
a try in different settings (1:1 and multiple folks) and let you know if
(3) + (4) actually did the trick (because on the 1:1, I could only test (4)
in isolation so far).

Best Regards,

Steve

On Thu, Jun 24, 2021 at 12:05 AM Kai-Chuan Hsieh <email address hidden>
wrote:

> ** Changed in: oem-priority
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
>...

[Steve Barriault (skidooman)]

OK Kai-chuan, bad news. I got a 1:1 with Tony and... the freeze is still
there, as present as ever. :(

Please let me know how I can help. If you have the iperf command that would
be useful, please let me know (and if I have to use it during a meeting
when it freezes).

Best Regards,

Steve

Bes

On Thu, Jun 24, 2021 at 2:11 PM Steve Barriault <email address hidden> wrote:

> Hi Kai-chuan:
>
> 1. On UFW, I disabled it, but it did not work.
>
> 2. For iperf, I did not know this tool existed, and I am not sure how to
> generate the right data. Please advise here.
>
> 3. I also tried the new ucode file. This is what I did: I cloned the git
> repo and copied the file into /usr/lib/firmware. Good news is that after
> reboot the Internet connection worked. But I did not have the opportunity
> to test this during a meeting yet though.
>
> 4. Stéphane Verdy, who you probably know, gave me the "decoding ring".
> When Daniel van Vugt said "the kernel is about two weeks old", this newbie
> had no idea if this was a good thing. I thought the kernel got updated
> automatically - I was probably mistaken. So I updated it manually.
>
> So, interestingly, it solved PART of the problem. When I am in a 1:1
> discussion, it works flawlessly on wireless. But if there are multiple
> people in the call, then it started having issues again.
>
> Give me a few days here. I have a few calls upcoming, I will give the wifi
> a try in different settings (1:1 and multiple folks) and let you know if
> (3) + (4) actually did the trick (because on the 1:1, I could only test (4)
> in isolation so far).
>
> Best Regards,
>
> Steve
>
> On Thu, Jun 24, 2021 at 12:05 AM Kai-Chuan Hsieh <
> <email address hidden>> wrote:
>
>> ** Changed in: oem-priority
>> Status: New => Confirmed
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1932548
>>
>> Title:
>> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
>> wireless [8086:a0f0]
>>
>> Status in OEM Priority Project:
>> Confirmed
>> Status in linux-oem-5.10 package in Ubuntu:
>> New
>>
>> Bug description:
>> Whenever I am using a wireless connection, the image freezes roughly
>> every two minutes. Sometimes, email cannot be retrieved / computer
>> complains the connection was momentarily lost.
>>
>> - If I am on a wire, this problem does NOT occur.
>> - This problems occurs on wireless independent of the platform used
>> (behavior seen in both Google Hangout and Zoom)
>> - This problem does NOT occur on Windows. I did a meeting where both my
>> Linux and Windows machines were connected to the same meeting and using the
>> same wifi router, and while the performance on Windows was flawless,
>> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
>> router or network is to blame.
>> - As far as I can recall, the problem used not to be there 2 weeks ago.
>> So it may have been introduced by a recent update.
>> - As communicated before, I am on a certified machine from Dell,
>> recently purchased with Ubuntu already on board from factory (I assume the
>> logs there were sent to you would...

[Kai-Chuan Hsieh (kchsieh)]

@skidooman

1. the ucode should be in /lib/firmware, please check kernel log, if the latest firmware is loaded
$ journalctl -k | grep "loaded firmware version"

2. the iperf test for local area network performance, you need such scenario
your PC (with problem) <-Wireless-> Access Point <-Ethernet-> Any PC (testbed)

Install iperf3 on both side PC $ sudo apt install iperf3
For testing Tx, run client command on your PC and server command on test bed.
For testing Rx, run server command on your PC and client command on test bed.

server command: $ iperf -s -i 1
client command: $ iperf -c <server ip> -t 100 -i 1

i: the interval to show statistics
t: the time to perform the test

you can monitor the throughput instantly on client side. the key point is the rate should comply your Wi-Fi selected modulation and stable.

For example, you can see the bit rate by running $ iwconfig, the throughput roughly should be the half of the theoretical rate, which is the bit rate you are using now, sometimes it may constraint by the bus speed, but that's the other story. I think the most important part for video conference is stability, you can focus on that.

[Kai-Chuan Hsieh (kchsieh)]

Open a platform bug https://bugs.launchpad.net/somerville/+bug/1933755 for tracking the firmware crash.

[AceLan Kao (acelankao)]

5.10 kernel supports API_MAX is 59 and on the system it uses 55,
I'm wondering if newer firmware fixes this issue.

Please copy the firmware "iwlwifi-QuZ-a0-hr-b0-59.ucode" to /lib/firmware and power cycle. Then check if this issue persists.

[Steve Barriault (skidooman)]

Hi Acelan:

I did but... it did not work. :(

Best Regards,

Steve

On Mon, Jun 28, 2021 at 4:50 AM AceLan Kao <email address hidden>
wrote:

> 5.10 kernel supports API_MAX is 59 and on the system it uses 55,
> I'm wondering if newer firmware fixes this issue.
>
> Please copy the firmware "iwlwifi-QuZ-a0-hr-b0-59.ucode" to
> /lib/firmware and power cycle. Then check if this issue persists.
>
> ** Attachment added: "iwlwifi-QuZ-a0-jf-b0-59.ucode"
>
> https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1932548/+attachment/5507574/+files/iwlwifi-QuZ-a0-jf-b0-59.ucode
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 18 09:47:58 2021
> DistUpgraded: Fresh install
> DistributionChannelDescriptor:
> # This is the distribution channel descriptor for the OEM CDs
> # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> canonical-oem-somerville-focal-amd64-20200502-85
> DistroCodename: focal
> DistroVariant: ubuntu
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> Intel Corporation Device [8086:9a49] (rev 01) (pr...

[Kai-Chuan Hsieh (kchsieh)]

Hello Steve,

Can you attach your kernel log? upload output of "$ journalctl -k".

Thanks,

[Alex Tu (alextu)]

Hi Steve,

is the firmware from #9 fixed the issue?
So far, we don't sure if the firmware crashing the root cause of your issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP: #1933755 (see LP: #1933755 comment #2)

[Steve Barriault (skidooman)]

Hi Kai-Chuan:

Let me do this after I just reproduced the bug. The last two days I kept my
computer connected through Ethernet because the freeze really impedes my
ability to understand my counterparts.

Best Regards,

Steve

On Wed, Jun 30, 2021 at 7:55 PM Kai-Chuan Hsieh <email address hidden>
wrote:

> Hello Steve,
>
> Can you attach your kernel log? upload output of "$ journalctl -k".
>
> Thanks,
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 18 09:47:58 2021
> DistUpgraded: Fresh install
> DistributionChannelDescriptor:
> # This is the distribution channel descriptor for the OEM CDs
> # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> canonical-oem-somerville-focal-amd64-20200502-85
> DistroCodename: focal
> DistroVariant: ubuntu
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
> controller])
> Subsystem: Dell Device [1028:0991]
> InstallationDate: Installed on 2021-04-24 (54 days ago)
> InstallationMedia: Ubuntu 20.04 "Focal" ...

[Steve Barriault (skidooman)]

Sorry Alex... could you please explain what you mean by #9?

Sorry for the newbie question, but I want to help, and I am not sure what
you would like me to do.

On Wed, Jun 30, 2021 at 11:10 PM Alex Tu <email address hidden> wrote:

> Hi Steve,
>
> is the firmware from #9 fixed the issue?
> So far, we don't sure if the firmware crashing the root cause of your
> issue, so KC separated it to LP: #1933755. And firmware from #9 helps LP:
> #1933755 (see LP: #1933755 comment #2)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Jun 18 09:47:58 2021
> DistUpgraded: Fresh install
> DistributionChannelDescriptor:
> # This is the distribution channel descriptor for the OEM CDs
> # For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
> canonical-oem-somerville-focal-amd64-20200502-85
> DistroCodename: focal
> DistroVariant: ubuntu
> EcryptfsInUse: Yes
> ExtraDebuggingInterest: Yes
> GraphicsCard:
> Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA
> controller])
> Subsystem: Dell Device [1028:0991]
> InstallationDate: Installed...

[Alex Tu (alextu)]

Hi Steve, my comment #12 is saying the firmware in #9 works on the machine in certification lab, so that HWE is doing a SRU [1] to land that firmware.

But that firmware seems not to work for your case(refer to your comment #10 which I missed when commenting #9).

Could you please also provide your dmesg again when for the issue after you applied the firmware from #9 or from [1]

[1] https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217

[Steve Barriault (skidooman)]

Hi Alex:

Alright, here's the dmesg as attached.

So, here's something funny that happened today. I lost power, so used my
cell phone as a hotspot with my Linux machine. My cell phone is not Wifi6.

Even after power was restored, I forgot that I was on the hotspot and I did
a meeting with about 10 people. And guess what? No freeze, not even a
slight!

Perhaps this was self-evident to you, but I think that the Wifi6 factor
that makes the difference. In the lab, did you try with Wifi6?

Best Regards,

Steve

On Tue, Jul 6, 2021 at 10:20 AM Alex Tu <email address hidden> wrote:

> Hi Steve, my comment #12 is saying the firmware in #9 works on the
> machine in certification lab, so that HWE is doing a SRU [1] to land
> that firmware.
>
> But that firmware seems not to work for your case(refer to your comment
> #10 which I missed when commenting #9).
>
> Could you please also provide your dmesg again when for the issue after
> you applied the firmware from #9 or from [1]
>
>
> [1] https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDesktop: ubuntu:GNOME
> Date:...

[Kai-Chuan Hsieh (kchsieh)]

@skidooman

hello,

According to your log, you indeed load -59 fw, but the firmware is still crashed.

[20088.470922] iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
[20088.472117] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[20088.472118] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
[20088.472120] iwlwifi 0000:00:14.3: Loaded firmware version: 59.601f3a66.0 QuZ-a0-hr-b0-59.ucode
[20088.472122] iwlwifi 0000:00:14.3: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[20088.472123] iwlwifi 0000:00:14.3: 0x0000A210 | trm_hw_status0
[20088.472124] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[20088.472125] iwlwifi 0000:00:14.3: 0x004CB046 | branchlink2
[20088.472126] iwlwifi 0000:00:14.3: 0x0001C700 | interruptlink1
[20088.472127] iwlwifi 0000:00:14.3: 0x0001C700 | interruptlink2
[20088.472128] iwlwifi 0000:00:14.3: 0x0000B734 | data1
[20088.472129] iwlwifi 0000:00:14.3: 0x00001000 | data2
[20088.472130] iwlwifi 0000:00:14.3: 0x00000000 | data3
[20088.472131] iwlwifi 0000:00:14.3: 0xD4C177FC | beacon time
[20088.472132] iwlwifi 0000:00:14.3: 0xBA7C7806 | tsf low
[20088.472133] iwlwifi 0000:00:14.3: 0x00000004 | tsf hi
[20088.472134] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[20088.472135] iwlwifi 0000:00:14.3: 0xACA6C4CC | time gp2
[20088.472136] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[20088.472137] iwlwifi 0000:00:14.3: 0x0000003B | uCode version major
[20088.472137] iwlwifi 0000:00:14.3: 0x601F3A66 | uCode version minor
[20088.472138] iwlwifi 0000:00:14.3: 0x00000351 | hw version
[20088.472139] iwlwifi 0000:00:14.3: 0x00C89004 | board version
[20088.472140] iwlwifi 0000:00:14.3: 0x803EFC02 | hcmd
[20088.472141] iwlwifi 0000:00:14.3: 0x24020000 | isr0
[20088.472142] iwlwifi 0000:00:14.3: 0x00400000 | isr1
[20088.472143] iwlwifi 0000:00:14.3: 0x08B00002 | isr2
[20088.472144] iwlwifi 0000:00:14.3: 0x00C37FCC | isr3
[20088.472145] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[20088.472145] iwlwifi 0000:00:14.3: 0x0464001C | last cmd Id
[20088.472146] iwlwifi 0000:00:14.3: 0x0000B734 | wait_event
[20088.472147] iwlwifi 0000:00:14.3: 0x00006208 | l2p_control
[20088.472148] iwlwifi 0000:00:14.3: 0x00010014 | l2p_duration
[20088.472149] iwlwifi 0000:00:14.3: 0x0000033F | l2p_mhvalid
[20088.472150] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
[20088.472150] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[20088.472151] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[20088.472152] iwlwifi 0000:00:14.3: 0x0000B0D0 | flow_handler
[20088.472658] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[20088.472659] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
[20088.472660] iwlwifi 0000:00:14.3: 0x2000307C | ADVANCED_SYSASSERT
[20088.472660] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[20088.472661] iwlwifi 0000:00:14.3: 0x80456E90 | umac branchlink2
[20088.472662] iwlwifi 0000:00:14.3: 0xC0085328 | umac interruptlink1
[20088.472662] iwlwifi 0000:00:14.3: 0x00000000 | umac interruptlink2
[20088.472663] iwlwifi 0000:00:14.3: 0x00000000 | umac data1
[20088.472664] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data2
[20088.472664] iwlwifi 0000:00:14.3: 0xDEADBEEF | umac data3
[20088.472665] iwlwifi 0000:00:14.3: 0x0000...

[Steve Barriault (skidooman)]

OK guys, please let me know if there are anything else you need me to do to
help you diagnose this.

All I can say is that if I am on wired OR on a Wifi that is not Wifi 6, I
do not see the freeze. But on my Wifi 6 access point it is easily
replicable.

That does not affect other OSes I have at home. Windows, Mac and Android
are all OK, so I know the base itself is not the problem.

On Tue, Jul 6, 2021 at 11:15 PM Kai-Chuan Hsieh <email address hidden>
wrote:

> @skidooman
>
> hello,
>
> According to your log, you indeed load -59 fw, but the firmware is still
> crashed.
>
> [20088.470922] iwlwifi 0000:00:14.3: Microcode SW error detected.
> Restarting 0x0.
> [20088.472117] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
> [20088.472118] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 6
> [20088.472120] iwlwifi 0000:00:14.3: Loaded firmware version:
> 59.601f3a66.0 QuZ-a0-hr-b0-59.ucode
> [20088.472122] iwlwifi 0000:00:14.3: 0x00000071 |
> NMI_INTERRUPT_UMAC_FATAL
> [20088.472123] iwlwifi 0000:00:14.3: 0x0000A210 | trm_hw_status0
> [20088.472124] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
> [20088.472125] iwlwifi 0000:00:14.3: 0x004CB046 | branchlink2
> [20088.472126] iwlwifi 0000:00:14.3: 0x0001C700 | interruptlink1
> [20088.472127] iwlwifi 0000:00:14.3: 0x0001C700 | interruptlink2
> [20088.472128] iwlwifi 0000:00:14.3: 0x0000B734 | data1
> [20088.472129] iwlwifi 0000:00:14.3: 0x00001000 | data2
> [20088.472130] iwlwifi 0000:00:14.3: 0x00000000 | data3
> [20088.472131] iwlwifi 0000:00:14.3: 0xD4C177FC | beacon time
> [20088.472132] iwlwifi 0000:00:14.3: 0xBA7C7806 | tsf low
> [20088.472133] iwlwifi 0000:00:14.3: 0x00000004 | tsf hi
> [20088.472134] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
> [20088.472135] iwlwifi 0000:00:14.3: 0xACA6C4CC | time gp2
> [20088.472136] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
> [20088.472137] iwlwifi 0000:00:14.3: 0x0000003B | uCode version major
> [20088.472137] iwlwifi 0000:00:14.3: 0x601F3A66 | uCode version minor
> [20088.472138] iwlwifi 0000:00:14.3: 0x00000351 | hw version
> [20088.472139] iwlwifi 0000:00:14.3: 0x00C89004 | board version
> [20088.472140] iwlwifi 0000:00:14.3: 0x803EFC02 | hcmd
> [20088.472141] iwlwifi 0000:00:14.3: 0x24020000 | isr0
> [20088.472142] iwlwifi 0000:00:14.3: 0x00400000 | isr1
> [20088.472143] iwlwifi 0000:00:14.3: 0x08B00002 | isr2
> [20088.472144] iwlwifi 0000:00:14.3: 0x00C37FCC | isr3
> [20088.472145] iwlwifi 0000:00:14.3: 0x00000000 | isr4
> [20088.472145] iwlwifi 0000:00:14.3: 0x0464001C | last cmd Id
> [20088.472146] iwlwifi 0000:00:14.3: 0x0000B734 | wait_event
> [20088.472147] iwlwifi 0000:00:14.3: 0x00006208 | l2p_control
> [20088.472148] iwlwifi 0000:00:14.3: 0x00010014 | l2p_duration
> [20088.472149] iwlwifi 0000:00:14.3: 0x0000033F | l2p_mhvalid
> [20088.472150] iwlwifi 0000:00:14.3: 0x00000000 | l2p_addr_match
> [20088.472150] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
> [20088.472151] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
> [20088.472152] iwlwifi 0000:00:14.3: 0x0000B0D0 | flow_handler
> [20088.472658] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
> [20088.472659] iwlwifi 0000:00:14.3: Status: 0x00000040, count: 7
> [20...

[Alex Tu (alextu)]

progress update:
 - Vicamo is SRUing related firmware for both oem 5.10, hwe 5.11 and oem 5.13.
   - for OEM 5.10, HWE 5.11: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217
   - for OEM 5.13: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415

The firmware crashing looks not happens to every machine using AX201.
 - Vicamo can not reproduce it with wifi6 AP during both SRU (LP: #1934217 and LP: 1933415)
 - one XPS 13 9310 passed with OEM 5.10 + firmware(LP: #1934217)
 - But another XPS 13 9310 failed with OEM 5.10 + firmware(LP: #1934217) on Steve's machine (per #17)

So, we are asking Intel for a suggested combination of Kernel and firmware to make sure the stability of AX201.

@Steve,
per #17, the firmware for OEM 5.10(LP: #1934217) not works for you.
Could you please have a try on OEM 5.13 + firmware from LP: #1933415?
Instruction:
 - # Add PPA from https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
 - sudo apt-get install linux-firmware # to get linux-firmware from Vicamo's PPA
 - sudo apt-get install linux-image-oem-20.04c # to install OEM 5.13

[Steve Barriault (skidooman)]

I am sorry Alex, but I am not sure what you are asking me to do exactly.

I am ready to try what you want, but please give me the howto as well, as I
am not sure what you mean here.

Best Regards,

Steve

On Wed, Jul 14, 2021 at 3:50 AM Alex Tu <email address hidden> wrote:

> progress update:
> - Vicamo is SRUing related firmware for both oem 5.10, hwe 5.11 and oem
> 5.13.
> - for OEM 5.10, HWE 5.11:
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934217
> - for OEM 5.13:
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415
>
> @Steve,
> per #17, the firmware for OEM 5.10(LP: #1934217) not works for you.
> Could you please have a try on OEM 5.13 + firmware from LP: #1933415?
>
> The firmware crashing looks not happens to every machine using AX201.
> - Vicamo can not reproduce it with wifi6 AP during both SRU (LP: #1934217
> and LP: 1933415)
> - It passed with OEM 5.10 + firmware(LP: #1934217)
> - But it failed with OEM 5.10 + firmware(LP: #1934217) on Steve's machine
> (per #17)
>
> So, we are asking Intel for a suggested combination of Kernel and
> firmware to make sure the stability of AX201.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in Linux Firmware:
> New
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission n...

[Alex Tu (alextu)]

sorry for confusing, let me break down the steps:
1. # Add PPA from https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
$ sudo add-apt-repository ppa:vicamo/linux-firmware-staging

2. # to get linux-firmware from Vicamo's PPA
$ sudo apt-get install linux-firmware

3. # to install OEM 5.13
# Please manually click on Pre-released updates(focal-proposed) in `Software & Updates` UI first.
$ sudo apt-get install linux-image-oem-20.04c

4. # reboot, and make sure you are running under oem kernel 5.13
$ uanme -r
5.13.0-1007-oem

5. # check if the target firmware `-63` loaded
$ dmesg | grep iwlwifi
iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode op_mode iwlmvm

6. # check if the wifi issue can still be reproduced.
- if it is there, please also attach the dmesg here.

[Alex Tu (alextu)]

@Zorro, We can not reproduce the AX201 wifi crashing issue with new firmware #9 + kernel 5.10.0-1037-oem on the machine XPS 13 TGL in the certification pool. But it happens to Steve's XPS 13 TGL.

Could you please check if this issue can be reproduced on other XPS 13 TGL + AX201 wifi[8086:a0f0] you have?

[Steve Barriault (skidooman)]

Hi Alex:

I did steps 1 and 2 already.

Step 3, I get the following error: could not find

(Actual message is in French)

Could you check if this has been uploaded to the database?

Best Regards,

Steve

On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <email address hidden> wrote:

> sorry for confusing, let me break down the steps:
> 1. # Add PPA from
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
> $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging
>
> 2. # to get linux-firmware from Vicamo's PPA
> $ sudo apt-get install linux-firmware
>
> 3. # to install OEM 5.13
> $ sudo apt-get install linux-image-oem-20.04c
>
> 4. # reboot, and make sure you are running under oem kernel 5.13
> $ uanme -r
> 5.13.0-1007-oem
>
> 5. # check if the target firmware `-63` loaded
> $ dmesg | grep iwlwifi
> iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0
> QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
>
> 6. # check if the wifi issue can still be reproduced.
> - if it is there, please also attach the dmesg here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1932548
>
> Title:
> [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> wireless [8086:a0f0]
>
> Status in Linux Firmware:
> New
> Status in OEM Priority Project:
> Confirmed
> Status in linux-oem-5.10 package in Ubuntu:
> New
>
> Bug description:
> Whenever I am using a wireless connection, the image freezes roughly
> every two minutes. Sometimes, email cannot be retrieved / computer
> complains the connection was momentarily lost.
>
> - If I am on a wire, this problem does NOT occur.
> - This problems occurs on wireless independent of the platform used
> (behavior seen in both Google Hangout and Zoom)
> - This problem does NOT occur on Windows. I did a meeting where both my
> Linux and Windows machines were connected to the same meeting and using the
> same wifi router, and while the performance on Windows was flawless,
> unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> router or network is to blame.
> - As far as I can recall, the problem used not to be there 2 weeks ago.
> So it may have been introduced by a recent update.
> - As communicated before, I am on a certified machine from Dell,
> recently purchased with Ubuntu already on board from factory (I assume the
> logs there were sent to you would contain the information).
> - I tried to generate a log on the wireless, but the process did not let
> me do this very easily. I am more than happy to send you additional
> information - but please let me know which package you want me to spy upon
> exactly, as I am not sure what would be helpful in this matter.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 20.04
> Package: xorg 1:7.7+19ubuntu14
> ProcVersionSignature: Ubuntu 5.10.0-1029.30-oem 5.10.35
> Uname: Linux 5.10.0-1029-oem x86_64
> ApportVersion: 2.20.11-0ubuntu27.18
> Architecture: amd64
> BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
> CasperMD5CheckResult: skip
> CompositorRunning: None
> CurrentDeskto...

[Alex Tu (alextu)]

Hi Steve,
Looks launchpad does not forward the updated comment through mail.
I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now:

3. # to install OEM 5.13
# Please manually click on Pre-released updates(focal-proposed) in
`Software & Updates` UI first.
$ sudo apt-get install linux-image-oem-20.04c

On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault <email address hidden>
wrote:

> Hi Alex:
>
> I did steps 1 and 2 already.
>
> Step 3, I get the following error: could not find
>
> (Actual message is in French)
>
> Could you check if this has been uploaded to the database?
>
> Best Regards,
>
> Steve
>
> On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <email address hidden>
> wrote:
>
> > sorry for confusing, let me break down the steps:
> > 1. # Add PPA from
> >
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
> > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging
> >
> > 2. # to get linux-firmware from Vicamo's PPA
> > $ sudo apt-get install linux-firmware
> >
> > 3. # to install OEM 5.13
> > $ sudo apt-get install linux-image-oem-20.04c
> >
> > 4. # reboot, and make sure you are running under oem kernel 5.13
> > $ uanme -r
> > 5.13.0-1007-oem
> >
> > 5. # check if the target firmware `-63` loaded
> > $ dmesg | grep iwlwifi
> > iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0
> > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
> >
> > 6. # check if the wifi issue can still be reproduced.
> > - if it is there, please also attach the dmesg here.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1932548
> >
> > Title:
> > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am on
> > wireless [8086:a0f0]
> >
> > Status in Linux Firmware:
> > New
> > Status in OEM Priority Project:
> > Confirmed
> > Status in linux-oem-5.10 package in Ubuntu:
> > New
> >
> > Bug description:
> > Whenever I am using a wireless connection, the image freezes roughly
> > every two minutes. Sometimes, email cannot be retrieved / computer
> > complains the connection was momentarily lost.
> >
> > - If I am on a wire, this problem does NOT occur.
> > - This problems occurs on wireless independent of the platform used
> > (behavior seen in both Google Hangout and Zoom)
> > - This problem does NOT occur on Windows. I did a meeting where both my
> > Linux and Windows machines were connected to the same meeting and using
> the
> > same wifi router, and while the performance on Windows was flawless,
> > unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> > router or network is to blame.
> > - As far as I can recall, the problem used not to be there 2 weeks ago.
> > So it may have been introduced by a recent update.
> > - As communicated before, I am on a certified machine from Dell,
> > recently purchased with Ubuntu already on board from factory (I assume
> the
> > logs there were sent to you would contain the information).
> > - I tried to generate a log on the wireless, but the process did not
> let
> > me do this very easily. I am more than happy to send you...

[Steve Barriault (skidooman)]

OK Alex, made it to step 4.

For step 5, I need to try a Web meeting. I should have a way to attempt
this tomorrow and let you know if it worked or not.

Best Regards,

Steve

On Fri, Jul 16, 2021 at 7:15 AM Alex Tu <email address hidden> wrote:

> Hi Steve,
> Looks launchpad does not forward the updated comment through mail.
> I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now:
>
> 3. # to install OEM 5.13
> # Please manually click on Pre-released updates(focal-proposed) in
> `Software & Updates` UI first.
> $ sudo apt-get install linux-image-oem-20.04c
>
> On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault <
> <email address hidden>>
> wrote:
>
> > Hi Alex:
> >
> > I did steps 1 and 2 already.
> >
> > Step 3, I get the following error: could not find
> >
> > (Actual message is in French)
> >
> > Could you check if this has been uploaded to the database?
> >
> > Best Regards,
> >
> > Steve
> >
> > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <email address hidden>
> > wrote:
> >
> > > sorry for confusing, let me break down the steps:
> > > 1. # Add PPA from
> > >
> >
> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
> > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging
> > >
> > > 2. # to get linux-firmware from Vicamo's PPA
> > > $ sudo apt-get install linux-firmware
> > >
> > > 3. # to install OEM 5.13
> > > $ sudo apt-get install linux-image-oem-20.04c
> > >
> > > 4. # reboot, and make sure you are running under oem kernel 5.13
> > > $ uanme -r
> > > 5.13.0-1007-oem
> > >
> > > 5. # check if the target firmware `-63` loaded
> > > $ dmesg | grep iwlwifi
> > > iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0
> > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
> > >
> > > 6. # check if the wifi issue can still be reproduced.
> > > - if it is there, please also attach the dmesg here.
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1932548
> > >
> > > Title:
> > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am
> on
> > > wireless [8086:a0f0]
> > >
> > > Status in Linux Firmware:
> > > New
> > > Status in OEM Priority Project:
> > > Confirmed
> > > Status in linux-oem-5.10 package in Ubuntu:
> > > New
> > >
> > > Bug description:
> > > Whenever I am using a wireless connection, the image freezes roughly
> > > every two minutes. Sometimes, email cannot be retrieved / computer
> > > complains the connection was momentarily lost.
> > >
> > > - If I am on a wire, this problem does NOT occur.
> > > - This problems occurs on wireless independent of the platform used
> > > (behavior seen in both Google Hangout and Zoom)
> > > - This problem does NOT occur on Windows. I did a meeting where both
> my
> > > Linux and Windows machines were connected to the same meeting and using
> > the
> > > same wifi router, and while the performance on Windows was flawless,
> > > unfortunately it was not so on the Ubuntu box. So I don't think my wifi
> > > router or network is to blame.
> > > - As far as I can recall, the problem used not to be th...

[Steve Barriault (skidooman)]

Hi Alex:

I gave it a go during Mark's presentation. I am sorry to report it is not
solved.

Wifi6 is freezing on a regular basis, while non-wife6 connections are just
fine.

Here's the dmesg appended.

Best Regards,

Steve

On Sun, Jul 18, 2021 at 10:01 AM Steve Barriault <email address hidden>
wrote:

> OK Alex, made it to step 4.
>
> For step 5, I need to try a Web meeting. I should have a way to attempt
> this tomorrow and let you know if it worked or not.
>
> Best Regards,
>
> Steve
>
> On Fri, Jul 16, 2021 at 7:15 AM Alex Tu <email address hidden>
> wrote:
>
>> Hi Steve,
>> Looks launchpad does not forward the updated comment through mail.
>> I updated step 3 because of OEM kernel 5.13 is only in focal-proposed now:
>>
>> 3. # to install OEM 5.13
>> # Please manually click on Pre-released updates(focal-proposed) in
>> `Software & Updates` UI first.
>> $ sudo apt-get install linux-image-oem-20.04c
>>
>> On Fri, Jul 16, 2021 at 10:00 AM Steve Barriault <
>> <email address hidden>>
>> wrote:
>>
>> > Hi Alex:
>> >
>> > I did steps 1 and 2 already.
>> >
>> > Step 3, I get the following error: could not find
>> >
>> > (Actual message is in French)
>> >
>> > Could you check if this has been uploaded to the database?
>> >
>> > Best Regards,
>> >
>> > Steve
>> >
>> > On Wed, Jul 14, 2021 at 10:01 AM Alex Tu <email address hidden>
>> > wrote:
>> >
>> > > sorry for confusing, let me break down the steps:
>> > > 1. # Add PPA from
>> > >
>> >
>> https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1933415/comments/2
>> > > $ sudo add-apt-repository ppa:vicamo/linux-firmware-staging
>> > >
>> > > 2. # to get linux-firmware from Vicamo's PPA
>> > > $ sudo apt-get install linux-firmware
>> > >
>> > > 3. # to install OEM 5.13
>> > > $ sudo apt-get install linux-image-oem-20.04c
>> > >
>> > > 4. # reboot, and make sure you are running under oem kernel 5.13
>> > > $ uanme -r
>> > > 5.13.0-1007-oem
>> > >
>> > > 5. # check if the target firmware `-63` loaded
>> > > $ dmesg | grep iwlwifi
>> > > iwlwifi 0000:00:14.3: loaded firmware version 63.c04f3485.0
>> > > QuZ-a0-hr-b0-63.ucode op_mode iwlmvm
>> > >
>> > > 6. # check if the wifi issue can still be reproduced.
>> > > - if it is there, please also attach the dmesg here.
>> > >
>> > > --
>> > > You received this bug notification because you are subscribed to the
>> bug
>> > > report.
>> > > https://bugs.launchpad.net/bugs/1932548
>> > >
>> > > Title:
>> > > [Intel Wi-Fi 6 AX201] Video conferences constantly freeze when I am
>> on
>> > > wireless [8086:a0f0]
>> > >
>> > > Status in Linux Firmware:
>> > > New
>> > > Status in OEM Priority Project:
>> > > Confirmed
>> > > Status in linux-oem-5.10 package in Ubuntu:
>> > > New
>> > >
>> > > Bug description:
>> > > Whenever I am using a wireless connection, the image freezes roughly
>> > > every two minutes. Sometimes, email cannot be retrieved / computer
>> > > complains the connection was momentarily lost.
>> > >
>> > > - If I am on a wire, this problem does NOT occur.
>> > > - This problems occurs on wireless independent of the platform used
>> > > (behavior seen in both Google Hangout and Zoom)
>> > > - This p...

[Kai-Chuan Hsieh (kchsieh)]

@skidooman

Could you try the software configuration you are using in #26, but disable UFW?
I am using Precision 5750 from daily basis (it utilizes the same Wi-Fi firmware as yours), but I didn't encounter the firmware crash like yours so frequently, I can finish the meeting with Wi-Fi everyday, and I am using https://www.asus.com/Networking-IoT-Servers/WiFi-Routers/ASUS-WiFi-Routers/RT-AX56U/, which is Wi-Fi 6 too.

From the log, the UFW keeps blocking the packet from the AP 192.168.1.1, then the firmware can't handle the request from driver and it is crashed. Sorry that we can't debug the firmware, since it is a pure binary from Intel.

By the way, could you attach the Access Point information? I'll try if we can find the same model here in Taiwan.

Thanks,

[Harrison Hemstreet (harrison-m-h)]

This bug is affecting me too!!!!!! Please fix!!!!!!!!!

The Intel AX201 Wi-fi 6 driver is broken on all current versions of Ubuntu!!!!!!!!

[Alex Tu (alextu)]

Hi Harrison,
Intel used to ask users using the latest proprietary firmware from upstream[1].
The proprietary firmware is a blackbox in opensource, so we are trying to figure out the stable combination of kernel and related firmware.

So far there are 2 kernel flavors verified works in the environment of #27 in Focal:
1. HWE kernel 5.11 + latest firmware iwlwifi-QuZ-a0-hr-b0-59.ucode (you can try it from the linux-firmware from #21 which is doing SRU)
2. OEM kernel 5.13 + latest firmware -63 (you can try it from the linux-firmware from #21 which is doing SRU)

We did not check the latest mainline kernel[2] + latest upstream firmware [1] because so far the above 2 works well in our WIFI AX environment.

We are wondering if any difference from the Steve's environment and yours keep the Intel proprietary firmware crashing.

Could you please check if the above 2 kernel flavors plus the linux-firmware doing SRUing work on your environment?
If it still failed, could you please share with us the dmesg and lspci (better to get sosreport as well) and which WIFI 6 AP you are connecting to? So that we can try reproducing your issue here :)

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
[2] https://kernel.ubuntu.com/~kernel-ppa/mainline/