February 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1208728] New: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208728 Bug ID: 1208728 Summary: Thinkpad X1 Carbon Gen 10 won't enter S3 sleep on kernel 6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: victorfuga(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 6, my thinkpad x1 carbon will not enter s3 sleep even when set as the default sleep option. Checked a few distros and noted it was working using kernel 5.19 "LTS" in manjaro. Currently running Tumbleweed snapshot 20230226, sleep mode is set to "Linux" in the bios. Checked on lid close, sleep button in KDE, and Fn + 4 key combo. $ cat /sys/power/mem_sleep s2idle [deep] $ sudo journalctl | grep "PM: suspend" | tail -2 2�� 27 18:29:09 reisen kernel: PM: suspend entry (s2idle) 2�� 27 18:29:11 reisen kernel: PM: suspend exit -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1206977] New: On boot hangs on fbo:switching to i915 from EFI VGA
by bugzilla_noreply＠suse.com 18 Mar '23

18 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206977 Bug ID: 1206977 Summary: On boot hangs on fbo:switching to i915 from EFI VGA Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: nsnospam3(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- HW: ASUS Prime Z790-P with iCore5 CPU with integrated GPU, M2 NVMe SSD Installation was not possible without grub linux parameter nomodeset. Of course with this parameter only the basic resolution of 1024x768 is available. Every successive boot hangs on log entry fbo:switching to i915 from EFI VGA. As I could not find any solution I tried first to install Windows 10. Worked without any Problem Intel drivers were installed properly and I got full resolution of 2560x1440. I tried openSUSE-Tumbleweed-GNOME-Live-x86_64-Current.iso starting form USB. Worked as expected with full resolution. I tried to install openSUSE-Tumbleweed-DVD-x86_64-Current.iso. Didn't hang and I could start the installation. I interromped the installation to try Leap 15.4 again first getting the updated version i.e. openSUSE-Leap-15.4-CR-DVD-x86_64-Build31.38-Media.iso. No chance, without nomodeset parameter no installation possible. I'll install tumbleweed now, but this is not exactly what I wanted. -- You are receiving this mail because: You are the assignee for the bug.

1 6

[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 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 1206316] New: [RKL] add_drivers+=" i915 " included in /etc/dracut.d/*, cause drm/dri issue(s) that delay initial X startup ~90 seconds
by bugzilla_noreply＠suse.com 08 Mar '23

08 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206316 Bug ID: 1206316 Summary: [RKL] add_drivers+=" i915 " included in /etc/dracut.d/*, cause drm/dri issue(s) that delay initial X startup ~90 seconds Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com, tzimmermann(a)suse.com Found By: --- Blocker: --- Created attachment 863458 --> http://bugzilla.opensuse.org/attachment.cgi?id=863458&action=edit .tgz of Xorg.0.log + journalctl -b (with drm.debug=0x1e log_buf_len=1M) Initial summary: [RKL] add_drivers+=" i915 " included in /etc/dracut.d/*, cause drm/dri issue(s) that delay initial X startup ~90 seconds To reproduce: 1-include add_drivers+=" i915 " in /etc/dracut.d/local.conf 2-dracut -f 3-reboot Actual behavior: 1-~90 seconds between shell prompt appearance on tty1 and TDM greeter appearance on tty7 2-Grep of /dev/dri/card from the attachment: [ 93.509] (II) xfree86: Adding drm device (/dev/dri/card1) [ 93.575] (II) modeset(0): using drv /dev/dri/card1 Dec 12 03:57:11 ab560 systemd[1]: Timed out waiting for device /dev/dri/card0. 3-# dmesg | grep -i Faile [ 2.410971] simple-framebuffer simple-framebuffer.0: [drm:drm_atomic_helper_check_planes] [CRTC:34:crtc-0] atomic driver check failed [ 2.410979] simple-framebuffer simple-framebuffer.0: [drm:drm_atomic_check_only] atomic driver check for 000000008eb548ce failed: -22 [ 2.548403] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging [ 2.738080] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging [ 2.814605] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging [ 3.640125] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 3.640127] cfg80211: failed to load regulatory.db [ 3.870867] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -61 [ 3.870938] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -61 [ 93.481800] i915 0000:00:02.0: [drm:i915_perf_remove_config_ioctl [i915]] Failed to remove unknown OA config [ 93.554205] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging [ 93.626006] i915 0000:00:02.0: [drm:intel_hdmi_set_edid [i915]] HDMI GMBUS EDID read failed, retry using GPIO bit-banging 4-in the attachment Expected behavior: 1-# systemd-analyze critical-chain (kernel 6.0.10 without including driver i915 in initrd) .... graphical.target @3.640s ��multi-user.target @3.640s ��kbdsettings.service @1.564s +2.075s ��basic.target @1.560s ��sockets.target @1.560s ��telnet.socket @1.560s ��sysinit.target @1.558s ��systemd-timesyncd.service @1.538s +20ms ��systemd-tmpfiles-setup.service @1.528s +9ms ��local-fs.target @1.527s ��run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @1.529s ��local-fs-pre.target @514ms ��lvm2-monitor.service @378ms +135ms ��dm-event.socket @315ms ��system.slice ��-.slice 2-Xorg.0.log begins at ~[ 4.7s] 3-Nice, fast boot to greeter # inxi -CSGz System: Kernel: 6.0.10-1-default arch: x86_64 bits: 64 Desktop: Trinity v: R14.0.13 Distro: openSUSE Tumbleweed 20221210 CPU: Info: 6-core model: 11th Gen Intel Core i5-11400 bits: 64 type: MT MCP cache: L2: 3 MiB Speed (MHz): avg: 2600 min/max: 800/4400 cores: 1: 2600 2: 2600 3: 2600 4: 2600 5: 2600 6: 2600 7: 2600 8: 2600 9: 2600 10: 2600 11: 2600 12: 2600 Graphics: Device-1: Intel RocketLake-S GT1 [UHD Graphics 730] driver: i915 v: kernel Display: x11 server: X.Org v: 21.1.4 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915 resolution: 1: 2560x1440~60Hz 2: 1920x1200~60Hz 3: 1680x1050~60Hz API: OpenGL v: 4.6 Mesa 22.2.4 renderer: Mesa Intel Graphics (RKL GT1) -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1208460] New: Blank screen with Radeon RX 5700
by bugzilla_noreply＠suse.com 06 Mar '23

06 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208460 Bug ID: 1208460 Summary: Blank screen with Radeon RX 5700 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: adam(a)mizerski.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0 Build Identifier: Few days ago my Radeon RX 5700 after 3 years of working absolutely fine, kind of stopped working. The symptoms are: - At BIOS and GRUB there is video output. - If I run the system with "nomodeset" kernel option, then there is video output (obviously without acceleration and limited to low resolution). - It's not a faulty cable, because I tested it with other cables. I usually use HDMI cable, but with DisplayPort it's the same. - It's not a faulty monitor, because I use it also with my laptop on a second input. - If I put my card into another computer with Windows, it works with acceleration, like there's nothing wrong. - But if I start my Tumbleweed with amdgpu drivers, then as soon as kernel loads drm driver (so it's even before Xorg starts), the screen goes blank (the monitor shows "no signal" and shuts off). It doesn't matter if I boot my Tumbleweed with current or previous kernel. It doesn't matter if it's my Tumbleweed or a Leap 15.4 booted from usb stick. dmesg: https://paste.opensuse.org/pastes/c4df53bb0f7a It says: amdgpu 0000:09:00.0: [drm] Cannot find any crtc or sizes Xorg.0.log: https://paste.opensuse.org/pastes/e9bd760602d1 It says: (WW) AMDGPU(0): Unable to find connected outputs I also tried: - remove "quiet", remove "splash=silent", and append "plymouth.enable=0" (as written at https://en.opensuse.org/SDB:Nomodeset:_Work_Around_Graphic_Upgrade_&_Instal…) - nothing changed - amdgpu.dc=0 - screen stays on, but shows nothing (just black) Reproducible: Always Steps to Reproduce: Just boot the system Actual Results: Screen goes into suspend Expected Results: Graphics on screen -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1206833] New: Cannot load KMPs on armv7
by bugzilla_noreply＠suse.com 02 Mar '23

02 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1206833 Bug ID: 1206833 Summary: Cannot load KMPs on armv7 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: armv7 OS: openSUSE Leap 15.4 Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: james.hobson(a)oriel.ox.ac.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- KMPs do not load on OpenSuse Leap 15.4 on armv7. This because the kernel-default/lpae package exports: Provides: ksym(...) = 5f For all kernel symbols, but kernel symbols are calculated correctly for KMP packages e.g. ksym(default:PDE_DATA) = 22e390 (made up hash) This means that when you install a KMP package with zypper, it says that it cannot resolve dependencies. More worryingly, this breaks OBS kiwi builds for the armv7 platform -- You are receiving this mail because: You are the assignee for the bug.

1 11

[Bug 1208750] New: kernel fails to access EFI runtime services, efibootmgr fails to run as a result
by bugzilla_noreply＠suse.com 01 Mar '23

01 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1208750 Bug ID: 1208750 Summary: kernel fails to access EFI runtime services, efibootmgr fails to run as a result Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: aarch64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 865153 --> https://bugzilla.suse.com/attachment.cgi?id=865153&action=edit dmesg-virt75-6.2.0-1.g89e2785-default.txt virt75 is a GIGABYTE G242-P34-00 It was possible to run Tumbleweed in the past. It runs SLE15 fine, modulo bug#1198682 The kernel 6.1 and 6.2 is unable to use the EFI runtime services: [ 0.722100] [Firmware Bug]: Unable to handle paging request in EFI runtime service -- You are receiving this mail because: You are the assignee for the bug.

1 3

[Bug 1208766] New: Kernel 6.2.1 does not suspend/hibernate anymore for AMD Ryzen 7 Pro
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1208766 Bug ID: 1208766 Summary: Kernel 6.2.1 does not suspend/hibernate anymore for AMD Ryzen 7 Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fkrueger(a)mailbox.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- TW20230227 with kernel-default-6.2.1-1.1.g69e0e95.x86_64 from Kernel:stable repo does not suspend/hibernate anymore. Regarding the latter, the possibility to hibernate is not even provided in KDE's menu. Kernel-default-6.2.0-5.1.g09a9a65.x86_64 works fine. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1189283] New: kernel-obs-build needs af_alg
by bugzilla_noreply＠suse.com 28 Feb '23

28 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1189283 Bug ID: 1189283 Summary: kernel-obs-build needs af_alg 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libkcapi got updated to 1.3.1 (https://build.opensuse.org/request/show/910806) and apparently gnutls picks that up now and enables support for it. It seems like that depends on AF_ALG sockets though, which are currently not enabled in kernel-obs-build (missing af_alg module), so various builds (libzip, libvirt) fail with libkcapi - Error: AF_ALG: socket syscall failed (errno: -97) I'm not sure whether just af_alg is enough, it might need some other modules as well. -- You are receiving this mail because: You are the assignee for the bug.

1 7