September 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1189879] New: Missing kernel config in /boot
by bugzilla_noreply＠suse.com 07 Dec '21

07 Dec '21

https://bugzilla.suse.com/show_bug.cgi?id=1189879 Bug ID: 1189879 Summary: Missing kernel config in /boot 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: petr.vorel(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- bsc#1184804 moved kernel config out of /boot into /usr/lib/modules/. But unlike vmlinuz and initrd there is missing symlink in /boot. Is it really a wanted change? $ ls -l /boot/ -rw-r--r-- 1 root root 0 Mar 13 2017 backup_mbr -rw-r--r-- 1 root root 1725 Jul 28 19:25 boot.readme drwxr-xr-x 6 root root 4096 Aug 25 11:18 grub2 lrwxrwxrwx 1 root root 34 Aug 25 10:57 initrd -> initrd-5.14.0-rc7-3.gdbb9dbc-debug -rw------- 1 root root 11202252 May 24 2019 initrd-5.0.7 -rw------- 1 root root 22664676 Aug 25 11:02 initrd-5.14.0-rc7-3.gdbb9dbc-debug -rw------- 1 root root 22652804 Aug 25 11:03 initrd-5.14.0-rc7-3.gdbb9dbc-default -rw------- 1 root root 13074280 Jul 4 2019 initrd-5.2.0-rc1-2.gb225e5a-default+ -rw------- 1 root root 19355748 Jul 4 2019 initrd-5.2.0-rc1-2.gb225e5a-default+-kdump lrwxrwxrwx 1 root root 58 Aug 25 10:57 sysctl.conf-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/sysctl.conf lrwxrwxrwx 1 root root 60 Aug 25 10:56 sysctl.conf-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/sysctl.conf lrwxrwxrwx 1 root root 57 Aug 25 10:57 System.map-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/System.map lrwxrwxrwx 1 root root 59 Aug 25 10:56 System.map-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/System.map lrwxrwxrwx 1 root root 35 Aug 25 10:57 vmlinuz -> vmlinuz-5.14.0-rc7-3.gdbb9dbc-debug lrwxrwxrwx 1 root root 54 Aug 25 10:57 vmlinuz-5.14.0-rc7-3.gdbb9dbc-debug -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-debug/vmlinuz lrwxrwxrwx 1 root root 56 Aug 25 10:56 vmlinuz-5.14.0-rc7-3.gdbb9dbc-default -> ../usr/lib/modules/5.14.0-rc7-3.gdbb9dbc-default/vmlinuz If yes, some users can be surprised. Also rpm package claims to have config in /boot but it's not there: $ rpm -ql kernel-default-5.14~rc7-3.1.gdbb9dbc.x86_64 |grep /boot/config /boot/config-5.14.0-rc7-3.gdbb9dbc-default ls -la /boot/config-5.14.0-rc7-3.gdbb9dbc-default ls: cannot access '/boot/config-5.14.0-rc7-3.gdbb9dbc-default': No such file or directory According to openQA it was broken somewhere between 5.13.12-1.2 999e6048a4cc6accd2653c9dccaaaff2f4ae8f86 (good) and 5.13.12-2.1 33df9c651d0aa37cce1275bd9528ea5cb9196022 (bad). It looks to me that 33df9c651d0aa37cce1275bd9528ea5cb9196022 Revert "Revert "UsrMerge the kernel (boo#1184804)"" broke it. -- You are receiving this mail because: You are the assignee for the bug.

1 34

[Bug 1190854] New: amdgpu fails to probe Radeon Pro WX3200
by bugzilla_noreply＠suse.com 01 Dec '21

