March 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208071] SELinux: restricting kernel_t causes issues for the way we setup Micro
by bugzilla_noreply＠suse.com 14 Mar '23

14 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208071 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 1208944] Kernel 6.2.0-1-default does not boot on tumbleweed
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208944 http://bugzilla.opensuse.org/show_bug.cgi?id=1208944#c17 --- Comment #17 from Pieter Terpstra <kesang.neljor(a)yahoo.com> --- It works on 6.2.5-1.g72ee280-default, meaning booting with both disks! Just had to find out how to dismantle the secure moktil/secureboot layers and turn it of in the BIOS, for some reason this was in the same moment. Thank you so much! -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208944] Kernel 6.2.0-1-default does not boot on tumbleweed
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208944 http://bugzilla.opensuse.org/show_bug.cgi?id=1208944#c16 --- Comment #16 from Pieter Terpstra <kesang.neljor(a)yahoo.com> --- Just booted with kernel-default-6.2.2-1.1.x86_64 and it still has the same problem as before. Two day's ago i booted with the kernel-default-6.2.4-1.1.g0532a55.x86_64 from the Kernel:Stable repository and that did not wanted to boot either for a different reason (started with a BIOS or shim screen and than said that it could not load the kernel). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1208362] nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208362 Chenzi Cao <chcao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Basesystem |Kernel 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 1207915] amdgpu 0000:00:01.0: amdgpu: GPU fault detected: 147 0x00422002 for process sddm-greeter pid 2186 thread sddm-greet:cs0 pid 2193
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1207915 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 1209006] Document how to secureboot-sign manually-built kernel modules on TW kernel >= 6.2.1
by bugzilla_noreply＠suse.com 13 Mar '23

13 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209006 https://bugzilla.suse.com/show_bug.cgi?id=1209006#c29 --- Comment #29 from Joey Lee <jlee(a)suse.com> --- (In reply to Jiri Slaby from comment #17) > (In reply to Stefan Dirsch from comment #14) > > > But we will need to change the rpm scripts of Nvidia driver again when Eric > > > Snowberg's patch set be merged on mainline if we want to follow upstream's > > > approach. > > > > Ok. But I need to know in which way. And I would like to have the time to > > prepare this beforehand ... > > Ok, this is enough. > > commit 44ca817f15b215421a4c788790dd5351c186d1df (HEAD -> stable, > origin/users/jslaby/stable/for-next) > Author: Jiri Slaby <jslaby(a)suse.cz> > Date: Thu Mar 9 07:01:29 2023 +0100 > > Disable lockdown. (bsc#1209006) > > This somehow doesn't play good wrt to external modules. > > When all is ready again, we can revert this revert. > > > master still have the patchset enabled, we can tune there... I have sent new change to master/for-next. I port the KEYS-Make-use-of-platform-keyring-for-module-signatu.patch patch, and also set CONFIG_IMA_SECURE_AND_OR_TRUSTED_BOOT=y to detect secure boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1189826] New: Severe screen flickering with kernel 5.13.12-1-default and i915
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1189826 Bug ID: 1189826 Summary: Severe screen flickering with kernel 5.13.12-1-default and i915 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: javier(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- My laptop's screen flickers so much with 5.13.12 that it renders my laptop unusable. One workaround is to close and open the lid. After resuming, it works fine - there is no flickering. Booting up from the KDE Live image works fine. I have used the same Tumbleweed version (20210820) as the one I have installed on my laptop. The only difference is that I have an encrypted /home partition on my laptop's SSD. Tested kernels: 5.10.16-1.3: OK 5.11.4-1.3: NON-OK 5.12.12-1: NON-OK 5.13.12-1: NON-OK KDE Plasma 5.22.4 KDE Frameworks 5.85.0 Qt 5.15.2 See the attachments for more details. -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1209174] New: xhci_hcd errors with kernel 6.2.2
by bugzilla_noreply＠suse.com 12 Mar '23

12 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1209174 Bug ID: 1209174 Summary: xhci_hcd errors with kernel 6.2.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Today's kernel update to 6.2.2 causes a few xhci_hcd errors on boot: kernel: DMAR: DRHD: handling fault status reg 3 kernel: DMAR: [DMA Write NO_PASID] Request device [3d:00.0] fault addr 0x0 [fault reason 0x05] PTE Write access is not set kernel: xhci_hcd 0000:3d:00.0: No xhci virt device for slot_id 4 kernel: xhci_hcd 0000:3d:00.0: ERROR Invalid Transfer event kernel: xhci_hcd 0000:3d:00.0: @00000000ffffd000 507d2b50 00000000 24000040 04038001 kernel: xhci_hcd 0000:3d:00.0: No xhci virt device for slot_id 4 kernel: xhci_hcd 0000:3d:00.0: ERROR Invalid Transfer event kernel: xhci_hcd 0000:3d:00.0: @00000000ffffd010 507d3b50 00000000 24000008 04058001 Not sure, if they cause any trouble, but I want to let you know - just in case. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1207837] New: amdgpu: externals displays don't work when booting with plugged in docking station
by bugzilla_noreply＠suse.com 11 Mar '23

