November 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1192891] New: rtw89 warning: network stops
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192891 Bug ID: 1192891 Summary: rtw89 warning: network stops Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rgoldwyn(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 853877 --> http://bugzilla.opensuse.org/attachment.cgi?id=853877&action=edit complete dmesg Using the rtw89 driver in openSUSE TW crashes and network stops working. [ 39.257022] WARNING: CPU: 11 PID: 918 at net/mac80211/rx.c:4856 ieee80211_rx_ list+0x2ff/0xb30 [mac80211] [ 39.257078] Modules linked in: ccm rfcomm af_packet nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject n ft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_m angle ip6table_raw ip6table_security iptable_nat nf_nat nf_conntrack nf_defrag_i pv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter cmac algif_hash algif_skcipher af_alg bnep dmi_sysfs msr xfs dm_crypt essiv authenc t rusted asn1_encoder tee snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq _device cdc_ether usbnet r8152 mii btusb btrtl btbcm btintel bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev inte l_rapl_msr ecdh_generic mc snd_acp3x_pdm_dma snd_soc_dmic snd_acp3x_rn snd_soc_c ore snd_compress snd_pcm_dmaengine intel_rapl_common snd_ctl_led snd_hda_codec_r ealtek rtw89_pci [ 39.257140] snd_hda_codec_generic rtw89_core edac_mce_amd snd_hda_codec_hdmi kvm_amd snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi mac80211 kvm snd_hda_ codec snd_hda_core snd_hwdep irqbypass cfg80211 pcspkr joydev efi_pstore snd_pcm r8169 think_lmi thinkpad_acpi firmware_attributes_class wmi_bmof realtek snd_rn _pci_acp3x snd_pci_acp3x mdio_devres snd_timer i2c_piix4 libphy platform_profile ledtrig_audio ucsi_acpi typec_ucsi rfkill snd libarc4 typec roles soundcore ac tiny_power_button i2c_scmi nls_iso8859_1 acpi_cpufreq nls_cp437 button vfat fat fuse configfs ip_tables x_tables amdgpu drm_ttm_helper ttm iommu_v2 gpu_sched i2 c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul hid_multitouch syscopyar ea sysfillrect hid_generic sysimgblt ghash_clmulni_intel fb_sys_fops cec rc_core xhci_pci xhci_pci_renesas xhci_hcd drm sdhci_pci cqhci aesni_intel usbcore sdhc i nvme crypto_simd mmc_core ccp cryptd nvme_core serio_raw sp5100_tco wmi batter y video i2c_hid_acpi i2c_hid [ 39.257221] btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq sg dm_ multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua efivarfs [ 39.257234] CPU: 11 PID: 918 Comm: irq/93-rtw89_pc Tainted: G O 5.14.14-2-default #1 openSUSE Tumbleweed 9a729ff54296ee874d75ab64f4a670e3c7dca 0f8 [ 39.257241] Hardware name: LENOVO 21A0001KUS/21A0001KUS, BIOS R1MET35W (1.05 ) 04/23/2021 [ 39.257242] RIP: 0010:ieee80211_rx_list+0x2ff/0xb30 [mac80211] [ 39.257282] Code: 09 0f 86 08 03 00 00 80 3d 9e 6d 0a 00 00 75 8c 0f b6 55 4a 0f b6 f0 48 c7 c7 88 5d 56 c2 c6 05 87 6d 0a 00 01 e8 81 39 8d dc <0f> 0b e9 6b ff ff ff 4d 85 e4 74 30 49 8d 76 0a 4c 89 e7 e8 29 a5 [ 39.257285] RSP: 0018:ffffb7f88043cd20 EFLAGS: 00010282 [ 39.257288] RAX: 0000000000000000 RBX: ffff911d99200800 RCX: 0000000000000027 [ 39.257291] RDX: ffff9123120da948 RSI: 0000000000000001 RDI: ffff9123120da940 [ 39.257292] RBP: ffff911d061d4700 R08: ffff91232e2c1c28 R09: 00000000ffff7fff [ 39.257294] R10: ffff912311a40000 R11: ffff912311a40000 R12: 0000000000000000 [ 39.257295] R13: ffff911d061d4d00 R14: 0000000000000001 R15: ffffb7f88043cde8 [ 39.257297] FS: 0000000000000000(0000) GS:ffff9123120c0000(0000) knlGS:0000000000000000 [ 39.257300] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 39.257301] CR2: 00007f62b85139f0 CR3: 0000000516e10000 CR4: 0000000000750ee0 [ 39.257303] PKRU: 55555554 [ 39.257305] Call Trace: [ 39.257310] <IRQ> [ 39.257318] ? skb_release_data+0x12e/0x170 [ 39.257325] ? __iterate_interfaces+0x9f/0x110 [mac80211 71229b687734dd1cd023e96672b129b9cdbbd98d] [ 39.257365] ? rtw89_core_rx_stats+0xb0/0xb0 [rtw89_core 4eaf2fb1a345285a09cf7862b4300fd32637d713] [ 39.257379] ieee80211_rx_napi+0x34/0xa0 [mac80211 71229b687734dd1cd023e96672b129b9cdbbd98d] [ 39.257414] rtw89_core_rx+0x668/0x7b0 [rtw89_core 4eaf2fb1a345285a09cf7862b4300fd32637d713] [ 39.257427] ? __alloc_skb+0xe7/0x270 [ 39.257432] rtw89_pci_napi_poll+0x332/0x460 [rtw89_pci baadb5c855ca0a726ce5bc87eefd4a8c67d7787f] [ 39.257439] __napi_poll+0x2a/0x150 [ 39.257446] net_rx_action+0x24c/0x2a0 [ 39.257451] __do_softirq+0xc6/0x268 [ 39.257458] do_softirq+0x76/0x90 [ 39.257464] </IRQ> [ 39.257465] __local_bh_enable_ip+0x4b/0x50 [ 39.257468] rtw89_pci_interrupt_threadfn+0x12a/0x1c0 [rtw89_pci baadb5c855ca0a726ce5bc87eefd4a8c67d7787f] [ 39.257473] ? irq_forced_thread_fn+0x90/0x90 [ 39.257478] irq_thread_fn+0x20/0x60 [ 39.257482] irq_thread+0xcb/0x180 [ 39.257485] ? irq_thread_fn+0x60/0x60 [ 39.257488] ? irq_thread_check_affinity+0xf0/0xf0 [ 39.257492] kthread+0x127/0x150 [ 39.257498] ? set_kthread_struct+0x40/0x40 [ 39.257502] ret_from_fork+0x22/0x30 [ 39.257511] ---[ end trace f4f8d0cecd559f71 ]--- [ 321.470027] [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3 -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1192476] New: CONFIG_FORTIFY_SOURCE isn't enabled on TW kernels
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192476 Bug ID: 1192476 Summary: CONFIG_FORTIFY_SOURCE isn't enabled on TW kernels Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: tiwai(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Through the bug 1192473, we noticed that CONFIG_FORTIFY_SOURCE isn't enabled on master/stable branches yet consistently while it's been enabled on SLE15-SP3 and SP4 (via jsc#SLE-11598). On TW, it's enabled only on s390x and riscv. This looks like an oversight. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1192874] During OS booting, the loading installation system progress is very slow with Intel Alder Lake nonVpro system.
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192874 http://bugzilla.opensuse.org/show_bug.cgi?id=1192874#c1 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P5 - None --- Comment #1 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- (In reply to Luke Lin from comment #0) > I got patch files from Intel. May I submit these patch files to openSUSE? Yes. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192874] During OS booting, the loading installation system progress is very slow with Intel Alder Lake nonVpro system.
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192874 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 Petr Mladek <pmladek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |pmladek(a)suse.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 19 Nov '21