01 Dec '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190854 Bug ID: 1190854 Summary: amdgpu fails to probe Radeon Pro WX3200 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: grasland(a)lal.in2p3.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 852729 --> http://bugzilla.opensuse.org/attachment.cgi?id=852729&action=edit dmesg log, with ANSI color codes On a Dell Precision 3650 equipped with a Radeon Pro WX3200, something very wrong happens during the amdgpu initialization process (or perhaps before, see below), which makes the card unusable on Linux. Thus, I have to fall back to the CPU's built-in graphics for the time being on this machine. The GPU is brand new and works on both the UEFI setup screen and Windows, which suggests to me that the hardware is not completely broken. But of course, this does not fully exclude the possibility of a hardware issue that would only be triggered by the Linux initialization process. You will find attached the dmesg log, with and without ANSI color codes as I personally find dmesg' color output much easier to visually parse. --- Let's have a closer look at the amdgpu logs, since that's what I'm directly interested in here. First we get the standard stuff, nothing special here as far as I can see. The CRAT table bit does looks suspicious, but it also happens during the init of my home Radeon RX 560 that otherwise works fine under Linux, so this does not seem to be a fatal issue... 771 �� [ 3.484654] [drm] amdgpu kernel modesetting enabled. 772 �� [ 3.484700] amdgpu: CRAT table not found 773 �� [ 3.484701] amdgpu: Virtual CRAT table created for CPU 774 �� [ 3.484707] amdgpu: Topology: Add CPU node ...then we get a power management failure, which may or may not be related to the problem at hand... 775 �� [ 3.484764] amdgpu 0000:01:00.0: can't change power state from D3hot to D0 (config space inaccessible) ...then more "normal" stuff, in the sense of stuff that looks close to what I see in the init logs of amdgpu on my RX 560... 776 �� [ 3.484888] [drm] initializing kernel modesetting (POLARIS12 0x1002:0x6981 0x1028:0x2B0D 0x10). 777 �� [ 3.484890] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported 778 �� [ 3.484895] [drm] register mmio base: 0x6E900000 779 �� [ 3.484896] [drm] register mmio size: 262144 780 �� [ 3.484898] [drm] add ip block number 0 <vi_common> 781 �� [ 3.484899] [drm] add ip block number 1 <gmc_v8_0> 782 �� [ 3.484899] [drm] add ip block number 2 <tonga_ih> 783 �� [ 3.484900] [drm] add ip block number 3 <gfx_v8_0> 784 �� [ 3.484900] [drm] add ip block number 4 <sdma_v3_0> 785 �� [ 3.484901] [drm] add ip block number 5 <powerplay> 786 �� [ 3.484901] [drm] add ip block number 6 <dm> 787 �� [ 3.484902] [drm] add ip block number 7 <uvd_v6_0> 788 �� [ 3.484902] [drm] add ip block number 8 <vce_v3_0> 789 �� [ 3.484913] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from VFCT 790 �� [ 3.484914] amdgpu: ATOM BIOS: 113-D0155200-100 791 �� [ 3.484932] [drm] vm size is 256 GB, 2 levels, block size is 10-bit, fragment size is 9-bit ...however, after this the driver tries to set up MMIO to communicate with the device, and here is where I think things go very wrong. 792 �� [ 3.485705] amdgpu 0000:01:00.0: BAR 2: releasing [mem 0x6100000000-0x61001fffff 64bit pref] 793 �� [ 3.485708] amdgpu 0000:01:00.0: BAR 0: releasing [mem 0x6000000000-0x60ffffffff 64bit pref] 794 �� [ 3.485709] [drm:amdgpu_device_resize_fb_bar [amdgpu]] *ERROR* Problem resizing BAR0 (-16). 795 �� [ 3.485811] amdgpu 0000:01:00.0: BAR 0: assigned [mem 0x6000000000-0x60ffffffff 64bit pref] 796 �� [ 3.485831] amdgpu 0000:01:00.0: BAR 0: error updating (0x00000c != 0xffffffff) 797 �� [ 3.485847] amdgpu 0000:01:00.0: BAR 0: error updating (high 0x000060 != 0xffffffff) 798 �� [ 3.485863] amdgpu 0000:01:00.0: BAR 2: assigned [mem 0x6100000000-0x61001fffff 64bit pref] 799 �� [ 3.485864] amdgpu 0000:01:00.0: BAR 2: error updating (0x00000c != 0xffffffff) 800 �� [ 3.485880] amdgpu 0000:01:00.0: BAR 2: error updating (high 0x000061 != 0xffffffff) 801 �� [ 3.485901] amdgpu 0000:01:00.0: amdgpu: VRAM: 4294967295M 0x000000FFFF000000 - 0x001000FFFEEFFFFF (4294967295M used) 802 �� [ 3.485903] amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x0000000000000000 - 0x000000000FFFFFFF 803 �� [ 3.485905] [drm] Detected VRAM RAM=4294967295M, BAR=4096M 804 �� [ 3.485906] [drm] RAM width 64bits UNKNOWN 805 �� [ 3.485913] [drm] amdgpu: 4294967295M of VRAM memory ready 806 �� [ 3.485914] [drm] amdgpu: 48026M of GTT memory ready. 807 �� [ 3.485916] [drm] GART: num cpu pages 65536, num gpu pages 65536 Failing to set up PCI BARs sounds bad, and concluding from this failed setup process that the GPU has 4 PiB of VRAM sounds even worse. I wouldn't be surprised if this were the point where things really went hopeless. But amdgpu is not the kind of program that will stop cleanly when the first error occurs, so it will first wait for an event that doesn't want to happen... 808 �� [ 3.600399] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! [...] 813 �� [ 3.714578] amdgpu 0000:01:00.0: amdgpu: Wait for MC idle timedout ! ...then emits a few more messages that also appear during the successful initialization process of my home RX 560, so which I consider "normal"... 814 �� [ 3.715166] [drm] PCIE GART of 256M enabled (table at 0x000000FFFF900000). 815 �� [ 3.716221] [drm] Chained IB support enabled! 816 �� [ 3.721721] amdgpu: hwmgr_sw_init smu backed is polaris10_smu ...and only then it dies brutally. 817 �� [ 3.726521] amdgpu: 818 �� last message was failed ret is 65535 819 �� [ 3.726522] amdgpu: 820 �� failed to send message 100 ret is 65535 821 �� [ 3.726525] amdgpu: SMC address must be 4 byte aligned. 822 �� [ 3.726525] amdgpu: [AVFS][Polaris10_SetupGfxLvlStruct] Problems copying VRConfig value over to SMC 823 �� [ 3.726526] amdgpu: [AVFS][Polaris10_AVFSEventMgr] Could not Copy Graphics Level table over to SMU 824 �� [ 3.726565] amdgpu: 825 �� last message was failed ret is 65535 826 �� [ 3.726566] amdgpu: 827 �� failed to send message 252 ret is 65535 828 �� [ 3.726566] amdgpu: 829 �� last message was failed ret is 65535 830 �� [ 3.726567] amdgpu: 831 �� failed to send message 253 ret is 65535 832 �� [ 3.726569] amdgpu: 833 �� last message was failed ret is 65535 834 �� [ 3.726570] amdgpu: 835 �� failed to send message 250 ret is 65535 836 �� [ 3.726571] amdgpu: 837 �� last message was failed ret is 65535 838 �� [ 3.726571] amdgpu: 839 �� failed to send message 251 ret is 65535 840 �� [ 3.726572] amdgpu: 841 �� last message was failed ret is 65535 842 �� [ 3.726573] amdgpu: 843 �� failed to send message 254 ret is 65535 844 �� [ 3.861852] [drm] Timeout wait for RLC serdes 0,0 [...] 846 �� [ 3.975981] amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring gfx test failed (-110) 847 �� [ 3.976112] [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v8_0> failed -110 848 �� [ 3.976241] amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_init failed 849 �� [ 3.976242] amdgpu 0000:01:00.0: amdgpu: Fatal error during GPU init 850 �� [ 3.976244] amdgpu 0000:01:00.0: amdgpu: amdgpu: finishing device. 851 �� [ 3.977567] amdgpu: probe of 0000:01:00.0 failed with error -110 852 �� [ 3.977650] [drm] amdgpu: ttm finalized --- So, to summarize, it seems something goes wrong at the MMIO setup stage, which may or may not be related to an earlier power management failure. My question is, how can I investigate this further? Here's some random trial and error stuff I already tried to no avail: - Upgrade the UEFI firmware. It's now at the latest release, and it did not change a thing. - Attempt to disable ASPM in case PCIe power management could be the issue (I found reports of an ASPM-related nvidia driver crash that started with the same ACPI error message at the beginning). Does not change anything here, rolled back. - Attempt to downgrade to an earlier amdgpu firmware, as this fixed a similar-looking crash on Arch. Did not help here, went back to the current AMD firmware. - Attempt to set the AMD GPU as the primary GPU in UEFI. This does not fix amdgpu initialization, and it breaks i915 initialization, which is definitely worse. Rolled back. -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 1189614] New: GPU hang problem in Kernel 5.13.8
by bugzilla_noreply＠suse.com 25 Nov '21

