realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21

Bug #1838133 reported by Jun Go on 2019-07-27
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Status tracked in Eoan
Disco
Undecided
Unassigned
Eoan
High
AaronMa

Bug Description

=== SRU Justification ===
[Impact]
Realtek Wifi stops working after the driver changed from rtlwifi to
rtw88.

[Fix]
Sync rtw88 to upstream version, and use MSI on the device.

[Test]
User confirmed the backport fixes the issue.

[Regression Potential]
Low. Currently only 8822be uses rtw88.

=== Original Bug Report ===
On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection.

Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21.

I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version:

Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

With this kernel version as well as linux-headers-5.0.0.20, linux-headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded:

# lsmod | grep r8
r8822be 692224 0
mac80211 806912 1 r8822be
cfg80211 671744 2 mac80211,r8822be
r8169 81920 0

Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information.

Best Regards,
Jun

Jun Go (gojun077) on 2019-07-27
description: updated
lotuspsychje (lotuspsychje) wrote :

Thank you for reporting this bug to make Ubuntu better!

If you file bugs on ubuntu please consider ubuntu-bug packagename (perhaps linux in your case)

at this stage, you can still collect the info with: apport-collect bugID so relevant
system info will add to your bug and developers can debug a better way

Jun Go (gojun077) wrote :

Hi @lotuspsycheje ~

I ran the command "apport-collect 1838133" but I got the message "no additional information collected". Should I just run "ubuntu-bug linux"?

Paul White (paulw2u) on 2019-07-27
affects: ubuntu → linux (Ubuntu)

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 1838133

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
AaronMa (mapengyu) wrote :

Could you upload dmesg and "sudo lspci -vvvnn" on kernel 5.0.0.21?

Jun Go (gojun077) wrote :

Hi Aaron~

I have attached a file containing the output of dmesg and lscpi from kernel 5.0.0-21
Please let me know if I you need me to provide add'l info.

Thanks,
Jun

Changed in linux (Ubuntu):
status: Incomplete → Triaged
assignee: nobody → AaronMa (mapengyu)
importance: Undecided → High
AaronMa (mapengyu) wrote :

Hi Jun:

I didn't reproduce this issue on aother realtek b822 wifi card.

Could you try the following steps.

1, append "blacklist r8822be" in "/etc/modprobe.d/blacklist.conf";

2, sudo update-initramfs -u -k 5.0.0-21-generic

3, reboot to check if wifi is OK.

If it still fails, please upload dmesg.

Jun Go (gojun077) wrote :

Hi Aaron,

I appended r8822be driver to blacklist.conf and then manually ran "sudo update-initramfs -u -k 5.0.0-21-generic" and rebooted. Still no wifi, however.

I have attached the output of dmesg. BTW this notebook has Realtek ethernet hardware, which is why kernel driver r8169 is loaded.

Also, I don't know if this is relevant, but I have disabled all linux power management on this AMD Ryzen 7 gaming notebook b/c of issues when this computer enters power-saving mode.

In "/etc/default/tlp" I set "TLP_ENABLE=0" and also appended the following parameter to my GRUB commandline:

ahci.mobile_lpm_policy=0

Best,
Jun

AaronMa (mapengyu) wrote :

Hi Jun,

dmesg shows the rtw88 driver works on your b822 wifi card.

First, you can use the following steps as work around:
1, append "blacklist rtwpci" in "/etc/modprobe.d/blacklist.conf";
2, sudo update-initramfs -u -k 5.0.0-21-generic

Because my b822 wifi card didn't reproduce the issue you got.
please help debug.
1, still blacklist r8822be and remove rtw88 from blacklist;
2, add rtw88.debug_mask=0x3ff in kernel cmdline.

Try to connect wifi.
Then upload dmesg.

Jun Go (gojun077) wrote :

Hi Aaron,

I have attached the output of dmesg with rr8822be blacklisted and with rtw88.debug_mask=0x3ff added to the linux commandline from GRUB.

After boot, I verified that the rtw88 driver is loaded:

junbuntu@pj:~/playground$ lsmod | grep rtw
rtwpci 24576 0
rtw88 413696 1 rtwpci
mac80211 806912 2 rtwpci,rtw88
cfg80211 671744 2 mac80211,rtw88

But wifi is still not working. Even if I stop NetworkManager, stop wpa_supplicant and try to negotiate wifi manually (I have saved my wifi passwords and connection info from previous successful connections in a wpa_supplicant conf file) the wifi card is not coming up:

