Bug#959757: This is a regression
Hi Peter, On Sun, May 02, 2021 at 05:32:19PM +0200, Peter Leipold wrote: > Hi, I'm the original reporter. FYI, the problem was fixed with one of the > kernel updates on last summer. It's stable since then. Thanks for reporting back! Regards, Salvatore
Bug#959757: This is a regression
Peter Leipold writes: > On 5/2/21 2:54 PM, Salvatore Bonaccorso wrote: > >> On Sun, Jul 05, 2020 at 01:15:38PM +0200, wf...@niif.hu wrote: >> >>> I started to see this problem after upgrading from 5.4.0-0.bpo.4-amd64 >>> to 5.5.0-0.bpo.2-amd64. It goes like: >> >> Do you still have the issue reproducible with a recent kernel from >> unstable or buster-backports? > > Hi, I'm the original reporter. FYI, the problem was fixed with one of > the kernel updates on last summer. It's stable since then. Hi, I certainly can't reproduce it with the current 5.10.24-1~bpo10+1. Not even with 5.10.13-1~bpo10+1, and I haven't got older logs anymore. -- Feri
Bug#959757: This is a regression
Hi, I'm the original reporter. FYI, the problem was fixed with one of the kernel updates on last summer. It's stable since then. Peter On 5/2/21 2:54 PM, Salvatore Bonaccorso wrote: Control: tags -1 + moreinfo On Sun, Jul 05, 2020 at 01:15:38PM +0200, wf...@niif.hu wrote: Control: found -1 5.5.0-0.bpo.2-amd64 I started to see this problem after upgrading from 5.4.0-0.bpo.4-amd64 to 5.5.0-0.bpo.2-amd64. It goes like: Do you still have the issue reproducible with a recent kernel from unstable or buster-backports? Regards, Salvatore
Processed: Re: Bug#959757: This is a regression
Processing control commands: > tags -1 + moreinfo Bug #959757 [src:linux] rtwpci: wifi unstable with Realtek 8822BE Added tag(s) moreinfo. -- 959757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959757 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#959757: This is a regression
Control: tags -1 + moreinfo On Sun, Jul 05, 2020 at 01:15:38PM +0200, wf...@niif.hu wrote: > Control: found -1 5.5.0-0.bpo.2-amd64 > > I started to see this problem after upgrading from 5.4.0-0.bpo.4-amd64 > to 5.5.0-0.bpo.2-amd64. It goes like: Do you still have the issue reproducible with a recent kernel from unstable or buster-backports? Regards, Salvatore
Bug#959757: This is a regression
Control: found -1 5.5.0-0.bpo.2-amd64 I started to see this problem after upgrading from 5.4.0-0.bpo.4-amd64 to 5.5.0-0.bpo.2-amd64. It goes like: [21825.096887] rtw_pci :04:00.0: start vif dc:f5:05:54:f6:0d on port 0 [21829.406272] wlo1: authenticate with 38:43:7d:8a:89:0e [21829.914017] wlo1: send auth to 38:43:7d:8a:89:0e (try 1/3) [21829.935816] wlo1: authenticated [21829.941105] wlo1: associate with 38:43:7d:8a:89:0e (try 1/3) [21829.984243] wlo1: RX AssocResp from 38:43:7d:8a:89:0e (capab=0x1511 status=0 aid=3) [21829.986178] rtw_pci :04:00.0: sta 38:43:7d:8a:89:0e joined with macid 0 [21830.045633] rtw_pci :04:00.0: wrong bfee role [21830.048864] wlo1: associated [21830.050828] [ cut here ] [21830.051893] invalid ra report c2h length [21830.052890] WARNING: CPU: 2 PID: 280 at drivers/net/wireless/realtek/rtw88/fw.c:117 rtw_fw_c2h_cmd_handle+0x11a/0x130 [rtw88] [21830.053924] Modules linked in: cmac bnep bbswitch(OE) snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp nls_ascii snd_soc_skl nls_cp437 snd_soc_hdac_hda vfat btusb snd_hda_ext_core fat btrtl snd_soc_sst_ipc snd_hda_codec_hdmi btbcm snd_soc_sst_dsp btintel ext4 snd_soc_acpi_intel_match x86_pkg_temp_thermal snd_soc_acpi snd_hda_codec_realtek intel_powerclamp rtwpci mbcache coretemp snd_soc_core snd_hda_codec_generic bluetooth jbd2 rtw88 ledtrig_audio snd_compress kvm_intel snd_hda_intel mac80211 drbg kvm snd_intel_dspcfg uvcvideo videobuf2_vmalloc irqbypass snd_hda_codec joydev videobuf2_memops ansi_cprng videobuf2_v4l2 asus_nb_wmi snd_hda_core cfg80211 videobuf2_common ecdh_generic intel_cstate asus_wmi snd_hwdep ecc intel_rapl_msr efi_pstore sparse_keymap intel_uncore videodev snd_pcm serio_raw intel_rapl_perf pcspkr snd_timer mc iTCO_wdt efivars wmi_bmof snd mei_me processor_thermal_device rfkill iTCO_vendor_support [21830.053944] soundcore hid_multitouch watchdog crc16 libarc4 intel_rapl_common mei int3403_thermal sg intel_soc_dts_iosf intel_pch_thermal ac int340x_thermal_zone tpm_crb tpm_tis tpm_tis_core tpm rng_core int3400_thermal evdev acpi_thermal_rel acpi_pad acpi_tad efivarfs ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_decompress zstd_compress raid6_pq libcrc32c crc32c_generic algif_skcipher af_alg dm_crypt dm_mod sd_mod hid_generic spi_pxa2xx_platform dw_dmac dw_dmac_core i2c_designware_platform i2c_designware_core i915 crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel ahci libahci i2c_algo_bit mxm_wmi drm_kms_helper xhci_pci xhci_hcd aesni_intel libata drm usbcore crypto_simd cryptd glue_helper scsi_mod i2c_hid i2c_i801 intel_lpss_pci hid intel_lpss idma64 usb_common mfd_core battery wmi video button [21830.063782] CPU: 2 PID: 280 Comm: kworker/u16:2 Tainted: G OE 5.5.0-0.bpo.2-amd64 #1 Debian 5.5.17-1~bpo10+1 [21830.064901] Hardware name: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FN_S430FN/X430FN, BIOS X430FN.308 05/28/2019 [21830.066026] Workqueue: phy0 rtw_c2h_work [rtw88] [21830.067158] RIP: 0010:rtw_fw_c2h_cmd_handle+0x11a/0x130 [rtw88] [21830.068241] Code: cc 35 00 00 e8 f7 33 0d 00 e9 77 ff ff ff 48 89 ee 4c 89 f7 e8 07 70 ff ff e9 67 ff ff ff 48 c7 c7 c1 e4 2d c1 e8 a1 6c 80 de <0f> 0b e9 54 ff ff ff e8 4a 6a 80 de 66 2e 0f 1f 84 00 00 00 00 00 [21830.069391] RSP: 0018:ac2d8073be30 EFLAGS: 00010286 [21830.070515] RAX: RBX: 93e3a126bfd8 RCX: [21830.071635] RDX: 93e3a5ca9740 RSI: 93e3a5c99a48 RDI: 93e3a5c99a48 [21830.072694] RBP: 93e39b91b000 R08: 0426 R09: 00aa [21830.073764] R10: R11: ac2da09d8220 R12: 93e3a0a65b78 [21830.074835] R13: 0006 R14: 93e3a0a61e60 R15: 93e3a0a65c30 [21830.075842] FS: () GS:93e3a5c8() knlGS: [21830.076866] CS: 0010 DS: ES: CR0: 80050033 [21830.077827] CR2: 558372174ed8 CR3: 00015540a004 CR4: 003606e0 [21830.078780] Call Trace: [21830.079736] ? skb_dequeue+0x52/0x60 [21830.080674] rtw_c2h_work+0x40/0x60 [rtw88] [21830.081602] process_one_work+0x1a7/0x360 [21830.082532] worker_thread+0x30/0x390 [21830.083458] ? create_worker+0x1a0/0x1a0 [21830.084385] kthread+0x112/0x130 [21830.085353] ? kthread_park+0x80/0x80 [21830.086276] ret_from_fork+0x35/0x40 [21830.087246] ---[ end trace defb67375a180861 ]--- [21831.010482] wlo1: deauthenticated from 38:43:7d:8a:89:0e (Reason: 2=PREV_AUTH_NOT_VALID) [21831.045061] rtw_pci :04:00.0: sta 38:43:7d:8a:89:0e with macid 0 left [21831.722504] wlo1: authenticate with 38:43:7d:8a:89:41 [21832.230266] wlo1: send auth to 38:43:7d:8a:89:41 (try 1/3) [21832.236978] wlo1: authenticated [21832.242505] wlo1: associating with AP with corrupt probe response [21832.247217] wlo1: associate with 38:43:7d:8a:89:41 (try 1/3) [21832.274448] wlo1: RX AssocResp from