25 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189614 Bug ID: 1189614 Summary: GPU hang problem in Kernel 5.13.8 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: imbearchild(a)outlook.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- To who this may concerned, I've met some problem on OpenGL applications. The screen freezes, but the sound and interaction are normal, except that the screen output does not change. You can switch to the kernel terminal with the Ctrl-Alt-Fx key combination, but even after the process that caused the problem is killed, the screen display still freezes, and does not recover. Kernel has message like this: ``` [ 111.900829] Asynchronous wait on fence 0000:00:02.0:kwin_x11[2517]:e88 timed out (hint:intel_atomic_commit_ready [i915]) [ 114.621866] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out [ 114.621883] i915 0000:00:02.0: [drm] valley_x64[3756] context reset due to GPU hang [ 114.651360] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:85dffffb, in valley_x64 [3756] [ 115.549923] i915 0000:00:02.0: [drm] Resetting rcs0 for preemption time out [ 115.549949] i915 0000:00:02.0: [drm] valley_x64[3756] context reset due to GPU hang [ 115.582029] i915 0000:00:02.0: [drm] GPU HANG: ecode 9:1:87f97cf9, in valley_x64 [3756] ``` I've also found a similar bug a on older kernel, see: https://bugzilla.redhat.com/show_bug.cgi?id=1843274 but it should have been fixed on the latest kernel. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[kernel-bugs] [Bug 1178013] New: Application Crash when using FUSE
by bugzilla_noreply＠suse.com 24 Nov '21

