January 2023 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205603] New: bpf lsm enabled but not included in LSM list
by bugzilla_noreply＠suse.com 17 Apr '23

17 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1205603 Bug ID: 1205603 Summary: bpf lsm enabled but not included in LSM list 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: mrueckert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- During my system upgrades i noticed the following message: ```systemd[1]: bpf-lsm: BPF LSM hook not enabled in the kernel, BPF LSM not supported``` but we have: ```CONFIG_BPF_LSM=y``` i asked Frank Bui what it checks for. it checks for the string "bpf" in this list: ``` cat /sys/kernel/security/lsm lockdown,capability,apparmor ``` it seems ```CONFIG_LSM="integrity,apparmor"``` needs an update. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1188954] New: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1
by bugzilla_noreply＠suse.com 14 Apr '23

14 Apr '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1188954 Bug ID: 1188954 Summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 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: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de CC: sndirsch(a)suse.com Found By: --- Blocker: --- Created attachment 851460 --> http://bugzilla.opensuse.org/attachment.cgi?id=851460&action=edit Xorg.0.log and dmesg Initial summary: black screen on initial X open on Kaveri Radeon R7, /dev/dri/card0: No such file or directory with radeon.cik_support=0 amdgpu.cik_support=1 To reproduce: 1-boot with included on kernel cmdline radeon.cik_support=0 amdgpu.cik_support=1 2-wait for X to fail to start 3-login on a tty 4-systemctl restart xdm Actual behavior: 1-X fails to start, finding no /dev/dri/card0, leaving login prompt on tty1 on display screen 2-X starts normally using amdgpu DDX driver Expected behavior: 1-X starts normally using amdgpu DDX driver Tested with kernels 5.12.13, 5.11.16, 5.7.11 # inxi -SGIay System: Host: asa88 Kernel: 5.12.13-1-default x86_64 bits: 64 compiler: gcc v: 11.1.1 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=tvgp07stw noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 video=1024x768@60 video=1440x900@60 drm.debug=0x1e log_buf_len=1M Console: tty pts/0 DM: TDM Distro: openSUSE Tumbleweed 20210730 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASUSTeK driver: amdgpu v: kernel alternate: radeon bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300 Display: server: X.org 1.20.12 driver: loaded: vesa unloaded: fbdev,modesetting alternate: ati Message: Advanced graphics data unavailable for root. Info:...inxi: 3.3.06 Comments: 1-without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline, X cannot be coaxed into using amdgpu DDX driver via /etc/X11/xorg.conf.d/*conf 2-without radeon.cik_support=0 amdgpu.cik_support=1, greeter startup completes (normally, on first try) using modesetting DIX driver -- You are receiving this mail because: You are the assignee for the bug.

1 27

[Bug 1191924] New: kernel-source.git/README outdated
by bugzilla_noreply＠suse.com 10 Apr '23

10 Apr '23

https://bugzilla.suse.com/show_bug.cgi?id=1191924 Bug ID: 1191924 Summary: kernel-source.git/README outdated 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: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- There is a section "Before You Commit -- Things To Check" in kernel-source.git/README, it will likely not work out of the box. According to rpm/kernel-binary.spec.in, at least three more packages beside the obvious gcc/make/patch need to be installed: BuildRequires: libopenssl-devel BuildRequires: libelf-devel BuildRequires: dwarves >= 1.21 Furthermore rapidquilt is not mentioned. It is not strictly required, but one can hardly live without it. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1202353] New: kernel: replace mkinitrd wrapper with native dracut
by bugzilla_noreply＠suse.com 31 Mar '23

