July 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1227194] ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c8 --- Comment #8 from Enzo Matsumiya <ematsumiya(a)suse.com> --- Thanks for confirming. I checked if I was using 'nohandlecache' on my test systems and I wasn't. So the problem is in my build system, that I'm still puzzled as I can't reproduce the bug with my self-built kernel. I'm suspecting probably some kernel config, but will update the bug once I get the fix. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227457] New: Snapper error message after choosing System's Log in Yast via the shell
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227457 Bug ID: 1227457 Summary: Snapper error message after choosing System's Log in Yast via the shell 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: ada.lovelace(a)gmx.de QA Contact: jsrain(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Created attachment 875913 --> https://bugzilla.suse.com/attachment.cgi?id=875913&action=edit y2logs I wanted to test/use Yast via the commandline/shell (in openSUSE Tumbleweed) since a longer time. I have done the following steps: 1) Open the terminal 2) Enter yast 3) Choose "Miscellaneous" 4) Choose "System's log" Yast has been closed shortly with the message: Server-side plugin '/usr/lib/snapper/plugins/10-sdbootutil.snapper' failed. Yast will be reopened with the log file /var/log messages. The error is appearing after every call of this Yast module. The yast log is attached. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227194] ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c7 --- Comment #7 from Rolf Wentland <R.Wentland(a)gmx.de> --- On my system the lookup occurs only with a Windows 11 23H2 machine. A FritzBox is a common SOHO router in Germany that provides a NAS option. Cifs mount does work without problem with the router box. I do not know what software is used in the router. Mounting the Windows 11 share with option 'nohandlecache' does solve the problem. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227194] ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c6 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hattons(a)speakeasy.net Flags| |needinfo?(hattons@speakeasy | |.net) --- Comment #6 from Enzo Matsumiya <ematsumiya(a)suse.com> --- Nevermind, I can reproduce it. Fix coming soon. Meanwhile, I used 'nohandlecache' mount option and it dint't hang. Let me know what you get if you try it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227194] ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227194 https://bugzilla.suse.com/show_bug.cgi?id=1227194#c5 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(R.Wentland(a)gmx.de | |), | |needinfo?(gross.jonas@gmail | |.com) --- Comment #5 from Enzo Matsumiya <ematsumiya(a)suse.com> --- (In reply to Rolf Wentland from comment #2) > I can reproduce this with kernel 6.4.0-150600.23.7-default and a Windows 11 > share. Mount command gives no error. System is freezing after ls /mnt until > power cycle see attached log snippet. A cifs share from a FritzBox router > works for me with no problems so far. Are you saying that the lockup only happens when you mount the share that's on Windows 11? I don't know FritzBox, but I'm assuming they use samba, or their own version of it. Do you have other servers you can try mounting cifs shares from? @Jonas what kind of server are you mounting from? Internal automated tests are done with Windows Server 2022 and samba shares -- such trivial task would've been catched easily. Hence why I'm asking if a different server yields different results on the cifs.ko client. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1226010] obs-service-kiwi_metainfo_helper does not consider Dockerfile.FLAVOR in _multibuild projects
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1226010 https://bugzilla.suse.com/show_bug.cgi?id=1226010#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to OBSbugzilla Bot from comment #1) > This is an autogenerated message for OBS integration: > This bug (1226010) was mentioned in > https://build.opensuse.org/request/show/1179156 Tools / > obs-service-kiwi_metainfo_helper SR got accepted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1225985] obs-service-docker_label_helper does not consider Dockerfile.FLAVOR in _multibuild projects
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1225985 https://bugzilla.suse.com/show_bug.cgi?id=1225985#c2 Fabian Vogt <fvogt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Fabian Vogt <fvogt(a)suse.com> --- (In reply to OBSbugzilla Bot from comment #1) > This is an autogenerated message for OBS integration: > This bug (1225985) was mentioned in > https://build.opensuse.org/request/show/1179155 Tools / > obs-service-docker_label_helper SR got accepted. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1227349] New: Installation not working - failed to compute default context
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227349 Bug ID: 1227349 Summary: Installation not working - failed to compute default context Classification: openSUSE Product: openSUSE Aeon Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: rbrown(a)suse.com Reporter: ruebe(a)mailbox.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875852 --> https://bugzilla.suse.com/attachment.cgi?id=875852&action=edit tik.log file Just tried to install Aeon. But it is not working, I get the same error as hjfrack on 3.6.2024 as described in the Matrix-Group. Here is the error again: You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot", or "exit" to continue bootup. sulogin: failed to compute default context sulogin: tcgetattr failed: Input/output error So I add a config.ign to the ignition Partition and added a root password. The tik.log file is below. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1227453] New: NO output via HDMI after Grub menu - Khadas Vim 3 Pro
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227453 Bug ID: 1227453 Summary: NO output via HDMI after Grub menu - Khadas Vim 3 Pro Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: amach(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 875910 --> https://bugzilla.suse.com/attachment.cgi?id=875910&action=edit Informations - Test Tumbleweed and Ubuntu Grub menu is visible on Dell U3415W monitor, but after Grub menu no output via HDMI anymore - Notes: 1- I've tested with image: https://mirrorcache-eu.opensuse.org/ports/aarch64/tumbleweed/appliances/ope… Result: NO output via HDMI after Grub menu 2- I've tested with image: https://dl.khadas.com/products/vim3/firmware/ubuntu/generic/vim3-ubuntu-24.… Result: Normal output via HDMI after Grub menu - Here snippet from Tumbleweed test: [ 26.488688][ T1125] Call trace: [ 26.491792][ T1125] meson_dw_hdmi_unbind+0x18/0x40 [meson_dw_hdmi 27a1be21cf3c481ffabdfa9568398cdcc7e24e79] [ 26.501540][ T1125] component_unbind+0x40/0x70 [ 26.506023][ T1125] component_unbind_all+0xcc/0xe0 [ 26.510853][ T1125] meson_drv_bind_master+0x1f4/0x560 [meson_drm 9e4ac0153e3c2b25677d58fc27c19ec8d14612bd] [ 26.520515][ T1125] meson_drv_bind+0x1c/0x30 [meson_drm 9e4ac0153e3c2b25677d58fc27c19ec8d14612bd] [ 26.529398][ T1125] try_to_bring_up_aggregate_device+0x21c/0x2f0 [ 26.535434][ T1125] component_master_add_with_match+0xc8/0x110 [ 26.541299][ T1125] meson_drv_probe+0x1e4/0x200 [meson_drm 9e4ac0153e3c2b25677d58fc27c19ec8d14612bd] [ 26.550443][ T1125] platform_probe+0x70/0xe0 [ 26.554754][ T1125] really_probe+0xc8/0x3a0 [ 26.558980][ T1125] __driver_probe_device+0x84/0x160 [ 26.563983][ T1125] driver_probe_device+0x44/0x120 [ 26.568813][ T1125] __driver_attach+0xf8/0x210 [ 26.573298][ T1125] bus_for_each_dev+0x80/0xf0 [ 26.577783][ T1125] driver_attach+0x2c/0x40 [ 26.582009][ T1125] bus_add_driver+0x118/0x250 [ 26.586494][ T1125] driver_register+0x70/0x140 [ 26.590979][ T1125] __platform_driver_register+0x30/0x50 [ 26.596327][ T1125] meson_drm_platform_driver_init+0x30/0xff8 [meson_drm 9e4ac0153e3c2b25677d58fc27c19ec8d14612bd] [ 26.606678][ T1125] do_one_initcall+0x4c/0x360 [ 26.611161][ T1125] do_init_module+0x68/0x260 [ 26.615560][ T1125] load_module+0x1c30/0x22f8 [ 26.619959][ T1125] __do_sys_init_module+0x300/0x358 [ 26.624962][ T1125] __arm64_sys_init_module+0x24/0x40 [ 26.630050][ T1125] invoke_syscall+0x78/0x110 [ 26.634449][ T1125] el0_svc_common.constprop.0+0xc8/0xf0 [ 26.639797][ T1125] do_el0_svc+0x24/0x40 [ 26.643764][ T1125] el0_svc+0x40/0x190 [ 26.647559][ T1125] el0t_64_sync_handler+0x120/0x130 [ 26.652561][ T1125] el0t_64_sync+0x1a8/0x1b0 [ 26.656876][ T1125] Code: d503233f a9bf7bfd 910003fd f9403c00 (f9406400) [ 26.663604][ T1125] ---[ end trace 0000000000000000 ]--- <--- --- For testing Tumbleweed and Ubuntu the complete serial console output, dmesg, lsmod and other information's are attached. --- -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1156112] Docker does not work after boot.
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1156112 https://bugzilla.suse.com/show_bug.cgi?id=1156112#c12 Michal Hlavac <miso(a)hlavki.eu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Flags|needinfo?(miso(a)hlavki.eu) | Status|NEW |RESOLVED --- Comment #12 from Michal Hlavac <miso(a)hlavki.eu> --- Hi, This problem is not reproducible anymore. It was probably an upstream bug because I saw the same description in the docker bug tracker with a different distribution. Thank you -- You are receiving this mail because: You are on the CC list for the bug.

1 0