24 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1178013 Bug ID: 1178013 Summary: Application Crash when using FUSE 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: reiokorn(a)tutanota.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please read this forum thread, with all the information about that bug that I can give you: https://forums.opensuse.org/showthread.php/546202-Cryptomator-Application-C… btw Leap is unaffected. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1188428] New: udev: failed to get device info: could not read 'authorized': No such file or directory
by bugzilla_noreply＠suse.com 08 Nov '21

08 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188428 Bug ID: 1188428 Summary: udev: failed to get device info: could not read 'authorized': No such file or directory 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: opensuse(a)mike.franken.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Starting with kernel 5.13.0-1 (Jul 09) on boot I always get an error message (see subject) from boltd regarding device cd010000-0060-XPS 9370. All messages from boltd: boltd[1189]: bolt 0.9.1 starting up. boltd[1189]: manager: initializing store boltd[1189]: store: located at: /var/lib/boltd boltd[1189]: config: loading user config boltd[1189]: bouncer: initializing polkit boltd[1189]: watchdog: enabled [pulse: 90s] boltd[1189]: udev: initializing udev boltd[1189]: store: loading domains boltd[1189]: [cd010000-0060-domain? ] store: loading domain boltd[1189]: journal: opened for 'cd010000-0060'; size: 0 bytes boltd[1189]: [cd010000-0060-domain? ] domain: registered (bootacl: 16/16) boltd[1189]: store: loading devices boltd[1189]: [00cd30c8-3205 ] store: loading device boltd[1189]: [cd010000-0060 ] store: loading device boltd[1189]: global 'generation' set to '3' boltd[1189]: [da010000-0070 ] store: loading device boltd[1189]: power: state located at: /run/boltd/power boltd[1189]: power: force power support: yes boltd[1189]: udev: found 1 domain boltd[1189]: udev: enumerating devices boltd[1189]: probing: adding /sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0 to roots boltd[1189]: [cd010000-0060-domain0 ] bootacl: synchronizing journal boltd[1189]: security level set to 'user' boltd[1189]: [cd010000-0060-domain0 ] connected: as domain0 [user] (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0) boltd[1189]: [cd010000-0060-XPS 9370 ] udev: failed to get device info: could not read 'authorized': No such file or directory boltd[1189]: [cd010000-0060-XPS 9370 ] parent is (null)... boltd[1189]: [cd010000-0060-XPS 9370 ] store: updating device boltd[1189]: [cd010000-0060-XPS 9370 ] connected: unknown (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0) boltd[1189]: [00cd30c8-3205-TS3 Plus ] parent is cd010000-0060... boltd[1189]: [00cd30c8-3205-TS3 Plus ] connected: authorized (/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:00.0/0000:05:00.0/domain0/0-0/0-3) boltd[1189]: [cd010000-0060-domain0 ] dbus: exported domain at /org/freedesktop/bolt/domains/cd010000_0060_6d18_a364_e809ccc32820 boltd[1189]: [00cd30c8-3205-TS3 Plus ] dbus: exported device at /org/freedesktop/bolt/devices/00cd30c8_3205... boltd[1189]: [cd010000-0060-XPS 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/cd010000_0060... boltd[1189]: [da010000-0070-XPS 13 9370 ] dbus: exported device at /org/freedesktop/bolt/devices/da010000_0070... boltd[1189]: probing: started [1000] boltd[1189]: [00cd30c8-3205-TS3 Plus ] udev: device changed: authorized -> authorized boltd[1189]: probing: timeout, done: [2974874] (2000000) System info: Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 8 �� Intel�� Core�� i7-8550U CPU @ 1.80GHz Memory: 15,0 GiB of RAM Graphics Processor: Mesa DRI Intel�� UHD Graphics 620 This is a DELL XPS 9370 notebook. -- You are receiving this mail because: You are the assignee for the bug.

1 9

[Bug 1190095] New: Kernel 5.13.12: Intel graphics suddenly very slow on redraw
by bugzilla_noreply＠suse.com 04 Nov '21

04 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190095 Bug ID: 1190095 Summary: Kernel 5.13.12: Intel graphics suddenly very slow on redraw 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: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I did a dup from 20210810 to 20210828, and since then I noticed a very slow redraw on KDE Plasma: when scolling in a terminal or in a window, the screen looks 'broken' for a moment, then the rendering is back. 30: PCI 02.0: 0300 VGA compatible controller (VGA) [Created at pci.386] Unique ID: _Znp.WlxwpsiDkK3 SysFS ID: /devices/pci0000:00/0000:00:02.0 SysFS BusID: 0000:00:02.0 Hardware Class: graphics card Model: "Intel CoffeeLake-H GT2 [UHD Graphics 630]" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x3e9b "CoffeeLake-H GT2 [UHD Graphics 630]" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x229f Driver: "i915" Driver Modules: "i915" Memory Range: 0xe9000000-0xe9ffffff (rw,non-prefetchable) Memory Range: 0xc0000000-0xcfffffff (ro,non-prefetchable) I/O Ports: 0x4000-0x403f (rw) Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled) IRQ: 143 (1116926 events) Module Alias: "pci:v00008086d00003E9Bsv000017AAsd0000229Fbc03sc00i00" Driver Info #0: Driver Status: i915 is active Driver Activation Cmd: "modprobe i915" Config Status: cfg=new, avail=yes, need=no, active=unknown Switching to nvidia chipset (prime-select) the issue is gone Other users to confirm this issue (see factory mailing list) -- You are receiving this mail because: You are the assignee for the bug.

