March 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1182377] kernel 5.10.16 snd_hda_intel (Audio device: NVIDIA Corporation GM107) spurious response 0x42490100:0x3331314d, rp = 0, wp = 0 with nvidia drivers
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182377 https://bugzilla.suse.com/show_bug.cgi?id=1182377#c27 --- Comment #27 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Created attachment 846862 --> https://bugzilla.suse.com/attachment.cgi?id=846862&action=edit kernel 5.11.2 RIP: 0010:kobject_put+0x19/0x1d0 and RIP: 0033:0x7fd93ce1c89e Typical 5.11 error which doesn't allow running system in single mode. I'm now running 5.10.16 (boot single, remove snd_hda_intel nvidia*, modprobe nvidia, snd_hda_intel) Can I test something else ? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182377] kernel 5.10.16 snd_hda_intel (Audio device: NVIDIA Corporation GM107) spurious response 0x42490100:0x3331314d, rp = 0, wp = 0 with nvidia drivers
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182377 https://bugzilla.suse.com/show_bug.cgi?id=1182377#c26 --- Comment #26 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Created attachment 846861 --> https://bugzilla.suse.com/attachment.cgi?id=846861&action=edit kernel 5.11.3 boot journal I've been forced to ctrl-alt-del during the process to stop the computer, and finally force poweroff manually after 3 minutes (umount doesn't want to respond) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1182377] kernel 5.10.16 snd_hda_intel (Audio device: NVIDIA Corporation GM107) spurious response 0x42490100:0x3331314d, rp = 0, wp = 0 with nvidia drivers
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182377 https://bugzilla.suse.com/show_bug.cgi?id=1182377#c25 Bruno Friedmann <bruno(a)ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bruno(a)ioda-net.ch | |) | --- Comment #25 from Bruno Friedmann <bruno(a)ioda-net.ch> --- With kernel 5.11.3 (or actual TW 5.11.2) there's a new RIP trace, which is worst as it doesn't allow to open rootfs (fully encrypted here) and doesn't allow single mode to start. Example extract mar 07 09:57:23 qt-kt kernel: CPU: 2 PID: 694 Comm: systemd-udevd Not tainted 5.11.3-1.g41a3f7e-default #1 openSUSE Tumbleweed (unreleased) mar 07 09:57:23 qt-kt kernel: Hardware name: Dell Inc. Precision 7510/0YH43H, BIOS 1.21.3 08/04/2020 mar 07 09:57:23 qt-kt kernel: RIP: 0010:kobject_put+0x19/0x1d0 mar 07 09:57:23 qt-kt kernel: Code: 48 c7 c7 48 33 e6 9a e8 85 b5 fe ff eb d6 0f 1f 00 48 85 ff 0f 84 b4 00 00 00 41 56 41 55 41 54 55 48 89 fd 53 bb ff ff ff ff <f6> 45 3c 01 0f 84 80 00 00 00 48 8d 7d 38 89 d8 f0 0f c1 45 38 83 mar 07 09:57:23 qt-kt kernel: RSP: 0018:ffffa9d640a4fd98 EFLAGS: 00010286 mar 07 09:57:23 qt-kt kernel: RAX: 0000000000000000 RBX: 00000000ffffffff RCX: 0000000000000000 mar 07 09:57:23 qt-kt kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: d111515f2ad71427 mar 07 09:57:23 qt-kt kernel: RBP: d111515f2ad71427 R08: 0000000000000001 R09: 0000000000000000 mar 07 09:57:23 qt-kt kernel: R10: 0000000000000001 R11: ffff889204881900 R12: d111515f2ad71427 mar 07 09:57:23 qt-kt kernel: R13: 0000000000007027 R14: ffffa9d640a4fe80 R15: 0000000000010000 mar 07 09:57:23 qt-kt kernel: FS: 00007f18f3717940(0000) GS:ffff88a144480000(0000) knlGS:0000000000000000 mar 07 09:57:23 qt-kt kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 mar 07 09:57:23 qt-kt kernel: CR2: 00005594d70a49e0 CR3: 0000000102ce0005 CR4: 00000000003706e0 mar 07 09:57:23 qt-kt kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 mar 07 09:57:23 qt-kt kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 mar 07 09:57:23 qt-kt kernel: Call Trace: mar 07 09:57:23 qt-kt kernel: kset_unregister+0x25/0x40 mar 07 09:57:23 qt-kt kernel: ? 0xffffffffc079f000 mar 07 09:57:23 qt-kt kernel: sysman_init+0x20a/0x1000 [dell_wmi_sysman] mar 07 09:57:23 qt-kt kernel: do_one_initcall+0x44/0x1d0 mar 07 09:57:23 qt-kt kernel: ? kmem_cache_alloc_trace+0xfe/0x250 mar 07 09:57:23 qt-kt kernel: do_init_module+0x5c/0x260 mar 07 09:57:23 qt-kt kernel: __do_sys_init_module+0x13b/0x1c0 mar 07 09:57:23 qt-kt kernel: do_syscall_64+0x33/0x80 mar 07 09:57:23 qt-kt kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 mar 07 09:57:23 qt-kt kernel: RIP: 0033:0x7f18f437889e mar 07 09:57:23 qt-kt kernel: Code: 48 8b 0d d5 15 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 af 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a2 15 0c 00 f7 d8 64 89 01 48 mar 07 09:57:23 qt-kt kernel: RSP: 002b:00007ffcb78a4118 EFLAGS: 00000246 ORIG_RAX: 00000000000000af mar 07 09:57:23 qt-kt kernel: RAX: ffffffffffffffda RBX: 00005594d709ba40 RCX: 00007f18f437889e mar 07 09:57:23 qt-kt kernel: RDX: 00007f18f44b93a3 RSI: 0000000000017027 RDI: 00005594d78aa8a0 mar 07 09:57:23 qt-kt kernel: RBP: 00005594d78aa8a0 R08: 00005594d709a260 R09: 0000000000000003 mar 07 09:57:23 qt-kt kernel: R10: 000055918e440d6a R11: 0000000000000246 R12: 00007f18f44b93a3 mar 07 09:57:23 qt-kt kernel: usb 1-5.2: new full-speed USB device number 14 using xhci_hcd mar 07 09:57:23 qt-kt kernel: R13: 00005594d7097d30 R14: 0000000000000000 R15: 00005594d7099370 mar 07 09:57:23 qt-kt kernel: Modules linked in: joydev ecc mc dell_wmi_sysman(+) dell_smbios fjes(-) dcdbas pcc_cpufreq(-) sparse_keymap intel_wmi_thunderbolt dell_wmi_descriptor acpi_cpufreq(-) cfg80211 i2c_i801 mxm_wmi wmi_bmof i2c_smbus e1000e(+) mei_me processor_thermal_device processor_thermal_rfim mei processor_thermal_mbox processor_thermal_rapl intel_pch_thermal intel_rapl_common ie31200_edac intel_soc_dts_iosf thermal tiny_power_button parport_pc int3403_thermal dell_rbtn int3400_thermal int3402_thermal ac parport dell_smo8800 acpi_pad int340x_thermal_zone acpi_thermal_rel rfkill button nls_iso8859_1 nls_cp437 vfat fat drm fuse configfs hid_logitech_hidpp uas usb_storage hid_logitech_dj dm_crypt hid_generic usbhid crct10dif_pclmul rtsx_pci_sdmmc xhci_pci xhci_pci_renesas crc32_pclmul ghash_clmulni_intel mmc_core aesni_intel nvme glue_helper crypto_simd xhci_hcd serio_raw cryptd usbcore rtsx_pci nvme_core battery video wmi btrfs blake2b_generic libcrc32c crc32c_intel xor raid6_pq dm_mirror mar 07 09:57:23 qt-kt kernel: dm_region_hash dm_log snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation snd_soc_core snd_compress snd_pcm_dmaengine soundwire_cadence soundwire_bus snd_hda_codec snd_hwdep snd_hda_core snd_pcm snd_timer snd soundcore l2tp_ppp l2tp_netlink l2tp_core ip6_udp_tunnel udp_tunnel pppox ppp_generic slhc sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua br_netfilter bridge stp llc msr efivarfs mar 07 09:57:23 qt-kt kernel: ---[ end trace 92237ce006e414fd ]--- I will attach the whole journal from this sessions. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183136] New: Wrong ownership of home directories
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183136 Bug ID: 1183136 Summary: Wrong ownership of home directories Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: robert.martin(a)martronix.im QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Initial installation from snapshot openSUSE-Tumbleweed-DVD-x86_64-Snapshot20210302-Media.iso When a user is created, as part of the installation process, some of the directories created within the users home directory, such as .config, are owned by root. This causes problems when KDE tries to write to them. The workaround was to go to a terminal session and change the ownerships manually prior to the first login to the KDE desktop. The installation was redone and the errors were the same. If a second user is created afterwards, via yast, the directories are created with the correct ownership. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183134] New: kde taskbar menu is translucent - always
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183134 Bug ID: 1183134 Summary: kde taskbar menu is translucent - always Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: erbenton(a)comcast.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- openSUSE Tumbleweed 20210115 (x86_64) KDE 5.78.0 Plasma 5.20.5 Qt: 5.15.2 The kde start menu (and taskbar), is always see-through, to the point its hard to read. In "System-Settings->Workspace-Behavior->Desktop-Effects" I tried setting translucent to unchecked - no joy, so i then checked it and set menu's to full opaque - still no joy, then i set everything to opaque and it still didn't work. This is reproducible on 2 different machines. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1181249] New: XFCE terminal not respecting font style preferences
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1181249 Bug ID: 1181249 Summary: XFCE terminal not respecting font style preferences Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: i686 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: suseino(a)riseup.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ rpm -q xfce4-terminal xfce4-terminal-0.8.10-1.1.i586 Unlike in previous versions, terminal preferences don't seem to respect font style selection any more. Example: Source Code Pro Regular 16 Source Code Pro Semibold 16 Source Code Pro Black 16 Source Code Pro ExtraLight Italic 16 all show the exact same font with no change whatsoever (yes "Use system font is unchecked"). In previous versions this worked as expected. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1182377] kernel 5.10.16 snd_hda_intel (Audio device: NVIDIA Corporation GM107) spurious response 0x42490100:0x3331314d, rp = 0, wp = 0 with nvidia drivers
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1182377 https://bugzilla.suse.com/show_bug.cgi?id=1182377#c24 --- Comment #24 from Bruno Friedmann <bruno(a)ioda-net.ch> --- Hi Takashi, thanks for the kernel, I will install and test it this sunday. A followup with the actual Tumbleweed 5.10.16-1-default and the new nvidia drivers 460.56-35.1 There's still a crash if I let the computer running normally (boot + autologin on X11 kde plasma) Rip trace + black screen and nivida module crashed (can't be removed, nor Xorg.bin be killable) If I start with single, I can enter maintenance console (in dmesg there's no RIP) I remove with snd_hda_intel then all nvidia stack (rmmod nvidia_drm nvidia_uvm nvidia_modeset nvidia) then I load manually the two module modprobe -v nvidia modprobe -v snd_hda_intel then exit and continue the normal boot, everything run fine afterwards. So the loading order seems to have an impact. -- So now I will test the 5.11 version. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183131] New: Hundreds of weird systemd-sysv-convert warnings
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183131 Bug ID: 1183131 Summary: Hundreds of weird systemd-sysv-convert warnings Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: criguada+opensuse(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- *Summary:* With every new update I have an increasing number of weird warning messages. They don't seem to affect system stability now, but I fear it could be affected in the future. *Linux kernel version used (uname -a):* Linux polarisuse 5.10.16-1-default #1 SMP Sat Feb 13 16:20:19 UTC 2021 (11381f3) x86_64 x86_64 x86_64 GNU/Linux *Unexpected behaviour you saw:* during update (zypper dup) I get hundreds of warning messages like these: systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping systemd-sysv-convert: warning, /usr/lib/systemd/system/--global.service not found, skipping *Steps to reproduce the problem:* simply issue the zypper dup command *Additional program output to the terminal or log subsystem illustrating the issue:* See https://gist.github.com/Cris70/fb42961ecd185aadabae1817ca426b40 -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1063638] btrfs balance renders system unresponsive and eventually even kills WiFi when quota is enabled - review I/O scheduling parameters of btrfsmaintenance
by bugzilla_noreply＠suse.com 07 Mar '21

07 Mar '21

https://bugzilla.suse.com/show_bug.cgi?id=1063638 https://bugzilla.suse.com/show_bug.cgi?id=1063638#c251 --- Comment #251 from Oliver Kurz <okurz(a)suse.com> --- This is an autogenerated message for openQA integration by the openqa_review script: This bug is still referenced in a failing openQA test: system_performance@64bit-2G https://openqa.opensuse.org/tests/1655448 To prevent further reminder comments one of the following options should be followed: 1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted 2. The openQA job group is moved to "Released" 3. The label in the openQA scenario is removed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1183127] New: Access tu exfat
by bugzilla_noreply＠suse.com 06 Mar '21

06 Mar '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1183127 Bug ID: 1183127 Summary: Access tu exfat Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: we_wolff(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have only access to my exfat-Micro-SD-Card after using stand-by-mode. -- You are receiving this mail because: You are on the CC list for the bug.

1 1