rtl8821ce locks up transmitter

nomorewindows · 2024-02-25 06:35:11

rtw_8821ce 0000:01:00.0: failed to send h2c command
rtw_8821ce 0000:01:00.0: failed to get tx report from firmware
rtw_8821ce 0000:01:00.0: timed out to flush queue 1
rtw_8821ce 0000:01:00.0: timed out to flush pci tx ring[1]

Sometimes while updating through pacman, file transfer will die, causing pacman to hang, probably does it on web browser too.

Maybe this is an upstream bug?

Using AUR rtl8821ce-dkms-git driver as it doesn't seem to be mainline kernel driver yet.

seth · 2024-02-25 09:08:17

Context…

A usual suspect could be NM's MAC altering scanning habits, so try a manual connection or wifi-menu
Another contender would be power saving (TLP, ASPM)
Finally something else might lock the bus (lspci -tvnn)

nomorewindows · 2024-02-26 06:40:22

seth wrote:

Context…
A usual suspect could be NM's MAC altering scanning habits, so try a manual connection or wifi-menu
Another contender would be power saving (TLP, ASPM)
Finally something else might lock the bus (lspci -tvnn)

Am using nm. Think I was trying to use connman/cmst but nothing shows up in wifi scan. Think there is something I have to install to make it work.

It possibly is resetting during power saving.

lspci -tvnn

+-1d.0-[01]----00.0  Realtek Semiconductor Co., Ltd. RTL8821CE 802.11ac PCIe Wireless Network Adapter [10ec:c821]

Looks like the bus is free.

Last edited by nomorewindows (2024-02-26 07:13:27)

seth · 2024-02-26 09:30:38

Try wifi-menu and

It possibly is resetting during power saving.

post a complete system journal covering the incident if you want informed input.
Right now this is just "At some point my wifi stopped working. Why?", https://bbs.archlinux.org/viewtopic.php?id=57855

nomorewindows · 2024-04-29 05:20:57

Not just on arch only.

https://forums.linuxmint.com/viewtopic.php?t=408218

Using the linux driver instead of the aur built one it looks like.

Using rtw88_8821ce driver located in linux modules. The guy suggests blacklisting the kernel driver.

But where's the driver I built? Hmm...

dkms status

Error! File dkms.conf does not exist.
File /var/lib/dkms/rtl8821ce/<version>/source/dkms.conf does not exist.

Last edited by nomorewindows (2024-04-29 05:30:35)

raindog1975 · 2024-04-29 07:00:53

Do you have linux*-headers installed, without that the dkms type drivers don't get installed ( ask me how I know

seth · 2024-04-29 07:07:23

https://aur.archlinux.org/packages/rtl8821ce-dkms-git
https://aur.archlinux.org/packages/rtl8 … ent-957878

modinfo rtl8821ce
pacman -Qs rtl8821ce

nomorewindows · 2024-04-29 16:10:59

raindog1975 wrote:

Do you have linux*-headers installed, without that the dkms type drivers don't get installed ( ask me how I know

Yes, do have headers installed.

nomorewindows · 2024-04-29 16:12:21

seth wrote:

https://aur.archlinux.org/packages/rtl8821ce-dkms-git
https://aur.archlinux.org/packages/rtl8 … ent-957878
modinfo rtl8821ce
pacman -Qs rtl8821ce

modinfo rtl8821ce

modinfo: ERROR: Module rtl8821ce not found!

pacman -Qs rtl8821ce

rtl8821ce-dkms-git

Last edited by nomorewindows (2024-04-29 16:13:17)

seth · 2024-04-29 16:51:53

https://wiki.archlinux.org/title/Dynami … ld_modules
Pay attention to erors and post the output.

