November 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1192116] Kernel 5.14.14 performance slow
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192116 https://bugzilla.suse.com/show_bug.cgi?id=1192116#c5 --- Comment #5 from Jason Straight <jason-opensuse(a)straights.net> --- I'm afraid I spoke too soon. After the computer was on all night, the slowness is back this morning. How do I go about getting the source and compiling? I've compiled the kernel many times, but that was prior to about 15-20 yrs ago. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192291] New: 389-DS crash related to compactdb operation
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192291 Bug ID: 1192291 Summary: 389-DS crash related to compactdb operation Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: aliqrudi(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A bug has been discussed in the 389-users mailing list that results in 389-ds crashing when no replication is set up. The bug is reported by Nelson Bartley in the thread titled "Monthly internal scheduled task failure resulting in segfault, also...": https://www.spinics.net/linux/fedora/389-users/ I can reproduce this problem in OpenSUSE-Leap 15.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192288 https://bugzilla.suse.com/show_bug.cgi?id=1192288#c2 --- Comment #2 from Borislav Petkov <bpetkov(a)suse.com> --- Can you try the latest kernel from here: https://kernel.suse.com/SLE15-SP3.html ? It already has family 0x19 support... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192287] New: Creates extra snapshot 2 in MicroOS
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192287 Bug ID: 1192287 Summary: Creates extra snapshot 2 in MicroOS Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aplanas(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- A fresh MicroOS installation via YaST (MicroOS role) shows an extra snapshot2 that is not the default one: # snapper ls -a # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+--------------------------+------+------------+---------+-----------------------+-------------- 0 | single | | | root | | | current | 1* | single | | Wed Nov 3 09:36:13 2021 | root | 11.86 MiB | | first root filesystem | 2 | single | | Wed Nov 3 09:38:32 2021 | root | 10.16 MiB | number | after installation | important=yes After the first boot seems that the difference is only in the SElinux labels. The default one (1) currently have the labels, and not the second one (this is expected) # btrfs send --no-data -p /.snapshots/1/snapshot /.snapshots/2/snapshot | btrfs receive --dump | less (bunch of selinux and access time diffs) IMHO YaST / snapper should not create this second snapshot, as can cause confusion later during cleaning / rollback. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1192287] Creates extra snapshot 2 in MicroOS
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192287 https://bugzilla.suse.com/show_bug.cgi?id=1192287#c1 --- Comment #1 from Lukas Ocilka <locilka(a)suse.com> --- With the second snapshot you mean 2: "after installation"? Please attach YaST logs. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192288] New: amd64_edac_mod does not load after CPU upgrade
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1192288 Bug ID: 1192288 Summary: amd64_edac_mod does not load after CPU upgrade Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.3 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: seroton10(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a server running an AMD Ryzen 9 3900X CPU, I use the following output, written during boot, to verify that DRAM ECC is enabled: Oct 31 13:44:48 blackbox kernel: EDAC MC: Ver: 3.0.0 ... Oct 31 13:44:53 blackbox kernel: EDAC amd64: F17h_M70h detected (node 0). Oct 31 13:44:53 blackbox kernel: EDAC MC: UMC0 chip selects: Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 0: 0MB 1: 0MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 2: 8192MB 3: 8192MB Oct 31 13:44:53 blackbox kernel: EDAC MC: UMC1 chip selects: Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 0: 0MB 1: 0MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: MC: 2: 8192MB 3: 8192MB Oct 31 13:44:53 blackbox kernel: EDAC amd64: using x16 syndromes. Oct 31 13:44:53 blackbox kernel: EDAC amd64: Node 0: DRAM ECC enabled. Oct 31 13:44:53 blackbox kernel: EDAC amd64: MCT channel count: 2 Oct 31 13:44:53 blackbox kernel: EDAC MC0: Giving out device to module amd64_edac controller F17h_M70h: DEV 0000:00:18.3 (INTERRUPT) Oct 31 13:44:53 blackbox kernel: EDAC PCI0: Giving out device to module amd64_edac controller EDAC PCI controller: DEV 0000:00:18.0 (POLLED) Oct 31 13:44:53 blackbox kernel: AMD64 EDAC driver v3.5.0 Due to a CPU failure, I was forced to replace it, so decided to also upgrade to an AMD Ryzen 9 5900X CPU. (No other hardware or software changes were made.) Now I only see the first line mentioning EDAC in the log: Nov 02 13:28:54 blackbox kernel: EDAC amd64: F19h detected (node 0). Nov 02 13:28:54 blackbox kernel: EDAC amd64: Error: F0 not found, device 0x1650 (broken BIOS?) An attempt to manually load the AMD EDAC driver fails: # modprobe amd64_edac_mod modprobe: ERROR: could not insert 'amd64_edac_mod': No such device Would it be possible to add or backport the missing hardware support in the Leap 15.3 kernel, please? -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 https://bugzilla.suse.com/show_bug.cgi?id=1192278#c1 --- Comment #1 from Max Lin <mlin(a)suse.com> --- online repos path stays the same as *origin* 15.3 having, it looks like new built 15.3 Respin ftp-tree hasn't push to there properly, http://download.opensuse.org/distribution/leap/15.3/repo still contains 15.3-1 data, maybe symlink is wrong? Lubos? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1192278] packagekit cannot update 15.3-2 respin due to new product version
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1192278 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mlin(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188970] Xorg crashes with a segmentation fault when a secondary USB display using DisplayLink is connected
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

https://bugzilla.suse.com/show_bug.cgi?id=1188970 https://bugzilla.suse.com/show_bug.cgi?id=1188970#c49 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guek.neo@toshibag | |cs.com) --- Comment #49 from Stefan Dirsch <sndirsch(a)suse.com> --- Does this crash happen only during installation or also still on installed system? I'm asking since OpenGL driver is missing during installation (by intention; llvm libs are simply too big), but should be available on installed system. In order to do a successful installation, install *without* the USB Displaylink. After successful installation add it again and reboot. Also I would like to see a /var/log/Xorg.0.log for an installed system with USB Displaylink attached. Thanks. Notes for myself: [ 84.881] (EE) modeset(G0): glamor initialization failed [ 85.173] (II) Initializing extension MIT-SCREEN-SAVER [ 85.175] (EE) AIGLX error: dlopen of /usr/lib64/dri/swrast_dri.so failed (/usr/lib64/dri/swrast_dri.so: cannot open shared object file: No such file or directory) [ 85.175] (EE) AIGLX error: unable to load driver swrast [ 85.175] (EE) GLX: could not load software renderer [ 86.030] (EE) [ 86.030] (EE) Backtrace: [ 86.030] (EE) 0: Xorg (xorg_backtrace+0x65) [0x562700e315a5] [ 86.031] (EE) 1: Xorg (0x562700c7f000+0x1b6279) [0x562700e35279] [ 86.031] (EE) 2: /lib64/libpthread.so.0 (0x7f982b1e2000+0x13f80) [0x7f982b1f5f80] [ 86.031] (EE) 3: Xorg (xf86ProbeOutputModes+0xa0e) [0x562700d4cf2e] [ 86.031] (EE) 4: Xorg (0x562700c7f000+0xd6939) [0x562700d55939] [ 86.031] (EE) 5: Xorg (RRGetInfo+0x95) [0x562700d964f5] [ 86.031] (EE) 6: Xorg (0x562700c7f000+0x1209e7) [0x562700d9f9e7] [ 86.031] (EE) 7: Xorg (0x562700c7f000+0x5d018) [0x562700cdc018] [ 86.031] (EE) 8: Xorg (0x562700c7f000+0x6101c) [0x562700ce001c] [ 86.031] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f982ae3234d] [ 86.031] (EE) 10: Xorg (_start+0x2a) [0x562700cc9cba] [ 86.031] (EE) [ 86.031] (EE) Segmentation fault at address 0x0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188941] ppc64 optflags don't enable LTO
by bugzilla_noreply＠suse.com 03 Nov '21

03 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188941 http://bugzilla.opensuse.org/show_bug.cgi?id=1188941#c14 Martin Li��ka <martin.liska(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #14 from Martin Li��ka <martin.liska(a)suse.com> --- Fixed in devel project. -- You are receiving this mail because: You are on the CC list for the bug.

1 0