junbuntu@pj:~/playground$ sudo wpa_supplicant -B -i wlp7s0 -c /etc/wpa_supplicant/local.conf
Successfully initialized wpa_supplicant
junbuntu@pj:~/playground$ wpa_cli -i wlp7s0
wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <email address hidden> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.

Interactive mode

> scan
FAIL-BUSY
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
> scan_results
bssid / frequency / signal level / flags / ssid
> scan
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-SCAN-RESULTS
<3>CTRL-EVENT-NETWORK-NOT-FOUND
> scan_results
bssid / frequency / signal level / flags / ssid
> quit

Thanks,
Jun

Jun Go (gojun077) wrote :

btw~

When I tried the workaround you suggested:

>1, append "blacklist rtwpci" in "/etc/modprobe.d/blacklist.conf";
>2, sudo update-initramfs -u -k 5.0.0-21-generic

and rebooted, wlp7s0 (wlan0) does not even show up anymore. I have attached the output of lsmod when workaround 1 and 2 are applied.

Thanks,
Jun

AaronMa (mapengyu) wrote :

Reply to #10,
From lsmod, r8822be is not loaded, r8822be should be removed from blacklist.
rtwpci should be in blacklist.

This is workaround, no workaround 2.
For now, I think r8822be is good for your wifi.

rtw88 should be working on your wifi too, unfortunately it's not.
That why I need to debug on rtw88 driver and try to find root cause.
Let me check dmesg of #9.

AaronMa (mapengyu) wrote :

Hi Jun

My realtek b822 is the same as yours.

1, Could you upload "journalctl -b 0" with 5.0.0-21 kernel?

2, Install mainline kernel [1] and upload "journalctl -b 0" too.

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/

AaronMa (mapengyu) wrote :

For #12

Please remove "blacklist rtwpci" in "/etc/modprobe.d/blacklist.conf"

AaronMa (mapengyu) wrote :

add rtw88.debug_mask=0x3ff in kernel cmdline.

George Nelson (deft) wrote :

I have the same issue with 5.0.0-21 kernel update. Wireless card rtl8822be, this is bluetooth combo m.2 card. In Lenovo E585 laptop. I do not see any obvious errors, I can load rtwpci kernel modules, interface wlp4s0 is created, I scan with iw dev or iwlist and no networks are found. In Windows, the card works fine. I imagine rolling back to 5.0.0-20 will fix it.

Jun Go (gojun077) wrote :

Hi Aaron~

For #10 and #11, I removed r8822be from /etc/modprobe.d/blacklist.conf and added rtwpci to blacklist, rebuilt the initial ramdisk with sudo update-initramfs -u -k 5.0.0-21-generic and rebooted;

Now my realtek wifi card is operational with this workaround!

For the next test to help you debug the rtw88 realtek driver I will do the following:
(1) re-add r8822be to blacklist.conf
(2) remove rtwpci from blacklist.conf
(3) rebuild initrd
(4) reboot
(5) add rtw88.debug_mask=0x3ff in kernel cmdline in GRUB
(6) boot
(7) send you the output of dmesg

Thanks for your help!
Jun

AaronMa (mapengyu) wrote :

Hi Jun:

"journalctl -b0" will be better than dmesg

George Nelson (deft) wrote :

Reverting to 5.0.0-20 fixed wifi for me, this kernel doesn't load rtwpci module. I updated to 5.0.0-23 today, same problem as 5.0.0-21. I don't see any errors but wifi does not find networks.

I added debug_mask option to kernel command line and output journalctl -b0 is attached. I did not blacklist any modules.

viot (viot) wrote :

I propose a workaround (which is not very elegant)
When you are using a kernel 5.0.0.21 or higher
sudo modprobe -r r8822be rtwpci
sudo modprobe r8822be rtwpci

In this case, you recover the wifi
and if you type
lspci -nnk | grep 0280 -A3
you will see
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822]
 Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950]
 Kernel driver in use: r8822be
 Kernel modules: rtwpci, r8822be

If you try the same command before this trick I obtain
Kernel driver in use: rtw_pci

By changing the loading order of the modules, the wifi works again.
IF you know a more elegant way to load the modules, I am very interested

AaronMa (mapengyu) wrote :

Hi Viot and George:

Could you try mainline build kernel[1]?