According to upstream you should also blacklist rtw_8821ce (but if you don't have that other driver to pick the job, this will just prevent any use of the wifi chip)

nomorewindows · 2024-04-29 19:17:45

seth wrote:

https://wiki.archlinux.org/title/Dynami … ld_modules
Pay attention to erors and post the output.
According to upstream you should also blacklist rtw_8821ce (but if you don't have that other driver to pick the job, this will just prevent any use of the wifi chip)

Ok, so I looked at one of the logs and apparently the module is built. So yes it's in the module directory under dkms. And it's also in /usr/lib/modules/<kernel version>.... where I would expect it to be.

So maybe the blacklist is what I need to get it to prefer the built module over the linux kernel module.

When I first installed Arch on this computer, I don't think wifi would even work without the dkms module, and sometime later the driver must've been added to the linux kernel. And I've had to update the version of the dkms-git driver to the latest because it did have build errors back some time ago. So I checked and I'm at the latest git pull on the dkms driver.

seth · 2024-04-29 21:20:52

Does

modinfo rtl8821ce

now suggest the module is available?
If so, fee free to blacklist the other one and see what happens.

If it gets loaded but you've similar connection issues, please post the journal to illustrate them so we can understand what's going on.

raindog1975 · 2024-04-30 05:20:51

@seth, @nomorewindows,
since I have the same realtek garbage in one of my machines ( but in my case the dkms driver from AUR works without issuses ) i did a little digging:

the module being loaded is "8821ce" ( NOT "rtl8821ce" } , this is the output from my machine:

  [paul@arch-e210ma ~]$ modinfo rtl8821ce
modinfo: ERROR: Module rtl8821ce not found.
[paul@arch-e210ma ~]$ modinfo 8821ce
filename:       /lib/modules/6.8.7-arch1-2/updates/dkms/8821ce.ko.zst
version:        v5.5.2_34066.20200325_COEX20180712-3232
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     6818A4C8D5609CAA534A519
alias:          pci:v000010ECd0000C82Bsv*sd*bc*sc*i*
alias:          pci:v000010ECd0000C82Asv*sd*bc*sc*i*
alias:          pci:v000010ECd0000C821sv*sd*bc*sc*i*
alias:          pci:v000010ECd0000B821sv*sd*bc*sc*i*
depends:        cfg80211
retpoline:      Y
name:           8821ce
vermagic:       6.8.7-arch1-2 SMP preempt mod_unload 
sig_id:         PKCS#7
signer:         DKMS module signing key
sig_key:        09:E8:CE:B3:3F:E5:AC:FA:DE:FC:4B:37:84:DA:9B:19:52:CA:5B:E1
sig_hashalgo:   sha512
signature:      8A:9D:01:4B:E2:F1:69:70:DF:B9:51:5A:36:C9:15:9D:C1:6A:CD:AD:
                65:7E:40:F3:AB:4D:CA:84:0F:E1:DC:52:97:8B:24:A7:BE:77:57:21:
                3B:0D:55:DB:D9:12:BD:DA:0A:9B:52:79:19:89:6E:7E:3D:86:93:E6:
                4E:9B:8D:EC:48:88:B3:BC:0C:6D:66:B1:E1:B8:B0:F2:84:1D:4D:67:
                0E:2E:DA:2C:AE:0E:CE:80:87:2D:E8:47:37:AD:C6:A5:C5:CD:6C:C0:
                E0:51:CD:C1:4D:BF:52:DE:F7:7F:BE:80:F0:6F:33:67:72:5A:5F:23:
                37:4E:82:12:EF:81:2F:E1:6A:36:61:70:9F:A4:47:4C:22:46:92:86:
                FF:E7:25:68:7F:89:15:F8:02:E2:BF:12:82:2C:EE:47:EB:7E:CA:3D:
                DA:50:DB:E2:57:C5:56:2E:A3:7E:C8:92:61:3A:CE:12:6B:35:2C:8F:
                27:B7:12:0D:32:D9:67:A6:82:55:96:9D:BE:3F:71:2F:C1:5E:F0:0E:
                94:F7:9A:BE:86:DF:49:11:3A:D6:31:73:84:B6:87:FF:01:7E:A5:EC:
                CE:CD:94:5B:7C:C1:57:94:87:C2:66:60:8C:E7:36:C3:F1:0B:2C:DD:
                CE:00:82:67:1C:BA:E2:45:6F:C1:59:13:10:36:BF:44
parm:           rtw_wireless_mode:int
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           rtw_lps_level:The default LPS level (int)
parm:           rtw_lps_chk_by_tp:int
parm:           rtw_max_bss_cnt:int
parm:           rtw_usb_rxagg_mode:int
parm:           rtw_dynamic_agg_enable:int
parm:           rtw_tx_bw_mode:The max tx bw for 2.4G and 5G. format is the same as rtw_bw_mode (uint)
parm:           rtw_rx_ampdu_sz_limit_1ss:RX AMPDU size limit for 1SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_2ss:RX AMPDU size limit for 2SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_3ss:RX AMPDU size limit for 3SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_rx_ampdu_sz_limit_4ss:RX AMPDU size limit for 4SS link of each BW, 0xFF: no limitation (array of uint)
parm:           rtw_vht_enable:int
parm:           rtw_vht_rx_mcs_map:VHT RX MCS map (uint)
parm:           rtw_rf_config:int
parm:           rtw_country_code:The default country code (in alpha2) (charp)
parm:           rtw_channel_plan:The default chplan ID when rtw_alpha2 is not specified or valid (int)
parm:           rtw_excl_chs:exclusive channel array (array of uint)
parm:           rtw_btcoex_enable:BT co-existence on/off, 0:off, 1:on, 2:by efuse (int)
parm:           rtw_ant_num:Antenna number setting, 0:by efuse (int)
parm:           rtw_qos_opt_enable:int
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_pwrtrim_enable:int
parm:           rtw_initmac:charp
parm:           rtw_special_rf_path:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_uapsd_max_sp:int
parm:           rtw_uapsd_ac_enable:int
parm:           rtw_wmm_smart_ps:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_bw_mode:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_rx_ampdu_amsdu:int
parm:           rtw_tx_ampdu_amsdu:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_power_mgnt:int
parm:           rtw_smart_ps:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_full_ch_in_p2p_handshake:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_antdiv_type:int
parm:           rtw_drv_ant_band_switch:int
parm:           rtw_single_ant_path:int
parm:           rtw_switch_usb_mode:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_check_hw_status:int
parm:           rtw_pci_aspm_enable:int
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_mc2u_disable:int
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
parm:           rtw_hiq_filter:0:allow all, 1:allow special, 2:deny all (uint)
parm:           rtw_adaptivity_en:0:disable, 1:enable (uint)
parm:           rtw_adaptivity_mode:0:normal, 1:carrier sense (uint)
parm:           rtw_adaptivity_th_l2h_ini:th_l2h_ini for Adaptivity (int)
parm:           rtw_adaptivity_th_edcca_hl_diff:th_edcca_hl_diff for Adaptivity (int)
parm:           rtw_amplifier_type_2g:BIT3:2G ext-PA, BIT4:2G ext-LNA (uint)
parm:           rtw_amplifier_type_5g:BIT6:5G ext-PA, BIT7:5G ext-LNA (uint)
parm:           rtw_RFE_type:default init value:64 (uint)
parm:           rtw_powertracking_type:default init value:64 (uint)
parm:           rtw_GLNA_type:default init value:0 (uint)
parm:           rtw_TxBBSwing_2G:default init value:0xFF (uint)
parm:           rtw_TxBBSwing_5G:default init value:0xFF (uint)
parm:           rtw_OffEfuseMask:default open Efuse Mask value:0 (uint)
parm:           rtw_FileMaskEfuse:default drv Mask Efuse value:0 (uint)
parm:           rtw_rxgain_offset_2g:default RF Gain 2G Offset value:0 (uint)
parm:           rtw_rxgain_offset_5gl:default RF Gain 5GL Offset value:0 (uint)
parm:           rtw_rxgain_offset_5gh:uint
parm:           rtw_rxgain_offset_5gm:default RF Gain 5GM Offset value:0 (uint)
parm:           rtw_pll_ref_clk_sel:force pll_ref_clk_sel, 0xF:use autoload value (uint)
parm:           rtw_tx_pwr_by_rate:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_tx_pwr_lmt_enable:0:Disable, 1:Enable, 2: Depend on efuse (int)
parm:           rtw_target_tx_pwr_2g_a:2.4G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_b:2.4G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_c:2.4G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_2g_d:2.4G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_a:5G target tx power (unit:dBm) of RF path A for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_b:5G target tx power (unit:dBm) of RF path B for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_c:5G target tx power (unit:dBm) of RF path C for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_target_tx_pwr_5g_d:5G target tx power (unit:dBm) of RF path D for each rate section, should match the real calibrate power, -1: undefined (array of int)
parm:           rtw_tsf_update_pause_factor:num of bcn intervals to stay TSF update pause status (int)
parm:           rtw_tsf_update_restore_factor:num of bcn intervals to stay TSF update restore status (int)
parm:           rtw_phy_file_path:The path of phy parameter (charp)
parm:           rtw_load_phy_file:PHY File Bit Map (int)
parm:           rtw_decrypt_phy_file:Enable Decrypt PHY File (int)
parm:           rtw_en_napi:int
parm:           rtw_en_gro:int
parm:           rtw_iqk_fw_offload:int
parm:           rtw_ch_switch_offload:int

nomorewindows · 2024-05-02 15:41:49

I blacklisted all the rtw88_ and related modules.

They still load up and add the built module on top of it.

So both are loaded at the same time.

And still all the funky dmesg are there right from the reboot.

Last edited by nomorewindows (2024-05-02 15:42:25)

seth · 2024-05-02 18:48:06

The upstream suggestion would have to blacklist rtw_8821ce and if you add "module_blacklist=rtw_8821ce" to the https://wiki.archlinux.org/title/Kernel_parameters nothing is gonna load that module. Ever.

nomorewindows · 2024-05-05 18:31:54

seth wrote:

The upstream suggestion would have to blacklist rtw_8821ce and if you add "module_blacklist=rtw_8821ce" to the https://wiki.archlinux.org/title/Kernel_parameters nothing is gonna load that module. Ever.

Ok yeah that worked and it looks like putting blacklist rtw88_8821ce at the top of the blacklist makes it work from /etc/modprobe.d.

The rtw88_8821c module looks like it has to do with the embedded bluetooth, but the 8821ce module seems to have that in it, so disabling rtw88_8821c doesn't affect it, and probably needs to be blacklisted just to prevent any other problems.

8821ce and cfg80211 is all the modules showing for 8821 related now.

Will observe the behaviour of the built module for a little while and then possibly marked solved when everything looks good.

nomorewindows · 2024-05-06 19:36:28

Well guys there's no news like bad news. Apparently the stock kernel driver at least keeps running without going down, but the built driver gave me a nasty OOPS!

[89065.704631] BUG: kernel NULL pointer dereference, address: 0000000000000000
[89065.704645] #PF: supervisor read access in kernel mode
[89065.704650] #PF: error_code(0x0000) - not-present page
[89065.704654] PGD 0 P4D 0 
[89065.704661] Oops: 0000 [#1] PREEMPT SMP NOPTI
[89065.704668] CPU: 2 PID: 205088 Comm: kworker/u16:29 Tainted: G           OE      6.8.9-arch1-1 #1 b1154d98cdfe0792477fb31da8bf552e17e27d3c
[89065.704680] Workqueue: cfg80211 cfg80211_event_work [cfg80211]
[89065.704790] RIP: 0010:__cfg80211_connect_result+0x322/0x910 [cfg80211]
[89065.704907] Code: f6 74 1e 83 f9 0e 0f b7 d0 8d 79 01 40 0f 95 c6 48 0f a3 ca 0f 82 b1 01 00 00 89 f9 66 85 c0 75 dd 41 80 8c 24 a4 00 00 00 01 <41> 8b 06 4c 89 e9 31 d2 41 89 84 24 98 03 00 00 41 0f b7 46 04 66
[89065.704912] RSP: 0018:ffffac59c773fd90 EFLAGS: 00010202
[89065.704916] RAX: 0000000000000000 RBX: ffff9885f3c46818 RCX: 0000000000000001
[89065.704920] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff9884d5a4e6d8
[89065.704923] RBP: ffffac59c773fde0 R08: 0000000000000067 R09: fffffffeff428ee8
[89065.704927] R10: ffff98885fab4910 R11: ffff9884c3ed10c0 R12: ffff9884d5a4e000
[89065.704929] R13: ffff9884d5a4e408 R14: 0000000000000000 R15: 0000000000000001
[89065.704933] FS:  0000000000000000(0000) GS:ffff98885fa80000(0000) knlGS:0000000000000000
[89065.704937] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[89065.704940] CR2: 0000000000000000 CR3: 0000000224820004 CR4: 0000000000f70ef0
[89065.704943] PKRU: 55555554
[89065.704946] Call Trace:
[89065.704951]  <TASK>
[89065.704956]  ? __die+0x23/0x70
[89065.704967]  ? page_fault_oops+0x171/0x4e0
[89065.704976]  ? exc_page_fault+0x7f/0x180
[89065.704983]  ? asm_exc_page_fault+0x26/0x30
[89065.704993]  ? __cfg80211_connect_result+0x322/0x910 [cfg80211 b760b1c4368dc84454ca19e75c376d58ee3e0359]
[89065.705101]  ? finish_task_switch.isra.0+0x94/0x2f0
[89065.705111]  ? cfg80211_process_wdev_events+0x82/0x1a0 [cfg80211 b760b1c4368dc84454ca19e75c376d58ee3e0359]
[89065.705196]  cfg80211_process_wdev_events+0x82/0x1a0 [cfg80211 b760b1c4368dc84454ca19e75c376d58ee3e0359]
[89065.705280]  cfg80211_process_rdev_events+0x2a/0x40 [cfg80211 b760b1c4368dc84454ca19e75c376d58ee3e0359]
[89065.705364]  cfg80211_event_work+0x29/0x40 [cfg80211 b760b1c4368dc84454ca19e75c376d58ee3e0359]
[89065.705439]  process_one_work+0x178/0x350
[89065.705447]  worker_thread+0x30f/0x450
[89065.705453]  ? __pfx_worker_thread+0x10/0x10
[89065.705459]  kthread+0xe5/0x120
[89065.705466]  ? __pfx_kthread+0x10/0x10
[89065.705473]  ret_from_fork+0x31/0x50
[89065.705480]  ? __pfx_kthread+0x10/0x10
[89065.705487]  ret_from_fork_asm+0x1b/0x30
[89065.705494]  </TASK>
[89065.705496] Modules linked in: snd_seq_dummy snd_seq snd_seq_device nfnetlink_queue nfnetlink_log tls rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace sunrpc netfs snd_ctl_led ledtrig_audio snd_soc_skl_hda_dsp snd_soc_hdac_hdmi snd_soc_intel_hda_dsp_common snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_soc_dmic snd_sof_pci_intel_tgl snd_sof_intel_hda_common intel_uncore_frequency soundwire_intel intel_uncore_frequency_common snd_sof_intel_hda_mlink soundwire_cadence xe snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp x86_pkg_temp_thermal intel_powerclamp snd_sof coretemp drm_gpuvm snd_sof_utils drm_exec snd_soc_hdac_hda gpu_sched kvm_intel drm_suballoc_helper snd_hda_ext_core drm_ttm_helper ax88796b snd_soc_acpi_intel_match kvm snd_soc_acpi soundwire_generic_allocation soundwire_bus irqbypass snd_soc_core crct10dif_pclmul crc32_pclmul snd_compress uvcvideo btusb polyval_clmulni ac97_bus videobuf2_vmalloc polyval_generic btrtl snd_pcm_dmaengine gf128mul btintel uvc
[89065.705579]  snd_hda_intel ghash_clmulni_intel i915 snd_intel_dspcfg btbcm asix sha512_ssse3 videobuf2_memops btmtk usbnet videobuf2_v4l2 8821ce(OE) sha256_ssse3 snd_intel_sdw_acpi selftests sha1_ssse3 processor_thermal_device_pci_legacy joydev bluetooth snd_hda_codec aesni_intel videodev hid_multitouch hp_wmi phylink iTCO_wdt crypto_simd processor_thermal_device drm_buddy snd_hda_core videobuf2_common cryptd processor_thermal_wt_hint mii platform_profile i2c_algo_bit intel_pmc_bxt processor_thermal_rfim rapl snd_hwdep libphy intel_rapl_msr iTCO_vendor_support ee1004 wacom mei_pxp mousedev mei_hdcp ecdh_generic mc snd_pcm sparse_keymap ttm processor_thermal_rapl intel_cstate cfg80211 wmi_bmof snd_timer intel_rapl_common i2c_i801 drm_display_helper intel_lpss_pci mei_me spi_nor cec snd intel_uncore processor_thermal_wt_req mei pcspkr intel_lpss intel_gtt i2c_smbus rfkill processor_thermal_power_floor soundcore mtd idma64 processor_thermal_mbox intel_pmc_core intel_soc_dts_iosf int3403_thermal video int340x_thermal_zone
[89065.705671]  intel_vsec int3400_thermal wmi pmt_telemetry pinctrl_tigerlake acpi_pad acpi_thermal_rel pmt_class wireless_hotkey mac_hid pkcs8_key_parser crypto_user loop dm_mod nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 uas usb_storage hid_generic usbhid nvme nvme_core nvme_auth serio_raw atkbd libps2 vivaldi_fmap spi_intel_pci crc32c_intel xhci_pci i2c_hid_acpi spi_intel i8042 xhci_pci_renesas vmd i2c_hid serio
[89065.705723] CR2: 0000000000000000
[89065.705727] ---[ end trace 0000000000000000 ]---
[89065.705730] RIP: 0010:__cfg80211_connect_result+0x322/0x910 [cfg80211]
[89065.705830] Code: f6 74 1e 83 f9 0e 0f b7 d0 8d 79 01 40 0f 95 c6 48 0f a3 ca 0f 82 b1 01 00 00 89 f9 66 85 c0 75 dd 41 80 8c 24 a4 00 00 00 01 <41> 8b 06 4c 89 e9 31 d2 41 89 84 24 98 03 00 00 41 0f b7 46 04 66
[89065.705833] RSP: 0018:ffffac59c773fd90 EFLAGS: 00010202
[89065.705837] RAX: 0000000000000000 RBX: ffff9885f3c46818 RCX: 0000000000000001
[89065.705839] RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff9884d5a4e6d8
[89065.705841] RBP: ffffac59c773fde0 R08: 0000000000000067 R09: fffffffeff428ee8
[89065.705844] R10: ffff98885fab4910 R11: ffff9884c3ed10c0 R12: ffff9884d5a4e000
[89065.705847] R13: ffff9884d5a4e408 R14: 0000000000000000 R15: 0000000000000001
[89065.705849] FS:  0000000000000000(0000) GS:ffff98885fa80000(0000) knlGS:0000000000000000
[89065.705852] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[89065.705855] CR2: 0000000000000000 CR3: 0000000224820004 CR4: 0000000000f70ef0
[89065.705858] PKRU: 55555554
[89065.705860] note: kworker/u16:29[205088] exited with irqs disabled

seth · 2024-05-06 20:47:50

Is there more context to this?
Please post the entire system journal or at least 30 minutes before and after this
cfg80211 isn't your device driver and the actual problem happened likely before

nomorewindows · 2024-05-06 20:51:30

seth wrote:

Is there more context to this?
Please post the entire system journal or at least 30 minutes before and after this
cfg80211 isn't your device driver and the actual problem happened likely before

I had a pretty fresh reboot before.
Nothing was showing up besides the norm in dmesg whereas the stock kernel driver was spamming as soon as booted.
So the OOPS is the first new development.
Cfg80211 is the only other module tied to 8821ce.

Could open a terminal, and do top but browsers, ifconfig, ip addr all hanged.

Then when I tried to reboot, wpa_supplicant, a core dump, and a couple other processes were hung. Wouldn't reboot from that, so had to power off to reboot. Blacklisted all the wireless drivers for now and using a usb ethernet for now.

Last edited by nomorewindows (2024-05-06 21:03:36)

seth · 2024-05-06 21:15:04

Please post your complete system journal for the boot, eg.

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

for the previous ("-1") one.

nomorewindows · 2024-05-09 15:06:38

seth wrote:

Please post your complete system journal for the boot, eg.
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
for the previous ("-1") one.

PM'd the output link to you.

seth · 2024-05-09 15:23:43

May 06 14:26:52 archlinux kernel: Linux version 6.8.9-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20240417, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Thu, 02 May 2024 17:49:46 +0000
May 06 14:26:53 archlinux kernel: rtl8821ce 0000:01:00.0: enabling device (0000 -> 0003)
May 06 14:26:56 archlinux NetworkManager[719]: <info>  [1715023616.3775] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.0/0000:01:00.0/ieee80211/phy0/rfkill0) (driver rtl8821ce)

May 06 14:27:01 archlinux wpa_supplicant[753]: wlan0: CTRL-EVENT-CONNECTED - Connection to <bssid_1> completed [id=0 id_str=]
May 06 14:27:22 archlinux wpa_supplicant[753]: wlan0: CTRL-EVENT-DISCONNECTED bssid=<bssid_1> reason=3 locally_generated=1

The journal continues for three days afterwards but w/o ever accessing the WiFi NIC and relying on

May 06 14:26:55 archlinux kernel: asix 1-1.4:1.0 enp0s20f0u1u4: renamed from eth0

only.
There're no obvious kernel or other errors, you connected the wifi NIC, disconnected manually and then completely stopped using it.

Check the older boots, "-1" was an example - idk which was the actually affected boot.

nomorewindows · 2024-05-09 17:45:13

seth wrote:

May 06 14:26:52 archlinux kernel: Linux version 6.8.9-arch1-1 (linux@archlinux) (gcc (GCC) 13.2.1 20240417, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Thu, 02 May 2024 17:49:46 +0000
May 06 14:26:53 archlinux kernel: rtl8821ce 0000:01:00.0: enabling device (0000 -> 0003)
May 06 14:26:56 archlinux NetworkManager[719]: <info>  [1715023616.3775] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.0/0000:01:00.0/ieee80211/phy0/rfkill0) (driver rtl8821ce)

May 06 14:27:01 archlinux wpa_supplicant[753]: wlan0: CTRL-EVENT-CONNECTED - Connection to <bssid_1> completed [id=0 id_str=]
May 06 14:27:22 archlinux wpa_supplicant[753]: wlan0: CTRL-EVENT-DISCONNECTED bssid=<bssid_1> reason=3 locally_generated=1

The journal continues for three days afterwards but w/o ever accessing the WiFi NIC and relying on

May 06 14:26:55 archlinux kernel: asix 1-1.4:1.0 enp0s20f0u1u4: renamed from eth0

only.
There're no obvious kernel or other errors, you connected the wifi NIC, disconnected manually and then completely stopped using it.

Check the older boots, "-1" was an example - idk which was the actually affected boot.

I probably need to go back one or possibly two more. After it crashed/hung I rebooted and disabled all 8821 drivers and went with the USB ethernet device wired into the router. So I may need to go back 1 or 2.

nomorewindows · 2024-05-12 06:17:55

PM'd you a farther back dmesg on the stock kernel driver. It seems to be croaking during power state changes. Having trouble finding the bug on the built driver. Nothing really showing up.

These lines on a 8821ce boot look interesting.

bgscan simple: Failed to enable signal strength monitoring
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support bap plugin
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support bass plugin
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support mcp plugin
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support vcp plugin
May 05 13:19:12 archlinux bluetoothd[793]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support micp plugin
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support ccp plugin
May 05 13:19:12 archlinux bluetoothd[793]: src/plugin.c:init_plugin() System does not support csip plugin

This may differ between the two drivers.

seth · 2024-05-12 10:42:12

May 03 12:05:30 archlinux kernel: rtw_8821ce 0000:01:00.0: firmware failed to leave lps state

rtw_8821ce isn't blacklisted in the journal segment you sent?

These lines on a 8821ce boot look interesting.

And those are not in that journal.

Arch Linux

#1 2024-02-25 06:35:11

rtl8821ce locks up transmitter

#2 2024-02-25 09:08:17

Re: rtl8821ce locks up transmitter

#3 2024-02-26 06:40:22

Re: rtl8821ce locks up transmitter

#4 2024-02-26 09:30:38

Re: rtl8821ce locks up transmitter

#5 2024-04-29 05:20:57

Re: rtl8821ce locks up transmitter

#6 2024-04-29 07:00:53

Re: rtl8821ce locks up transmitter

#7 2024-04-29 07:07:23

Re: rtl8821ce locks up transmitter

#8 2024-04-29 16:10:59

Re: rtl8821ce locks up transmitter

#9 2024-04-29 16:12:21

Re: rtl8821ce locks up transmitter

#10 2024-04-29 16:51:53

Re: rtl8821ce locks up transmitter

#11 2024-04-29 19:17:45

Re: rtl8821ce locks up transmitter

#12 2024-04-29 21:20:52

Re: rtl8821ce locks up transmitter

#13 2024-04-30 05:20:51

Re: rtl8821ce locks up transmitter

#14 2024-05-02 15:41:49

Re: rtl8821ce locks up transmitter

#15 2024-05-02 18:48:06

Re: rtl8821ce locks up transmitter

#16 2024-05-05 18:31:54

Re: rtl8821ce locks up transmitter

#17 2024-05-06 19:36:28

Re: rtl8821ce locks up transmitter

#18 2024-05-06 20:47:50

Re: rtl8821ce locks up transmitter

#19 2024-05-06 20:51:30

Re: rtl8821ce locks up transmitter

#20 2024-05-06 21:15:04

Re: rtl8821ce locks up transmitter

#21 2024-05-09 15:06:38

Re: rtl8821ce locks up transmitter

#22 2024-05-09 15:23:43

Re: rtl8821ce locks up transmitter

#23 2024-05-09 17:45:13

Re: rtl8821ce locks up transmitter

#24 2024-05-12 06:17:55

Re: rtl8821ce locks up transmitter

#25 2024-05-12 10:42:12

Re: rtl8821ce locks up transmitter

Board footer