31 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1202353 Bug ID: 1202353 Summary: kernel: replace mkinitrd wrapper with native dracut 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: antonio.feijoo(a)suse.com QA Contact: qa-bugs(a)suse.de Blocks: 1202351 Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1202351 +++ Upstream support removed in March 2021 (https://github.com/dracutdevs/dracut/commit/43df4ee2) and deprecation announcement on factory mailing list in May 2021 (https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/…) ALP will not ship the mkinitrd wrapper, so it's better to get rid of it in Tumbleweed first. Affected packages that need to be updated before (at least): # zypper se --requires mkinitrd Loading repository data... Reading installed packages... S | Name | Summary | Type ---+---------------------+----------------------------------------------------+-------- | kernel-debug | A Debug Version of the Kernel | package i+ | kernel-default | The Standard Kernel | package | kernel-default-base | The Standard Kernel - base modules | package | kernel-kvmsmall | The Small Developer Kernel for KVM | package | kernel-pae | Kernel with PAE Support | package | kernel-vanilla | The Standard Kernel - without any SUSE patches | package i | mdadm | Utility for configuring "MD" software RAID devices | package -- You are receiving this mail because: You are the assignee for the bug.

1 39

[Bug 1207728] New: qgroup rescan paused every startup or reboot
by bugzilla_noreply＠suse.com 23 Mar '23

23 Mar '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207728 Bug ID: 1207728 Summary: qgroup rescan paused every startup or reboot 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: jshand2013(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- after the release of kernel 6.1.8, upon each startup and reboot i get a message: btrfs info : qgroup rescan paused. to get passed this point i have to run sudo btrfs quota rescan / each time to complete the rescan process so it gets to be BTRFS info (device sda2): qgroup scan completed (inconsistency flag cleared) -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1190261] New: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used
by bugzilla_noreply＠suse.com 21 Mar '23

21 Mar '23

https://bugzilla.suse.com/show_bug.cgi?id=1190261 Bug ID: 1190261 Summary: Kernel scriptlets: XXX: Only call mokutil if UEFI and shim are used 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: martin.wilck(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Spin-off from bug 1189841. From https://github.com/openSUSE/suse-module-tools/pull/33: @mwilck: so why not test this? e.g. like this: if [ "$(mokutil --sb-state 2>/dev/null)" = "SecureBoot enabled" ]; then ... fi @hramrach: ??? The part that github displays as context for this comment does not look relevant @hramrach hramrach 21 hours ago Member Right, if you refer to XXX: Only call mokutil if UEFI and shim are used then I have no opinion on that. Should be probably handled in a separate bug and the implications of any possible check discussed to death. @hramrach hramrach 21 hours ago Member Actually, there is the problem that on arm64 you suddenly get from no shim to shim on SP update without any warning so this is really hairy to get right. Really deserves a separate bug. -- You are receiving this mail because: You are the assignee for the bug.

1 3

[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 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 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 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

[Bug 1207279] New: When going to suspend, system instantly wakes up again
by bugzilla_noreply＠suse.com 25 Feb '23

25 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207279 Bug ID: 1207279 Summary: When going to suspend, system instantly wakes up again Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: ralf.kissmann(a)uibk.ac.at QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Firefox/102.0 Build Identifier: Since the change from kernel 6.0 to 6.1 suspend does not work any more on my system - neither when using the Gnome desktop menu nor when closing the lid on the laptop. In this case the system seems to briefly go to suspend only to directly wake up again (the power LED briefly turns off, just to turn on again). The system still works fine, but suspend just does not work any more. On kernel 6.0 this worked without any problem. The problem was present for the first version of kernel 6.1 and is still unchanged with kernel 6.1.4 The hardware I use is a Lenovo Thinkpad T14s G2 AMD with AMD with Ryzen 7 Pro 5850U processor. Reproducible: Always Steps to Reproduce: 1. Run gnome on recent AMD system 2. Suspend system Actual Results: The computer will instantly wake up again. Expected Results: System should stay in suspend and only wake up when either opening the lid or pressing the power button It seems that the bug is related to the kernel according a discussion in the Arch-Linux community, e.g., to be found here: https://bbs.archlinux.org/viewtopic.php?id=282293 -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1207655] New: amdgpu [RX 7900] causing system freeze
by bugzilla_noreply＠suse.com 22 Feb '23

22 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207655 Bug ID: 1207655 Summary: amdgpu [RX 7900] causing system freeze 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: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864535 --> http://bugzilla.opensuse.org/attachment.cgi?id=864535&action=edit journalctl After running the system for a while, out of nowhere the system suddenly stops responding to anything and I need to do Alt+SysRq+reisub The error started at 21:04 in the logs -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1207516] New: No modesetting with Zen4 integrated graphics or rx6950 XT
by bugzilla_noreply＠suse.com 22 Feb '23

22 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207516 Bug ID: 1207516 Summary: No modesetting with Zen4 integrated graphics or rx6950 XT Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rguenther(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The Alpha from late December doesn't perform graphic install and listing pci IDs and corresponding kernel drivers shows nothing. X startup complains that no modesetting is possible. Plugged to monitor during install: 39:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at 80000000 (64-bit, prefetchable) [size=256M] Memory at 90000000 (64-bit, prefetchable) [size=2M] I/O ports at e000 [disabled] [size=256] Memory at ece00000 (32-bit, non-prefetchable) [size=512K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/4 Maskable- 64bit+ Capabilities: [c0] MSI-X: Enable- Count=4 Masked- Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [410] #26 Capabilities: [450] #27 Also installed: 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6950 XT] [1002:73a5] (rev c0) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3955] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at a0000000 (64-bit, prefetchable) [size=256M] Memory at b0000000 (64-bit, prefetchable) [size=2M] I/O ports at f000 [disabled] [size=256] Memory at ecf00000 (32-bit, non-prefetchable) [size=1M] Expansion ROM at ed000000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [64] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [200] #15 Capabilities: [240] Power Budgeting <?> Capabilities: [270] #19 Capabilities: [2a0] Access Control Services Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [320] Latency Tolerance Reporting Capabilities: [410] #26 Capabilities: [440] #27 gdm-Xorg doesn't even try to load the readeon module but ultimatively fails as Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (--) PCI: (3@0:0:0) 1002:73a5:1462:3955 rev 192, Mem @ 0xa0000000/268435456, 0xb0000000/2097152, 0xecf00000/1048576, I/O @ 0x0000f000/256, BIOS @ 0x????????/131072 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (--) PCI:*(57@0:0:0) 1002:164e:1458:d000 rev 194, Mem @ 0x80000000/268435456, 0x90000000/2097152, 0xece00000/524288, I/O @ 0x0000e000/256 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "glx" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Module glx: vendor="X.Org Foundation" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: compiled for 1.21.1.4, module version = 1.0.0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: ABI class: X.Org Server Extension, version 10.0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Scanning /usr/share/X11/xorg_pci_ids directory for additional PCI ID's supported by the drivers Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched ati as autoconfigured driver 0 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched modesetting as autoconfigured driver 1 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched fbdev as autoconfigured driver 2 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Matched vesa as autoconfigured driver 3 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (==) Assigned the driver to the xf86ConfigLayout Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "ati" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (WW) Warning, couldn't open module ati Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "ati" (module does not exist, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "modesetting" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Module modesetting: vendor="X.Org Foundation" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: compiled for 1.21.1.4, module version = 1.21.1 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: Module class: X.Org Video Driver Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: ABI class: X.Org Video Driver, version 25.2 Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "fbdev" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load /usr/lib64/xorg/modules/drivers/fbdev_drv.so: /usr/lib64/xorg/modules/drivers/fbdev_drv.so: undefined symbol: fbdevHWSave Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "fbdev" (loader failed, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) LoadModule: "vesa" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load /usr/lib64/xorg/modules/drivers/vesa_drv.so: /usr/lib64/xorg/modules/drivers/vesa_drv.so: undefined symbol: VBESetModeParameters Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Failed to load module "vesa" (loader failed, 0) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) modesetting: Driver for Modesetting Kernel Drivers: kms Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) open /dev/dri/card0: No such file or directory Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (WW) Falling back to old probe method for modesetting Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) open /dev/dri/card0: No such file or directory Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Screen 0 deleted because of no matching config section. Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (II) UnloadModule: "modesetting" Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Device(s) detected, but none match those in the config file. Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: Fatal server error: Jan 25 03:48:40 localhost.localdomain gdm-Xorg-:4[1352]: (EE) no screens found(EE) -- You are receiving this mail because: You are the assignee for the bug.

1 17

[Bug 1207701] New: Kernel panic on suspend after upgrade to TW 20230125
by bugzilla_noreply＠suse.com 13 Feb '23

13 Feb '23

https://bugzilla.suse.com/show_bug.cgi?id=1207701 Bug ID: 1207701 Summary: Kernel panic on suspend after upgrade to TW 20230125 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dheidler(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 864559 --> https://bugzilla.suse.com/attachment.cgi?id=864559&action=edit journal I'm using a Thinkpad T14s and after the upgrade to 20230125 the system freezes with a black screen but the power led still indicating a running system and no successful suspend. After trying some keys and the power key to trigger a resume, the caps led blinking indicates a kernel panic. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1207807] New: khugepaged consumes 100% cpu apparently causing virtual machine to freeze for extended times
by bugzilla_noreply＠suse.com 03 Feb '23

03 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207807 Bug ID: 1207807 Summary: khugepaged consumes 100% cpu apparently causing virtual machine to freeze for extended times Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: x86-64 OS: openSUSE Leap 15.4 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: obs(a)akr.yagii.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am running a Windows 10 virtual machine guest in VMware Workstation 16.2. The guest becomes unresponsive for 10-60s after each mouse click and khugepaged is run at 100% cpu. This is reproducible after almost every suspend of the guest or a suspend of the host. -- You are receiving this mail because: You are the assignee for the bug.

1 8

[Bug 1202570] New: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202570 Bug ID: 1202570 Summary: steam deck - echo freeze | tee -a /sys/powerstate glitches the screen Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suspend seems to work in the latest kernel in kernel:HEAD repo. Software suspends seems to glitch the screen upon re-initialization. Wifi and changing to tty works. lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a zypper info kernel-default Loading repository data... Reading installed packages... Information for package kernel-default: --------------------------------------- Repository : kernel-repo Name : kernel-default Version : 6.0~rc1-3.1.g7bd57d5 Arch : x86_64 Vendor : obs://build.opensuse.org/Kernel Installed Size : 273.3 MiB Installed : Yes Status : up-to-date Source package : kernel-default-6.0~rc1-3.1.g7bd57d5.nosrc Upstream URL : https://www.kernel.org/ Summary : The Standard Kernel Description : The standard kernel for both uniprocessor and multiprocessor systems. Source Timestamp: 2022-08-16 07:58:42 +0000 GIT Revision: 7bd57d59ba8c141be35bb5189487a899d04e76ec GIT Branch: master -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1202566] New: Steam deck wakes up from hibernate with max brightness
by bugzilla_noreply＠suse.com 02 Feb '23

02 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1202566 Bug ID: 1202566 Summary: Steam deck wakes up from hibernate with max brightness Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- echo 0x1e | sudo tee -a /sys/module/drm/parameters/debug [sudo] password for root: 0x1e -> echo disk | sudo tee -a /sys/power/state disk ~> dmesg > dmesg-suspend-from-disk-with-0x1e-enabled lsb_release -a LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20220817 Codename: n/a Linux steamdeck 6.0.0-rc1-1.gd997b88-default #1 SMP PREEMPT_DYNAMIC Thu Aug 18 14:44:01 UTC 2022 (d997b88) x86_64 x86_64 x86_64 GNU/Linux https://build.opensuse.org/project/show/home:tiwai:bsc1201418 -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1207763] New: Since 5.14.21-150400.24.41-default, machine fails to recover from hibernation.
by bugzilla_noreply＠suse.com 01 Feb '23

01 Feb '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207763 Bug ID: 1207763 Summary: Since 5.14.21-150400.24.41-default, machine fails to recover from hibernation. Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since the last update, the machine fails on recovery from hibernation. It goes to boot instead. I will attach "journalctl -b0" and "journalctl --boot=-1", editing the central part out for privacy (emails and such). Core: Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 80% Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 90% Jan 30 11:30:35 Telcontar kernel: PM: Image loading progress: 100% Jan 30 11:30:35 Telcontar kernel: PM: Image loading done Jan 30 11:30:35 Telcontar kernel: PM: hibernation: PM: secret key is invalid Jan 30 11:30:35 Telcontar kernel: PM: hibernation: PM: Hibernation trampoline page prepared Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Read 17090332 kbytes in 16.95 seconds (1008.27 MB/s) Jan 30 11:30:35 Telcontar kernel: PM: Image successfully loaded Jan 30 11:30:35 Telcontar kernel: printk: Suspending console(s) (use no_console_suspend to debug) Jan 30 11:30:35 Telcontar kernel: serial 00:05: disabled Jan 30 11:30:35 Telcontar kernel: PM: pci_pm_freeze(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 Jan 30 11:30:35 Telcontar kernel: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xd0 returns -16 Jan 30 11:30:35 Telcontar kernel: xhci_hcd 0000:29:00.3: PM: failed to quiesce async: error -16 Jan 30 11:30:35 Telcontar kernel: xhci_hcd 0000:03:00.0: xHC error in resume, USBSTS 0x401, Reinit Jan 30 11:30:35 Telcontar kernel: usb usb1: root hub lost power or was reset Jan 30 11:30:35 Telcontar kernel: usb usb2: root hub lost power or was reset Jan 30 11:30:35 Telcontar kernel: serial 00:05: activated Jan 30 11:30:35 Telcontar kernel: nvme nvme0: Shutdown timeout set to 8 seconds Jan 30 11:30:35 Telcontar kernel: nvme nvme0: 32/0/0 default/read/poll queues Jan 30 11:30:35 Telcontar kernel: ata9: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata5: SATA link down (SStatus 0 SControl 330) Jan 30 11:30:35 Telcontar kernel: ata10: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata7: SATA link down (SStatus 0 SControl 300) Jan 30 11:30:35 Telcontar kernel: ata6: SATA link down (SStatus 0 SControl 330) Jan 30 11:30:35 Telcontar kernel: usb 1-13: reset low-speed USB device number 2 using xhci_hcd Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Failed to load image, recovering. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: Basic memory bitmaps freed Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) -- You are receiving this mail because: You are the assignee for the bug.

1 13

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 31 Jan '23

31 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c40 --- Comment #40 from David Mair <dmair(a)suse.com> --- (In reply to David Mair from comment #39) > @Ludwig, @Martin, should the change have been made conditional upon > build_kmp? > > By default the change seems to ultimately build require kernel-syms which is > not available for 32-bit products. i586 builds fail for several products as > a result because they are unable to fulfill requirement kernel-syms. My apologies. Comment #39 for the crash package only. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205149] %kernel_module_package_buildreqs needs to require suse-kernel-rpm-scriptlets
by bugzilla_noreply＠suse.com 31 Jan '23

31 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1205149 https://bugzilla.suse.com/show_bug.cgi?id=1205149#c39 David Mair <dmair(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dmair(a)suse.com, | |lnussel(a)suse.com Flags| |needinfo?(lnussel(a)suse.com) | |, | |needinfo?(martin.wilck@suse | |.com) --- Comment #39 from David Mair <dmair(a)suse.com> --- @Ludwig, @Martin, should the change have been made conditional upon build_kmp? By default the change seems to ultimately build require kernel-syms which is not available for 32-bit products. i586 builds fail for several products as a result because they are unable to fulfill requirement kernel-syms. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 31 Jan '23

31 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c24 Sarah Kriesch <ada.lovelace(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #24 from Sarah Kriesch <ada.lovelace(a)gmx.de> --- Thanks for this hint, Berthold. I close this bugreport then. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207776] External monitor ceased working in the middle of an X11 session and cannot be reactivated
by bugzilla_noreply＠suse.com 31 Jan '23

31 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207776 http://bugzilla.opensuse.org/show_bug.cgi?id=1207776#c1 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrik.jakobsson(a)suse.com, | |tiwai(a)suse.com, | |tzimmermann(a)suse.com Component|X.Org |Kernel Assignee|gfx-bugs(a)suse.de |kernel-bugs(a)opensuse.org QA Contact|gfx-bugs(a)suse.de |qa-bugs(a)suse.de --- Comment #1 from Stefan Dirsch <sndirsch(a)suse.com> --- Hmm. Looks like a kernel (driver) issue to me ... therefore reassigning. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189791] btrfs filesystem corruptions with HyperPAV
by bugzilla_noreply＠suse.com 31 Jan '23

31 Jan '23

https://bugzilla.suse.com/show_bug.cgi?id=1189791 https://bugzilla.suse.com/show_bug.cgi?id=1189791#c23 Berthold Gunreben <azouhr(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(azouhr(a)opensuse.o | |rg) | --- Comment #23 from Berthold Gunreben <azouhr(a)opensuse.org> --- At the moment, I cannot reproduce this bug, because I don't have the needed z/VM available. The next steps I will do are an upgrade of z15 -> z16, after this I will perform an upgrade of the z/VM release. After that, I can try to reproduce the issue. However, since I also have direct support from IBM at hand for SLES releases, I can go forward with IBM then. So, for me, it is ok to close this here. It will take some more months to reproduce with SLES on the latest z/VM. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1207761] New: CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO %
by bugzilla_noreply＠suse.com 30 Jan '23

30 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1207761 Bug ID: 1207761 Summary: CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO % Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: carlos.e.r(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Suddenly I noticed that "iotop" fails to produce adequate information: Total DISK READ : 0.00 B/s | Total DISK WRITE : 18.63 K/s Actual DISK READ: 0.00 B/s | Actual DISK WRITE: 23.29 K/s TID PRIO USER DISK READ DISK WRITE SWAPIN IO> COMMAND 653 be/3 root 0.00 B/s 2.33 K/s ?unavailable? [jbd2/nvme0n1p5-] 1287 be/3 root 0.00 B/s 8.15 K/s ?unavailable? [jbd2/sdc5-8] 8764 be/4 cer 0.00 B/s 3.49 K/s ?unavailable? firefox --sm-client-id 29~dd20a571983d [Cache2 I/O] 9660 be/4 cer 0.00 B/s 4.66 K/s ?unavailable? firefox --sm-client-id 29~-dd20a571983d [LS Thread] ... CONFIG_TASK_DELAY_ACCT not enabled in kernel, cannot determine SWAPIN and IO % I am not sure what update produced this. I know that it worked with 15.3. -- You are receiving this mail because: You are the assignee for the bug.

1 2