1 18

[Bug 1190200] New: Severe graphics glitches in KDE applications when compositor is disabled
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190200 Bug ID: 1190200 Summary: Severe graphics glitches in KDE applications when compositor is disabled 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: psychonaut(a)nothingisreal.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I normally run KDE with the compositor disabled. In this mode, all KDE applications exhibit severe screen corruption: all new text or graphics that appear have a garbled appearance, to the extent that text is completely illegible. The corruption sometimes disappears after a few seconds or after the window is scrolled. The problem does not affect GTK+ applications. The problem can be worked around by using systemsettings5 to tell KDE to enable the compositor at startup. However, simply changing the rendering backend (XRender vs. OpenGL) has no effect. I am using an onboard Intel HD Graphics 630 controller with the i915 driver. I'm not sure if it's the kernel driver/firmware which is causing the problem, but based on past experience with Intel graphics glitches, I am tentatively assuming it is. The problem occurred after updating Tumbleweed from version 20210810 to version 20210827. (In case it's relevant, this included an update of kernel-default 5.13.8 to 5.13.12, and from kernel-firmware-i915 from 20210719 to 20210812.) The problem persists in version 20210830. Booting from the old 5.13.8 kernel doesn't work around the problem. I could also try reverting kernel-firmware-i915 if I can find or build an old package. -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 1180749] New: AMD Ryzen 4800H Integrated Graphics brightness control not working as found in some Lenovo Legion 5 15ARH05
by bugzilla_noreply＠suse.com 31 Oct '21