I didn't reproduce this issue on both AMD and Intel platform.

[1] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/

Jun Go (gojun077) wrote :

Hi Aaron~

I have attached the debug info you requested for #16.

This time I re-blacklisted r8822be driver in blacklist.conf and removed rtwpci from blacklist.conf, rebuilt initrd, rebooted, and used the rtw88.debug_mask=0x3ff option in linux cmdline in GRUB.

As expected, wifi is not working when only rtw88 driver is active (and r8822be is inactive).

Next I will try with the mainline kernel.

Thanks,
Jun

Jun Go (gojun077) wrote :

Hi Aaron~

I downloaded the mainline kernel 5.3.0 from the ppa you provided and installed as follows:

wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux-headers-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb

wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux-image-unsigned-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb

wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux-modules-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb

sudo dpkg -i *.deb

I left my blacklist.conf unchanged (r8822be blacklisted, rtwpci not blacklisted). I rebooted and selected the mainline kernel from GRUB and added the rtw88.debug_mask=0x3ff linux cmdline option.

But with r8822be blacklisted, wifi does not work even on mainline 5.3.0. I have attached the output from journalctl -b0.

Here are the realtek kernel modules that are loaded:

junbuntu@pj:~$ lsmod | grep rtw
rtwpci 24576 0
rtw88 442368 1 rtwpci
mac80211 847872 2 rtwpci,rtw88
cfg80211 708608 2 mac80211,rtw88

Should I try again but this time remove r8822be from blacklist.conf (and also do not blacklist rtwpci)?

Best,
Jun

Jun Go (gojun077) wrote :
Download full text (7.6 KiB)

Hi Aaron~

I removed r8822be from the blacklist, rebuilt the mainline kernel with

sudo update-initramfs -u -k 5.3.0-050300rc2-generic

and rebooted. What is interesting is that in mainline, r8822be is not loaded at all! I have attached journalctl -b0.

In future kernels, will the Realtek 8822be card use the rtw88 kernel module?

Cheers,
Jun

output of lsmod below
====================================

Module Size Used by
rfcomm 81920 4
xt_CHECKSUM 16384 1
iptable_mangle 16384 1
bridge 176128 0
stp 16384 1 bridge
llc 16384 2 bridge,stp
ebtable_filter 16384 0
ebtables 36864 1 ebtable_filter
cmac 16384 1
overlay 114688 0
bnep 24576 2
binfmt_misc 24576 1
nls_iso8859_1 16384 1
snd_hda_codec_realtek 114688 1
snd_hda_codec_generic 81920 1 snd_hda_codec_realtek
ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek
snd_hda_codec_hdmi 61440 1
snd_hda_intel 49152 5
snd_hda_codec 131072 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_usb_audio 241664 2
snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
snd_usbmidi_lib 36864 1 snd_usb_audio
uvcvideo 98304 0
snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec
btusb 57344 0
snd_seq_midi 20480 0
snd_seq_midi_event 16384 1 snd_seq_midi
btrtl 20480 1 btusb
videobuf2_vmalloc 20480 1 uvcvideo
btbcm 16384 1 btusb
videobuf2_memops 20480 1 videobuf2_vmalloc
snd_rawmidi 36864 2 snd_seq_midi,snd_usbmidi_lib
btintel 24576 1 btusb
videobuf2_v4l2 24576 1 uvcvideo
videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo
bluetooth 577536 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
rtwpci 24576 0
snd_seq 69632 2 snd_seq_midi,snd_seq_midi_event
rtw88 442368 1 rtwpci
snd_pcm 106496 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
edac_mce_amd 32768 0
videodev 208896 3 videobuf2_v4l2,uvcvideo,videobuf2_common
kvm_amd 98304 0
snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi
mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
input_leds 16384 0
ecdh_generic 16384 2 bluetooth
joydev 24576 0
mac80211 847872 2 rtwpci,rtw88
snd_timer 36864 2 snd_seq,snd_pcm
ecc 28672 1 ecdh_generic
snd 86016 27 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
kvm 647168 1 kvm_amd
cfg80211 708608 2 mac80211,rtw88
irqbypass 16384 1 kvm
asus_nb_wm...

Read more...

Kai-Heng Feng (kaihengfeng) wrote :

Please compile a kernel latest wireless-drivers as the following:
$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git
$ cd wireless-drivers-next
$ yes '' | make localmodconfig
$ make -j`nproc` && make -j`nproc` modules && sudo make INSTALL_MOD_STRIP=1 modules_install && sudo make install

Jun Go (gojun077) wrote :

btw I can confirm that viot's workaround in #19 does indeed work on 5.0.0-23-generic which was released from the disco dingo repos yesterday.

Jun

AaronMa (mapengyu) wrote :

Hi Jun:

Yes, r8822be will be removed in latest kernel.
That's why we need to fix the issue on rtw88.

rtw88 is not working on 5.3-rc2 too.
right?

I can not reproduce this issue with b822 wifi card on AMD.

Let me check logs first,
you can try to build wireless-drivers-next in comment #24 too.

I suggest Blacklist rtw88 as a workaround for now.

Jun Go (gojun077) wrote :

Hi Aaron,

> rtw88 is not working on 5.3-rc2 too.
> right?

That is correct. rtw88 is not working for me on 5.3-rc2 mainline kernel. I will try to build a kernel with wireless-drivers-next as suggested in #24.

And for the time being I will add rtw88 to my /etc/modprobe.d/blacklist.conf and rebuild initrd when using kernels 5.0.0-21+ for disco dingo.

Cheers,
Jun

viot (viot) wrote :

Hi Aaron
I tried with the kernel 5.3-rc2 but the wifi does not work and the previous workround does not work anymore since only the module rtwpci can be loaded. The module r8822be is not present. I tried the module rtw88 but the kernel module in use is always rtwpci.
Cheers, Pascal

Kai-Heng Feng (kaihengfeng) wrote :

Can someone test #24? If the issue is still there then we need to raise the issue to upstream.

Jun Go (gojun077) wrote :

Hi Kai-Heng~

I tried the steps mentioned in #24 to build a kernel with the latest wireless-drivers-next modules. However, I'm getting the following error at the last step:

$ INSTALL_MOD_STRIP=1 modules_install && sudo make install
modules_install: command not found

Is there anything else I need to "make" before running this command?

Thanks,
Jun

Kai-Heng Feng (kaihengfeng) wrote :

Yes it's `sudo make INSTALL_MOD_STRIP=1 modules_install && sudo make install`.

The command gets cut halfway in the comment.

Jun Go (gojun077) wrote :

Hi Kai-Heng~

Thanks for the help. Now the 5.3.0-rc1+ kernel with wireless-drivers-next builds properly. I rebooted into the new kernel (selected from GRUB menu) and I can verify that wireless does not work.

I have attached a tarball containing the output of dmesg, journalctl -b0, and lsmod on mainline kernel 5.3.0-rc1+ with "wireless-drivers-next".

Let me know if there's any other information I can get for you.

Best,
Jun

Kai-Heng Feng (kaihengfeng) wrote :

rtw88 isn't in lsmod. Please unblacklist rtw88 and related modules, reboot, and rerun instruction in comment #24.

Jun Go (gojun077) wrote :

Hi Kai-Heng,

I checked my /etc/modprobe.d/blacklist.conf file, however, rtwpci and rtw88 are not blacklisted. I am not sure why both these kernel modules are not loaded when booting with kernel 5.3.0-rc1+...

Should I try building 5.3.0-rc1+ with different options?

Jun

Kai-Heng Feng (kaihengfeng) wrote :

Edit .config and manually enable rtw88:
CONFIG_RTW88=m
CONFIG_RTW88_CORE=m
CONFIG_RTW88_PCI=m
CONFIG_RTW88_8822BE=y
CONFIG_RTW88_8822CE=y
CONFIG_RTW88_DEBUG=y
CONFIG_RTW88_DEBUGFS=y

Jun Go (gojun077) wrote :

Hello Kai-Heng,

I edited the .config file in wireless-drivers-next and manually added the RTW88 drivers you mentioned above and then rebuilt the 5.3.0-rc1+ kernel.

After rebooting into the new kernel, I noticed that rtw88 and rtwpci kernel modules are now loaded but wifi is still not working... I have attached the output of lsmod, dmesg, and journalctl -b0 in a tarball.

Thanks for your help,
Jun

Kai-Heng Feng (kaihengfeng) wrote :

If latest driver doesn't work then we need help from Realtek. Please mail this issue to the following recipients:
Yan-Hsuan Chuang <email address hidden> (maintainer:REALTEK WIRELESS DRIVER (rtw88))
Kalle Valo <email address hidden> (maintainer:NETWORKING DRIVERS (WIRELESS))
"David S. Miller" <email address hidden> (odd fixer:NETWORKING DRIVERS)
<email address hidden> (open list:REALTEK WIRELESS DRIVER (rtw88))
<email address hidden> (open list:NETWORKING DRIVERS)
<email address hidden> (open list)

Jun Go (gojun077) wrote :

Hi Kai-Heng~

I sent the mail as you requested to the kernel module maintainers you mentioned above.

Cheers,
Jun

Andrew Hamilton (ahamilton9) wrote :

I'm having the same issues. Just wanted to add that kernel 5.0.0-25 was picked up on my Ubuntu Budgie system today so I tried it, but still had the same problems. Sticking to 5.0.0-13 for now. If there is anything I can do to help test let me know. I will be following this thread closely.

Mike R (m750luxx) wrote :

I can confirm this problem on Ubuntu 18.04 with kernel 5.0.0-23-generic. I'm on a Lenovo Thinkpad with r8822be wifi adapter.

Mike R (m750luxx) wrote :

I just updated updated 18.04 to kernel 5.0.0-25-generic and still no wifi.

Jarrod Farrell (jarrodmaddy) wrote :

Lenovo Thinkpad E585 with r8822be adapter. 5.0.0-25 still has issues.
Staying on 5.0.0-20 until another kernel version comes out that fixes the issue.

Kai-Heng Feng (kaihengfeng) wrote :

Please test this patch:
https://lore.kernel.org/linux<email address hidden>/T/#m00317d33cee4010d265d1a543a9811ee06376f19

Andrew Hamilton (ahamilton9) wrote :

I have a lack of experience dealing with kernel modules, so I know there was a much easier way to build and test the module by itself, but I took the long route and it seems like a success.

Grabbed source for Ubuntu kernel package 5.0.0-25. Output mentioned patches to 5.0.0-25.26, if that means anything. Blacklisted r8822be, patched rtw88 with the requested patch, built everything, checked lsmod and see rtwpci/rtw88 instead of r8822be as intended, and wifi seems to be working! Only weird thing is when I built the kernel it started calling it version 5.0.18. I'm not really sure how kernel build versioning works, so let me know if I did something wrong.

As a verification I ran update-initramfs against 5.0.0-25-generic (no rtw88 patch) to apply the blacklist r8822be rule, loaded it, checked that it's using rtwpci/rtw88, and I get no wifi as expected. Another validation would be great, but it looks promising to me.

Andrew Hamilton (ahamilton9) wrote :

I get other errors that cause my desktop to freeze a few seconds after login on that kernel as I did when I tried 5.3.0-rc4 mainline, but I was able to at least see that the wifi did say it was connected with the kernel you provided.

Kai-Heng Feng (kaihengfeng) wrote :

Please test this kernel:
https://people.canonical.com/~khfeng/lp1838133-disco/

It's based on Linux v5.0.

Andrew Hamilton (ahamilton9) wrote :

Everything seems to be working as expected with that kernel on my system. Wifi is up, no panics or other issues.

description: updated
Seth Forshee (sforshee) on 2019-08-23
Changed in linux (Ubuntu Eoan):
status: Triaged → Fix Committed
Mike R (m750luxx) wrote :

I just updated my Thinkpad e585 to the latest bios and now the wifi is working.

George Nelson (deft) wrote :

I confirm that latest bios fixes the problem on 5.0.0-25 using rtw88. So the whole time it was related to the ACPI IVRS bug. I wonder how many of these little model-specific quirk work-arounds are sitting in the various kernel drivers.

Launchpad Janitor (janitor) wrote :
Download full text (12.7 KiB)

This bug was fixed in the package linux - 5.2.0-15.16