11 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207837 Bug ID: 1207837 Summary: amdgpu: externals displays don't work when booting with plugged in docking station Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: jirib79(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864672 --> http://bugzilla.opensuse.org/attachment.cgi?id=864672&action=edit dmesg - one with plugged in, other without 6.1.8-3.gbddbb73-default #1 openSUSE Tumbleweed (unreleased) ec01a7011546b1865e0ba429f47535b0e2fbc5e1, but also usual latest TW kernel - Lenovo T14s gen1 - FW: 0.1.42 (latest for 2023-02-01) - no idea if docking statin FW exists and can be updated When Lenonvo T14s Gen1 boots with plugged in USB-C connecting it with 'ThinkPad Hybrid USB-C with USB-A Dock (40AF)' (??) the externals monitors never work. The OS has to be booted with docking station unplugged, then when plugged again external monitors work. But..., after than when suspend is done, after resume the monitors are not active anymore - although visible in `xrandr' output. Steps to reproduce: - the docking station - external monitors (i have two SAMSUNG LF22T450F, HDMI and DP connected) - boot with usb-c cable between the docking station and Lenovo T14s gen1 plugged in Is this related? ---%>--- # tac /root/dmesg.txt | grep -m1 -A 20 -B 40 'Call Trace:' | tac Feb 01 17:47:35 t14s kernel: usb 5-1.1: SerialNumber: 301000001 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: ------------[ cut here ]------------ Feb 01 17:47:35 t14s kernel: WARNING: CPU: 6 PID: 161 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:3533 update_mst_stream_alloc_table+0x150/0x160 [amdgpu] Feb 01 17:47:35 t14s kernel: Modules linked in: dm_crypt essiv authenc trusted asn1_encoder tee hid_generic usbhid amdgpu crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic gf128mul drm_ttm_helper ttm iommu_v2 ghash_clmulni_intel gpu_sched ehci_pci xhci_pci sha512_ssse3 rtsx_pci_sdmmc xhci_pci_renesas drm_buddy mmc_core drm_display_helper xhci_hcd ehci_hcd aesni_intel ucsi_acpi nvme crypto_simd typec_ucsi cryptd cec usbcore roles nvme_core ccp rtsx_pci sp5100_tco rc_core typec video battery wmi serio_raw btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror dm_region_hash dm_log sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua ledtrig_timer msr efivarfs Feb 01 17:47:35 t14s kernel: CPU: 6 PID: 161 Comm: kworker/6:1 Tainted: G W 6.1.8-3.gbddbb73-default #1 openSUSE Tumbleweed (unreleased) ec01a7011546b1865e0ba429f47535b0e2fbc5e1 Feb 01 17:47:35 t14s kernel: Hardware name: LENOVO 20UJS2B901/20UJS2B901, BIOS R1CET73W(1.42 ) 12/09/2022 Feb 01 17:47:35 t14s kernel: Workqueue: events_long drm_dp_mst_link_probe_work [drm_display_helper] Feb 01 17:47:35 t14s kernel: RIP: 0010:update_mst_stream_alloc_table+0x150/0x160 [amdgpu] Feb 01 17:47:35 t14s kernel: Code: 00 00 75 2d 48 81 c4 98 00 00 00 5b 5d 41 5c e9 16 da ad d5 41 0f b7 40 04 4d 89 19 49 89 59 08 66 41 89 41 10 e9 71 ff ff ff <0f> 0b e9 fe fe ff ff e8 c4 01 83 d5 0f 1f 40 00 0f 1f 44 00 00 55 Feb 01 17:47:35 t14s kernel: RSP: 0018:ffffb7ce0073f678 EFLAGS: 00010202 Feb 01 17:47:35 t14s kernel: RAX: 0000000000000002 RBX: 0000000000000000 RCX: 0000000000000000 Feb 01 17:47:35 t14s kernel: RDX: 0000000000000000 RSI: ffffb7ce0073f678 RDI: ffffb7ce0073f708 Feb 01 17:47:35 t14s kernel: RBP: ffff9826d5e00aa0 R08: ffffb7ce0073f738 R09: ffffb7ce0073f480 Feb 01 17:47:35 t14s kernel: R10: ffff9826c7edb000 R11: ffff9826dd3037e0 R12: 0000000000000002 Feb 01 17:47:35 t14s kernel: R13: ffff9826d8701000 R14: ffffffffc188d8e0 R15: 0000000000000000 Feb 01 17:47:35 t14s kernel: FS: 0000000000000000(0000) GS:ffff9829bf980000(0000) knlGS:0000000000000000 Feb 01 17:47:35 t14s kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 01 17:47:35 t14s kernel: CR2: 00007effc2b12440 CR3: 0000000295010000 CR4: 0000000000350ee0 Feb 01 17:47:35 t14s kernel: Call Trace: Feb 01 17:47:35 t14s kernel: <TASK> Feb 01 17:47:35 t14s kernel: dc_link_allocate_mst_payload+0x95/0x290 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: core_link_enable_stream+0x7cc/0x980 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? optc1_set_drr+0x136/0x1e0 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dce110_apply_ctx_to_hw+0x652/0x700 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dc_commit_state_no_check+0x38c/0xc90 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: dc_commit_state+0x92/0x110 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: amdgpu_dm_atomic_commit_tail+0x4a0/0x2a80 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? get_page_from_freelist+0x4d9/0x1590 Feb 01 17:47:35 t14s kernel: ? dcn21_fast_validate_bw+0x3be/0x490 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? dcn21_validate_bandwidth_fp+0x101/0x6d0 [amdgpu 94e1b47238533e7ef69a131fcfbdc0d3832eb584] Feb 01 17:47:35 t14s kernel: ? __alloc_pages+0xec/0x240 Feb 01 17:47:35 t14s kernel: ? __get_random_u32_below+0x12/0x60 Feb 01 17:47:35 t14s kernel: ? allocate_slab+0x255/0x490 Feb 01 17:47:35 t14s kernel: ? drm_atomic_helper_setup_commit+0x4c7/0x840 Feb 01 17:47:35 t14s kernel: ? dma_resv_iter_first_unlocked+0x62/0x70 Feb 01 17:47:35 t14s kernel: ? dma_resv_get_fences+0x52/0x210 Feb 01 17:47:35 t14s kernel: ? wait_for_completion_timeout+0x112/0x140 Feb 01 17:47:35 t14s kernel: commit_tail+0x94/0x130 Feb 01 17:47:35 t14s kernel: drm_atomic_helper_commit+0x112/0x140 Feb 01 17:47:35 t14s kernel: drm_atomic_commit+0x77/0xf0 Feb 01 17:47:35 t14s kernel: ? drm_plane_get_damage_clips.cold+0x1c/0x1c Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit_atomic+0x1e7/0x230 Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit_locked+0x56/0x160 Feb 01 17:47:35 t14s kernel: drm_client_modeset_commit+0x21/0x40 Feb 01 17:47:35 t14s kernel: drm_fb_helper_set_par+0x9e/0xe0 Feb 01 17:47:35 t14s kernel: drm_fb_helper_hotplug_event+0x9f/0xe0 Feb 01 17:47:35 t14s kernel: drm_kms_helper_hotplug_event+0x26/0x30 Feb 01 17:47:35 t14s kernel: process_one_work+0x20f/0x3d0 Feb 01 17:47:35 t14s kernel: worker_thread+0x4a/0x3b0 Feb 01 17:47:35 t14s kernel: ? process_one_work+0x3d0/0x3d0 Feb 01 17:47:35 t14s kernel: kthread+0xda/0x100 Feb 01 17:47:35 t14s kernel: ? kthread_complete_and_exit+0x20/0x20 Feb 01 17:47:35 t14s kernel: ret_from_fork+0x22/0x30 Feb 01 17:47:35 t14s kernel: </TASK> Feb 01 17:47:35 t14s kernel: ---[ end trace 0000000000000000 ]--- Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:35 t14s kernel: amdgpu: [VBLANK]:crtc:0, vupdate-vrr:0, planes:1 Feb 01 17:47:36 t14s kernel: [HDCP_TOP]: Feb 01 17:47:36 t14s kernel: [HDCP_TOP]:[Link 0] mod_hdcp_add_display display 4 ---%<--- -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1206995] system fails to boot to gui with USB-C dock with all kernels > 6.1.0
by bugzilla_noreply＠suse.com 11 Mar '23

11 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1206995 https://bugzilla.suse.com/show_bug.cgi?id=1206995#c11 Sebastian Turza��ski <dpbasti(a)wp.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #11 from Sebastian Turza��ski <dpbasti(a)wp.pl> --- works fine with 6.2.1 kernel -- You are receiving this mail because: You are the assignee for the bug.

1 0