Unstable WiFi adapter Gigabyte GC-WB867D-I

Bug #1772154 reported by Gabriele N. Tornetta on 2018-05-19
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu 18.04. I do not have data relative to previous versions of Ubuntu since this PCIe card is part of a new build that has had 18.04 as the first installed version.

The reason why I can point the finger at the Linux kernel is that the card seems to work reliably well on Windows 10 (no packet loss when pinging the local router). On Ubuntu 18.04, the card's behaviour seems very correlated to the signal strength and exhibits a threshold phenomenon. With the antenna placed in an obstacle-free area, some ping packets are occasionally lost. But when some objects are placed near the antenna (e.g. a phone), the packet loss can get up to 90%. Under the very same conditions, the packet loss on Windows is exactly 0 (and the RTT never gets above 500ms).

I have disabled the WiFi power saving (changed from 2 to 3) but that didn't fix the problem. It seems that restarting the NetworkManager service helps for a bit, but after a while the problem resurfaces.

The card in question has onboard USB Bluetooth and is pretty much an M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output of lspci is

03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 19 10:32:00 2018
InstallationDate: Installed on 2018-04-29 (19 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/pcmC1D7p: gabriele 1893 F...m pulseaudio
 /dev/snd/controlC1: gabriele 1893 F.... pulseaudio
 /dev/snd/controlC0: gabriele 1893 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=d2390d6b-2bc3-41bb-b385-3dd8921a36e2
InstallationDate: Installed on 2018-04-29 (22 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2e79827f-410a-4aba-ab8f-e278ca6e7aa3 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-20-generic N/A
 linux-backports-modules-4.15.0-20-generic N/A
 linux-firmware 1.173
Tags: bionic
Uname: Linux 4.15.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/07/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: B360M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/07/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB360MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6

affects: linux-signed (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Medium

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1772154

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

As per instructions received, I have tested v4.17-rc6 of the Ubuntu Linux Kernel (http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/) and the problem still persists.

tags: added: kernel-bug-exists-upstream
Kai-Heng Feng (kaihengfeng) wrote :

Can you also try latest firmware, iwlwifi-8265-36.ucode in [1]?

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

I have tried the latest firmware on 4.17-rc6:

$ uname -a
Linux gabriele-clake 4.17.0-041700rc6-generic #201805202330 SMP Sun May 20 23:31:40 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ dmesg | grep iwlwifi
[ 3.076579] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 3.096863] iwlwifi 0000:03:00.0: loaded firmware version 36.e91976c0.0 op_mode iwlmvm
[ 3.120264] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 3.178567] iwlwifi 0000:03:00.0: base HW address: 74:e5:f9:06:c9:9e
[ 3.261497] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0

This is the result of some testing:

2659 packets transmitted, 2075 received, 21% packet loss, time 2675131ms
rtt min/avg/max/mdev = 1.423/17.950/2177.566/139.050 ms, pipe 3

The problem seems to persist.

Kai-Heng Feng (kaihengfeng) wrote :

There are lots of new commits in iwlwifi since v4.17-rc6. Please wait for v4.18-rc1 and give it a try.

If the issue still happen, file a bug at https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers, component: network-wireless.

Download full text (5.6 KiB)

I have tried the latest firmware on v4.18-rc1
(ce397d215ccd07b8ae3f71db689aedb85d56ab40) and the problem seems to persist:

7399 packets transmitted, 5704 received, 22% packet loss, time 7446041ms
rtt min/avg/max/mdev = 1.431/5.948/1057.709/36.507 ms, pipe 2

It is hard to tell for sure, but even though there still is a considerable
number of lost packets, stability seems a bit better.

It might be worth noting that the same problem has now appeared on Win10
after the April 2018 update. The latest Intel 8265 from the 14th of June
doesn't seem to do any good (microcode update?).

Please advise on how to proceed.

Thanks.

Best regards,
Gabriele

On Fri, 8 Jun 2018 at 20:01, Kai-Heng Feng <email address hidden>
wrote:

> There are lots of new commits in iwlwifi since v4.17-rc6. Please wait
> for v4.18-rc1 and give it a try.
>
> If the issue still happen, file a bug at
> https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers, component:
> network-wireless.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772154
>
> Title:
> Unstable WiFi adapter Gigabyte GC-WB867D-I
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> The WiFi adapter Gigabyte GC-WB867D-I is quite unstable on Ubuntu
> 18.04. I do not have data relative to previous versions of Ubuntu
> since this PCIe card is part of a new build that has had 18.04 as the
> first installed version.
>
> The reason why I can point the finger at the Linux kernel is that the
> card seems to work reliably well on Windows 10 (no packet loss when
> pinging the local router). On Ubuntu 18.04, the card's behaviour seems
> very correlated to the signal strength and exhibits a threshold
> phenomenon. With the antenna placed in an obstacle-free area, some
> ping packets are occasionally lost. But when some objects are placed
> near the antenna (e.g. a phone), the packet loss can get up to 90%.
> Under the very same conditions, the packet loss on Windows is exactly
> 0 (and the RTT never gets above 500ms).
>
> I have disabled the WiFi power saving (changed from 2 to 3) but that
> didn't fix the problem. It seems that restarting the NetworkManager
> service helps for a bit, but after a while the problem resurfaces.
>
> The card in question has onboard USB Bluetooth and is pretty much an
> M.2 to PCIe x1 adapter for an Intel Wifi adapter. The relevant output
> of lspci is
>
> 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275
> (rev 78)
>
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: linux-image-4.15.0-20-generic 4.15.0-20.21
> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
> Uname: Linux 4.15.0-20-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.9-0ubuntu7
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Sat May 19 10:32:00 2018
> InstallationDate: Installed on 2018-04-29 (19 days ago)
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
> SourcePackage: linux-signed
> UpgradeStatus: No upgrade log present (probably ...

Read more...

Kai-Heng Feng (kaihengfeng) wrote :

Follow #22 and file a bug to let Intel iwlwifi developers know.

aaronfranke (arnfranke) wrote :

Does this card still have issues with kernel 5.0?

You-Sheng Yang (vicamo) wrote :

Most people don't have the hardware you have, so usually it's on your own. There are a few ways to try:

1. latest kernel from https://kernel.ubuntu.com/~kernel-ppa/mainline/
2. latest firmware from https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/
3. backport-iwlwifi dkms from https://launchpad.net/~vicamo/+archive/ubuntu/backport-iwlwifi-dkms

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers