Bug 1464731 - Wifi not working at all on new Lenovo E570p - Realtek RTL8822BE
Summary: Wifi not working at all on new Lenovo E570p - Realtek RTL8822BE
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 27
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Stanislaw Gruszka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-25 07:27 UTC by trevor
Modified: 2018-02-20 22:55 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-20 22:55:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Full dmesg output from v2 build (117.11 KB, text/plain)
2017-10-21 05:03 UTC, trevor
no flags Details
Kernel configuration file (188.04 KB, text/plain)
2017-10-22 04:34 UTC, trevor
no flags Details

Description trevor 2017-06-25 07:27:31 UTC
Description of problem:
Wifi card is not detected properly on Lenovo E570p notebook.

The documentation says this is:
Realtek® RTL8822BE, Wi-Fi 2x2 802.11ac + BT4.1, M.2 card

Seems listed in lspci as b822

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 05)
00:01.1 PCI bridge: Intel Corporation Skylake PCIe Controller (x8) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Device 591b (rev 04)
00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1)
00:1c.3 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #4 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #13 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Device a171 (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
02:00.0 3D controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] (rev ff)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device b822
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)
06:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961
07:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)



Version-Release number of selected component (if applicable):


How reproducible:
Everytime


Steps to Reproduce:
1. Boot computer
2. Try to connect to wifi
3. 

Actual results:
No Wifi available

Expected results:
Wifi available.

Additional info:

The only reference I could find was here : https://github.com/rtlwifi-linux/rtlwifi-next
but I don't know what that all means.

Comment 1 trevor 2017-06-25 07:31:32 UTC
Not sure if this https://github.com/lwfinger/rtlwifi_new/issues/233 is relevant.

Comment 2 Stanislaw Gruszka 2017-10-19 11:17:12 UTC
We have staging driver for rtl8822be device. We already enabled some staging Realtek driver on Fedora so perhaps we could enable this one as well.

I will provide fedora-kernel with the driver for test.

Comment 3 Stanislaw Gruszka 2017-10-19 14:26:49 UTC
Here is kernel with the driver enabled.  It is rawhide 4.14 kernel as driver is not present in 4.13 kernel. It should be installable on older fedoras via "rpm -ivh --force ...":

https://koji.fedoraproject.org/koji/taskinfo?taskID=22548318

You might need to update linux-firmware as well to assure needed rtl8822be*.bin image is there:

https://koji.fedoraproject.org/koji/buildinfo?buildID=983986

Please test.

Comment 4 trevor 2017-10-19 22:04:41 UTC
Downloaded and installed the kernel as suggested.
> rpm -ivh --force kernel-4.14.0-0.rc5.git2.1.r8822be.fc28.x86_64.rpm kernel-core-4.14.0-0.rc5.git2.1.r8822be.fc28.x86_64.rpm kernel-modules-4.14.0-0.rc5.git2.1.r8822be.fc28.x86_64.rpm

Rebooted to new kernel.

Wifi started and associated but then failed, system hang for some seconds while wifi failed:

dmesg output :

[   16.784441] wlp4s0: authenticate with 60:e3:27:44:20:62
[   16.829817] wlp4s0: send auth to 60:e3:27:44:20:62 (try 1/3)
[   16.831945] wlp4s0: authenticated
[   16.833246] wlp4s0: associate with 60:e3:27:44:20:62 (try 1/3)
[   16.842379] wlp4s0: RX AssocResp from 60:e3:27:44:20:62 (capab=0x431 status=0 aid=3)
[   16.843029] wlp4s0: associated
[   16.843122] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[   17.202948] NetworkManager (1458) used greatest stack depth: 11744 bytes left
[   22.645593] fuse init (API version 7.26)
[   23.661312] Bluetooth: RFCOMM TTY layer initialized
[   23.661327] Bluetooth: RFCOMM socket layer initialized
[   23.661460] Bluetooth: RFCOMM ver 1.11
[   25.167522] rfkill: input handler disabled
[   25.583623] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
[   25.583631] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
[   25.583648] pcieport 0000:00:1c.2:   device [8086:a112] error status/mask=00001000/00002000
[   25.583652] pcieport 0000:00:1c.2:    [12] Replay Timer Timeout  
[   36.191270] r8822be: AP off, try to reconnect now
[   36.191834] wlp4s0: Connection to AP 60:e3:27:44:20:62 lost
[   75.452557] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
[   83.361963] r8822be: [ERR]Pwr cmd polling timeout!!
[   83.362004] r8822be: [ERR]Pwr cmd offset : 5!!
[   83.362014] r8822be: [ERR]Pwr cmd value : 0!!
[   83.362022] r8822be: [ERR]Pwr cmd msk : 2!!
[   83.362030] r8822be: [ERR]Read offset = 5 value = 2!!
[   83.362039] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[   83.362047] r8822be: Handle power off cmd error
[   83.385434] r8822be: halmac_init_hal failed
[   85.968474] rfkill: input handler enabled
[  100.861399] rfkill: input handler disabled

Comment 5 trevor 2017-10-19 22:33:15 UTC
Also tried with module options : 
 cat rtl8822be.conf 
options r8822be fwlps=0 ips=0

Still crashed, but I did find some more info in dmesg: 

r8822be 0000:04:00.0: DMA-API: device driver frees DMA memory with different size [device address=0x0000000078477000] [map size=4096 bytes] [unmap size=424 bytes]
[    9.158917] ------------[ cut here ]------------
[    9.158921] WARNING: CPU: 6 PID: 811 at lib/dma-debug.c:1112 check_unmap+0x256/0x860
[    9.158923] Modules linked in: ebtable_filter(+) ebtables ip6table_filter ip6_tables binfmt_misc cmac bnep sunrpc vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel intel_cstate arc4 intel_uncore iTCO_wdt iTCO_vendor_support intel_rapl_perf r8822be(C) snd_hda_codec_hdmi snd_hda_codec_conexant snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device uvcvideo snd_pcm cfg80211 videobuf2_vmalloc videobuf2_memops wmi_bmof videobuf2_v4l2 videobuf2_core videodev joydev snd_timer media i2c_i801 btusb hci_uart btrtl mei_me ucsi_acpi btbcm btqca mei btintel bluetooth intel_pch_thermal shpchp typec_ucsi typec thinkpad_acpi snd soundcore intel_lpss_acpi ecdh_generic pinctrl_sunrisepoint
[    9.159004]  rfkill intel_lpss tpm_crb pinctrl_intel tpm_tis tpm_tis_core tpm acpi_pad hid_microsoft nouveau i915 mxm_wmi ttm i2c_algo_bit sdhci_pci drm_kms_helper crc32c_intel sdhci nvme mmc_core r8169 serio_raw nvme_core drm mii hid_logitech ff_memless wmi video i2c_hid
[    9.159076] CPU: 6 PID: 811 Comm: NetworkManager Tainted: G        WC      4.14.0-0.rc5.git2.1.r8822be.fc28.x86_64 #1
[    9.159078] Hardware name: LENOVO 20JAA00EAU/20JAA00EAU, BIOS R0MET29W (1.06) 01/19/2017
[    9.159079] task: ffff8b59d8b23380 task.stack: ffffa58a029b4000
[    9.159082] RIP: 0010:check_unmap+0x256/0x860
[    9.159083] RSP: 0018:ffffa58a029b71e8 EFLAGS: 00010082
[    9.159086] RAX: 00000000000000a2 RBX: ffff8b59d65cc3c0 RCX: 0000000000000000
[    9.159087] RDX: 0000000000000000 RSI: ffff8b59debce3c8 RDI: ffff8b59debce3c8
[    9.159089] RBP: ffffa58a029b7230 R08: 0000000000000001 R09: 0000000000000001
[    9.159090] R10: ffffa58a029b7148 R11: 0000000000000000 R12: ffffffff8f61a8d0
[    9.159091] R13: 0000000000000086 R14: ffffa58a029b7240 R15: 00000000000001a8
[    9.159093] FS:  00007f34584e1980(0000) GS:ffff8b59dea00000(0000) knlGS:0000000000000000
[    9.159094] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    9.159095] CR2: 00005586ed0a0a40 CR3: 00000004469da001 CR4: 00000000003606e0
[    9.159097] Call Trace:
[    9.159103]  debug_dma_unmap_page+0xa5/0xb0
[    9.159112]  ? unmap_single+0x2f/0x40
[    9.159123]  _rtl8822be_send_bcn_or_cmd_packet+0x2c5/0x300 [r8822be]
[    9.159129]  ? _rtl8822be_send_bcn_or_cmd_packet+0x2c5/0x300 [r8822be]
[    9.159139]  rtl8822b_halmac_cb_write_data_rsvd_page+0x51/0xc0 [r8822be]
[    9.159149]  _halmac_write_data_rsvd_page+0x22/0x30 [r8822be]
[    9.159158]  halmac_download_rsvd_page_88xx+0xee/0x1f0 [r8822be]
[    9.159168]  halmac_dlfw_to_mem_88xx+0x80/0x120 [r8822be]
[    9.159178]  halmac_download_firmware_88xx.part.47+0x477/0x600 [r8822be]
[    9.159192]  halmac_download_firmware_88xx+0x32/0x40 [r8822be]
[    9.159200]  rtl_halmac_dlfw+0x70/0x120 [r8822be]
[    9.159210]  rtl_halmac_init_hal+0x5f/0x1b0 [r8822be]
[    9.159218]  rtl8822be_hw_init+0x8a2/0x1040 [r8822be]
[    9.159226]  rtl_pci_start+0x77/0x150 [r8822be]
[    9.159232]  rtl_op_start+0x59/0x90 [r8822be]
[    9.159248]  drv_start+0x69/0x290 [mac80211]
[    9.159259]  ieee80211_do_open+0x3e3/0x900 [mac80211]
[    9.159263]  ? mutex_unlock+0x12/0x20
[    9.159273]  ieee80211_open+0x52/0x60 [mac80211]
[    9.159286]  __dev_open+0xc4/0x150
[    9.159290]  __dev_change_flags+0x1a7/0x1e0
[    9.159294]  dev_change_flags+0x29/0x60
[    9.159298]  do_setlink+0x2fa/0xe60
[    9.159303]  ? __lock_acquire+0x2d4/0x1320
[    9.159307]  ? sched_clock+0x9/0x10
[    9.159311]  ? __lock_acquire+0x2d4/0x1320
[    9.159316]  ? nla_parse+0x35/0x110
[    9.159320]  rtnl_newlink+0x5d4/0x900
[    9.159345]  ? __lock_is_held+0x65/0xb0
[    9.159350]  rtnetlink_rcv_msg+0x28a/0x640
[    9.159356]  ? rtnl_calcit.isra.23+0x1f0/0x1f0
[    9.159360]  netlink_rcv_skb+0x91/0x130
[    9.159365]  rtnetlink_rcv+0x15/0x20
[    9.159367]  netlink_unicast+0x20b/0x300
[    9.159371]  netlink_sendmsg+0x2d2/0x3d0
[    9.159378]  sock_sendmsg+0x38/0x50
[    9.159381]  ___sys_sendmsg+0x29d/0x2f0
[    9.159389]  ? sched_clock+0x9/0x10
[    9.159392]  ? __fget+0xf5/0x200
[    9.159398]  ? __fget+0x114/0x200
[    9.159404]  __sys_sendmsg+0x54/0x90
[    9.159406]  ? __sys_sendmsg+0x54/0x90
[    9.159414]  SyS_sendmsg+0x12/0x20
[    9.159416]  entry_SYSCALL_64_fastpath+0x1f/0xbe
[    9.159418] RIP: 0033:0x7f3456d72134
[    9.159419] RSP: 002b:00007ffd4eacb610 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
[    9.159422] RAX: ffffffffffffffda RBX: 0000557c985892b9 RCX: 00007f3456d72134
[    9.159423] RDX: 0000000000000000 RSI: 00007ffd4eacb660 RDI: 0000000000000007
[    9.159424] RBP: 00007ffd4eacbaf0 R08: 0000000000000000 R09: 0000557c9a28bd10
[    9.159426] R10: 00007f3455137b38 R11: 0000000000000293 R12: 0000000000000001
[    9.159427] R13: 0000000000000001 R14: 00007ffd4eacb820 R15: 0000557c988025a0
[    9.159435] Code: 48 89 4d c8 4c 89 45 d0 e8 f8 6b 15 00 4c 8b 45 d0 48 8b 4d c8 48 8b 55 c0 4d 89 f9 48 89 c6 48 c7 c7 70 6b d0 8d e8 db c8 c2 ff <0f> ff 48 89 df e8 23 17 00 00 8b 0d 12 8d c7 00 85 c9 0f 85 fc 
[    9.159508] ---[ end trace 0bea21a5333fbf16 ]---
[    9.159510] Mapped at:
[    9.159512]  debug_dma_map_page+0x87/0x140
[    9.159519]  rtl8822be_tx_fill_special_desc+0x115/0x3a0 [r8822be]
[    9.159524]  _rtl8822be_send_bcn_or_cmd_packet+0xfe/0x300 [r8822be]
[    9.159530]  rtl8822b_halmac_cb_write_data_rsvd_page+0x51/0xc0 [r8822be]
[    9.159537]  _halmac_write_data_rsvd_page+0x22/0x30 [r8822be]
[    9.629570] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
[   10.079002] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
[   10.134852] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
[   10.206400] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   10.508361] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[   10.633091] Netfilter messages via NETLINK v0.30.
[   10.639024] ip_set: protocol 6
[   11.250810] tun: Universal TUN/TAP device driver, 1.6
[   11.253421] virbr0: port 1(virbr0-nic) entered blocking state
[   11.253425] virbr0: port 1(virbr0-nic) entered disabled state
[   11.253626] device virbr0-nic entered promiscuous mode
[   11.405117] virbr0: port 1(virbr0-nic) entered blocking state
[   11.405131] virbr0: port 1(virbr0-nic) entered listening state
[   11.474547] virbr0: port 1(virbr0-nic) entered disabled state
[   11.802045] usb 1-5: new high-speed USB device number 8 using xhci_hcd
[   11.928397] usb 1-5: New USB device found, idVendor=2357, idProduct=0101
[   11.928401] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.928404] usb 1-5: Product: 802.11n NIC
[   11.928406] usb 1-5: Manufacturer: Realtek
[   11.928408] usb 1-5: SerialNumber: 123456
[   16.527680] r8822be: [ERR]Pwr cmd polling timeout!!
[   16.527709] r8822be: [ERR]Pwr cmd offset : 5!!
[   16.527715] r8822be: [ERR]Pwr cmd value : 0!!
[   16.527721] r8822be: [ERR]Pwr cmd msk : 2!!
[   16.527726] r8822be: [ERR]Read offset = 5 value = 2!!
[   16.527732] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[   16.527737] r8822be: Handle power off cmd error
[   16.529872] r8822be: halmac_init_hal failed

Comment 6 Stanislaw Gruszka 2017-10-20 12:21:53 UTC
I disabled DMA_API_DEBUG which cause problems as it deliberately make some DMA allocations fails, for what the driver is not prepared. New v2 build is here:

https://koji.fedoraproject.org/koji/taskinfo?taskID=22566871

Please report back as this one works.

Comment 7 trevor 2017-10-21 05:02:08 UTC
Had the same errors with v2 build. :(

Additional error seen in dmesg output repeating many times before final crash. 

[   64.439467] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
[   64.439475] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
[   64.439480] pcieport 0000:00:1c.2:   device [8086:a112] error status/mask=00001000/00002000
[   64.439483] pcieport 0000:00:1c.2:    [12] Replay Timer Timeout  

Same final error as before

[   64.439467] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
[   64.439475] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
[   64.439480] pcieport 0000:00:1c.2:   device [8086:a112] error status/mask=00001000/00002000
[   64.439483] pcieport 0000:00:1c.2:    [12] Replay Timer Timeout  
[   90.687901] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
[   90.687932] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
[   90.687952] pcieport 0000:00:1c.2:   device [8086:a112] error status/mask=00001000/00002000
[   90.687969] pcieport 0000:00:1c.2:    [12] Replay Timer Timeout  
[  116.918717] pcieport 0000:00:1c.2: AER: Corrected error received: id=00e2
[  116.918730] pcieport 0000:00:1c.2: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e2(Transmitter ID)
[  116.918739] pcieport 0000:00:1c.2:   device [8086:a112] error status/mask=00001000/00002000
[  116.918746] pcieport 0000:00:1c.2:    [12] Replay Timer Timeout  
[  197.408051] r8822be: AP off, try to reconnect now
[  197.408713] wlp4s0: Connection to AP 60:e3:27:44:20:62 lost
[  227.033291] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready
[  231.332664] r8822be: [ERR]Pwr cmd polling timeout!!
[  231.332714] r8822be: [ERR]Pwr cmd offset : 5!!
[  231.332723] r8822be: [ERR]Pwr cmd value : 0!!
[  231.332731] r8822be: [ERR]Pwr cmd msk : 2!!
[  231.332739] r8822be: [ERR]Read offset = 5 value = 2!!
[  231.332747] r8822be: [Err]pwr sub seq parser fail, status = 0x28!
[  231.332756] r8822be: Handle power off cmd error
[  231.375115] r8822be: halmac_init_hal failed

Comment 8 trevor 2017-10-21 05:03:35 UTC
Created attachment 1341491 [details]
Full dmesg output from v2 build

Attached full dmesg output

Comment 9 Stanislaw Gruszka 2017-10-21 07:28:02 UTC
Regarding errors we would need Realtek support for those.

Regarding crash, please switch to terminal from XWindow (via CTRL+ALT+F2) wait until the crash and provide photo of printed messages. There are other methods for provide crash informations like kdump or netconsole, but picture of terminal messages should be sufficient if it works.

Comment 10 trevor 2017-10-21 23:58:32 UTC
"crash".  I probably used the wrong word. I just mean the "Replay Timer Error" occurred many times before the fatal "r8822be: [ERR]Pwr cmd polling timeout!!" message and wifi stopping.  The machine did not actually crash.

Comment 11 Larry Finger 2017-10-22 00:10:41 UTC
Please be precise when making bug reports.

I am running a 4.14-rc4 system here, and I see neither the splat about size differences during buffer unmap, nor any PCI errors.

Could either of you please post the configuration file?

Thanks, Larry

Comment 12 trevor 2017-10-22 00:13:50 UTC
Larry, I'm just a poorly end user and don't know what configuration file you are referring to, but am happy to do what I can if you can give me some instructions on what you need.

Comment 13 Larry Finger 2017-10-22 01:40:31 UTC
You should have a file /boot/config-xxxxx, where xxxxx matches the output of the 'uname -r' command. That is the file I need.

Comment 14 trevor 2017-10-22 04:34:54 UTC
Created attachment 1341725 [details]
Kernel configuration file

Comment 15 Stanislaw Gruszka 2017-10-23 09:25:17 UTC
Regarding DMA-API size splat skb->len is used instead of pskb->len . I don't think it causes failure of the driver, but I'll provide kernel to test.

However there is worst thing than that, DMA mapping failures are not handed correctly and this seems to be problem with all rtlwifi drivers. Fortunately dma mappings can only fail when IOMMU is enabled or when DMA_API_DEBUG is enabled.

Comment 16 Stanislaw Gruszka 2017-10-23 12:30:56 UTC
Trevor, 

below is kernel with the DMA len fix (I posted it here: 
http://driverdev.linuxdriverproject.org/pipermail/driverdev-devel/2017-October/112676.html).  I don't think the patch fixes the overall malfunction, but you can try it, thanks:

https://koji.fedoraproject.org/koji/taskinfo?taskID=22645889

Comment 17 Stanislaw Gruszka 2017-10-24 09:33:33 UTC
One more thing. Since we have those PCIe bus error's I would check if there is BIOS update available to the laptop and if it is - update it.

If the above kernel and BIOS update will not help, than Larry hopefully could ask his contacts at Realtek for support.

Comment 18 trevor 2017-10-24 22:00:28 UTC
Today, I updated to latest BIOS. There did not seem to be anything in the BIOS release notes that indicated any relevant changes to WIFI chipset or anything else related and as expected I did not see any change in behaviour, that is WIFI still fails with same errors as before.

Comment 19 Larry Finger 2017-10-24 23:24:03 UTC
I have completed my tests here with the Redhat configuration, and I have added all IOMMU options as well as DMA_API_DEBUG. I never see any error messages.

I will have the Realtek crew look at this. They may even have access to a Lenovo E570p, which I do not.

Comment 20 Larry Finger 2017-10-25 15:42:27 UTC
Realtek does not have access to a Lenovo E570p, but they have seen the problem with a different Lenovo model. Please try loading the module with ASPM disabled. The command sequence is

sudo modprobe -rv r8822be
sudo modprobe -v r8822be aspm=0

If that helps, then use your favorite editor (as root) to create a file /etc/modprobe.d/50-r8822be.conf. This file should contain a single line
"options r8822be aspm=0". Do not include the quotation marks.

Comment 21 trevor 2017-10-26 05:44:23 UTC
Added "options r8822be aspm=0" to /etc/modprobe.d/50-r8822be.conf and now wifi is working without any issues as far as I can tell.  I have been using it without error for about 25 minutes and can't see any errors in the logs.

I will continue testing with this kernel, "4.14.0-0.rc5.git2.1.r8822be_v3.fc28.x86_64" and report back if I find any issues .

Thanks everyone.

Comment 22 trevor 2017-10-30 06:40:55 UTC
I have been testing for the last few days and had no issues with the on board wifi. :) 

Should I close this bug or should I leave that until this reaches a stable kernel release in Fedora 28?

Comment 23 Stanislaw Gruszka 2017-10-30 11:40:31 UTC
CC fedora kernel maintainers, we need to enable the driver ( CONFIG_R8822BE ) in official build to close this bz. We should also apply the fix from comment 16 in the build.

Comment 24 Stanislaw Gruszka 2017-10-30 13:21:06 UTC
For the record: we have already enabled CONFIG_R8188EU, CONFIG_R8712U, CONFIG_R8723AU Realtek drivers from the staging. Enabling another one should be no problem. Bugs can be reported to me and Larry.

Comment 26 Justin M. Forbes 2017-10-30 16:55:57 UTC
This has been added to rawhide and should appear in 4.14-rc7

Comment 27 Laura Abbott 2018-02-20 19:59:24 UTC
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

Comment 28 trevor 2018-02-20 22:02:18 UTC
This is now working for me. Since Kernel 4.14 AFAICT

Comment 29 Laura Abbott 2018-02-20 22:55:57 UTC
Thanks for letting us know.


Note You need to log in before you can comment on or make changes to this bug.