19 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c11 --- Comment #11 from Petr Mladek <pmladek(a)suse.com> --- There actually might be an "easier" solution to make the loglevel consistent. It would be be possible to remember the last loglevel in struct task_struct, and in per-CPU/per-irq-context variables. It can then be used for any follow up pr_cont() call. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c18 --- Comment #18 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jiri Slaby from comment #17) > Or is this host-setup-specific (maybe virtio-blk) memory corruption or > something? Fabian, can you try with virtio-scsi instead of virtio-blk? Something like: -drive file=/data/libvirt/disks/boo1192714.qcow2,if=none,id=hd -device virtio-scsi-pci,id=scsi -device scsi-hd,drive=hd Instead of: -blockdev driver=file,node-name=hd0-file,filename=/data/libvirt/disks/boo1192714.qcow2,cache.no-flush=on -blockdev driver=qcow2,node-name=hd0,file=hd0-file,cache.no-flush=on -device virtio-blk,id=hd0-device,drive=hd0,serial=hd0 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c17 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |CCB_Review? --- Comment #17 from Jiri Slaby <jslaby(a)suse.com> --- (In reply to Jan Kara from comment #16) > Hmm, I was trying for some time but for some reason the problem does not > reproduce for me when I run the VM from your image on my test host. Not sure > why is that. FWIW I cannot either. Neither with the provided qemu command line. I don't know what else can affect this. The host is TW with 5.15.2. Or is this host-setup-specific (maybe virtio-blk) memory corruption or something? Fabian, can you try with virtio-scsi instead of virtio-blk? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192714] [Build 20211114] podman tests triggering gpf in kernel 5.15.1
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192714 https://bugzilla.suse.com/show_bug.cgi?id=1192714#c16 --- Comment #16 from Jan Kara <jack(a)suse.com> --- Hmm, I was trying for some time but for some reason the problem does not reproduce for me when I run the VM from your image on my test host. Not sure why is that. I've also looked into the code and the refcounting of blkg's inside BFQ looks rather straightforward and I didn't find any problem there. Any chance for triggering a crashdump when the problem happens so that we can poke around memory? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1192767] Kernel boot logging gets mixed up when bringing up CPUs on SMP system
by bugzilla_noreply＠suse.com 18 Nov '21

18 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192767 https://bugzilla.suse.com/show_bug.cgi?id=1192767#c10 --- Comment #10 from Archie Cobbs <archie.cobbs(a)gmail.com> --- > That said. It would be easy to make the loglevel consistent here. But there will be another 2000 pr_cont() calls that might cause the same problem. And there is no simple generic solution. ��A journey of a thousand miles begins with a single step�� - Chinese proverb -- You are receiving this mail because: You are the assignee for the bug.

1 0