31 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1180749 Bug ID: 1180749 Summary: AMD Ryzen 4800H Integrated Graphics brightness control not working as found in some Lenovo Legion 5 15ARH05 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: antonyjr000(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When using switchable graphics in Lenovo Legion 5 15ARH05, the AMD Renoir APU works along with NVIDIA Graphics(even non-free and prime works) but the brightness cannot be controlled by the Fn keys, Software or /sys/class/backlight I've tried setting all the kernel params like acpi_backlight=vender or native but the brightness control still does not work. I highly suspect it's a bug in the amdgpu kernel driver. For now nvidia graphics card works with brightness control. It is also worthy to note that cat /sys/class/backlight/*/actual_brightness always returns 311 and does not change even when executed echo 50 > /sys/class/backlight/*/brightness There are number of reports on this issue over the internet but nothing official. I've tried a lot of linux distros and none of them work and it seems it is broken even in the mainline kernel. I've also tried Kernel:HEAD version of the kernel without the nvidia graphics support but still the brightness control does not work. At the time writing I've booted linux 5.11-rc2 but the brightness control still does not work. -- You are receiving this mail because: You are the assignee for the bug.

1 36

[Bug 1190986] New: nouveau broken in 5.14.5-1 does not load
by bugzilla_noreply＠suse.com 30 Oct '21

30 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190986 Bug ID: 1190986 Summary: nouveau broken in 5.14.5-1 does not load Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: qwert.zuiop(a)byom.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Reading other reddit posts on this issue, systems with nvidia don't boot any more apparently, nouveau is broken and not loading any more. On my AMD+Nvdia notebook, only AMD works now and nvidia nouveau drivers don't load @localhost:~> sudo lspci -nnk | grep -iA2 vga 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) Subsystem: ASUSTeK Computer Inc. Device [1043:16ff] Kernel modules: nouveau -- 06:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c7) Subsystem: ASUSTeK Computer Inc. Device [1043:16ff] Kernel driver in use: amdgpu -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1189772] New: initrds get built by posttrans scripts despite no kernel package installed
by bugzilla_noreply＠suse.com 27 Oct '21

27 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189772 Bug ID: 1189772 Summary: initrds get built by posttrans scripts despite no kernel package installed Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: patrick.schaaf(a)yalwa.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm using tumbleweed for production virtual machines (KVM host) with host side externnal kernels, and no initrd inside the virtual machine. That setup appeals because it saves a bit of time during zypper dup'ping the VMs, avoiding any initrd rebuild per VM. Since a month or two ago, I notice that tumbleweed started to nevertheless build initrds again, from %posttrans scripts of packages like coreutils or dracut, for the actually running kernel version, even if no vmlinuz or anything except a /boot/config-VER symlink (of my own making) exists inside the VM. Not a huge problem for sure, but it would be nice if that could be changed, e.g. by only building an initrd if a corresponding /boot/vmlinuz-VER exists. -- You are receiving this mail because: You are the assignee for the bug.

1 5