---------------
linux (5.2.0-15.16) eoan; urgency=medium

  * Packaging resync (LP: #1786013)
    - [Packaging] resync getabis

  * Change kernel compression method to improve boot speed (LP: #1840934)
    - [Packaging] add build dependencies for compression algorithms

linux (5.2.0-14.15) eoan; urgency=medium

  * eoan/linux: 5.2.0-14.15 -proposed tracker (LP: #1841159)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync getabis

  * Eoan update: v5.2.9 upstream stable release (LP: #1841110)
    - Revert "PCI: Add missing link delays required by the PCIe spec"
    - IIO: Ingenic JZ47xx: Set clock divider on probe
    - iio: cros_ec_accel_legacy: Fix incorrect channel setting
    - iio: imu: mpu6050: add missing available scan masks
    - iio: adc: gyroadc: fix uninitialized return code
    - iio: adc: max9611: Fix misuse of GENMASK macro
    - staging: gasket: apex: fix copy-paste typo
    - staging: wilc1000: flush the workqueue before deinit the host
    - staging: android: ion: Bail out upon SIGKILL when allocating memory.
    - Staging: fbtft: Fix probing of gpio descriptor
    - Staging: fbtft: Fix reset assertion when using gpio descriptor
    - crypto: ccp - Fix oops by properly managing allocated structures
    - crypto: ccp - Add support for valid authsize values less than 16
    - crypto: ccp - Ignore tag length when decrypting GCM ciphertext
    - driver core: platform: return -ENXIO for missing GpioInt
    - usb: usbfs: fix double-free of usb memory upon submiturb error
    - Revert "USB: rio500: simplify locking"
    - usb: iowarrior: fix deadlock on disconnect
    - sound: fix a memory leak bug
    - mmc: cavium: Set the correct dma max segment size for mmc_host
    - mmc: cavium: Add the missing dma unmap when the dma has finished.
    - loop: set PF_MEMALLOC_NOIO for the worker thread
    - bdev: Fixup error handling in blkdev_get()
    - Input: usbtouchscreen - initialize PM mutex before using it
    - Input: elantech - enable SMBus on new (2018+) systems
    - Input: synaptics - enable RMI mode for HP Spectre X360
    - coresight: Fix DEBUG_LOCKS_WARN_ON for uninitialized attribute
    - perf annotate: Fix s390 gap between kernel end and module start
    - perf db-export: Fix thread__exec_comm()
    - perf record: Fix module size on s390
    - x86/purgatory: Do not use __builtin_memcpy and __builtin_memset
    - x86/purgatory: Use CFLAGS_REMOVE rather than reset KBUILD_CFLAGS
    - genirq/affinity: Create affinity mask for single vector
    - gfs2: gfs2_walk_metadata fix
    - usb: host: xhci-rcar: Fix timeout in xhci_suspend()
    - usb: yurex: Fix use-after-free in yurex_delete
    - usb: typec: ucsi: ccg: Fix uninitilized symbol error
    - usb: typec: tcpm: free log buf memory when remove debug file
    - usb: typec: tcpm: remove tcpm dir if no children
    - usb: typec: tcpm: Add NULL check before dereferencing config
    - usb: typec: tcpm: Ignore unsupported/unknown alternate mode requests
    - can: rcar_canfd: fix possible IRQ storm on high load
    - can: flexcan: fix stop mode acknowledgment
    - can: flexcan: fix an use-after-free in flexcan_setup...

Changed in linux (Ubuntu Eoan):
status: Fix Committed → Fix Released
Changed in linux (Ubuntu Disco):
status: New → In Progress
Jimmy Gjersvold (chillabis) wrote :

I'm on Ubuntu 18.04.3 LTS and has this bug. My wifi worked fine on my Asus-rog-strix-gl702zc-gc175t laptop until an recent 'sudo apt upgrade' to the latest kernel 5.0.0-27-generic.
Can't find any networks with it after the upgrade.

Please add Ubuntu 18.04.3 LTS to the list of fixing this!
Thank you!

Changed in linux (Ubuntu Disco):
status: In Progress → Fix Committed

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-disco' to 'verification-done-disco'. If the problem still exists, change the tag 'verification-needed-disco' to 'verification-failed-disco'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-disco
Jimmy Gjersvold (chillabis) wrote :

verification-failed-disco

Kai-Heng Feng (kaihengfeng) wrote :

Jimmy,

Can you please describe why it's failed? Have you enabled -proposed?

Jimmy Gjersvold (chillabis) wrote :

I got RTL8822BE. Does it use the same driver? Because i've been enabled -proposed and did a sudo update and a sudo upgrade but it didn't fix it for me. I don't know what logs to paste, can you help?
Oh one other thing a guy on #ubuntu@Freenode said that Bionic uses the same hwe kernel as Disco. And i'm on Bionic.

Kai-Heng Feng (kaihengfeng) wrote :

Can you please attach `sudo lspci -k` and `dmesg`? Thanks.

To post a comment you must log in.