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 1227194] New: ‘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 Bug ID: 1227194 Summary: ‘mount -t cifs’ then ‘ls /mnt’ causes “soft lockup - CPU#0 stuck”. Can’t kill -9 nor init s, etc Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: hattons(a)speakeasy.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/115.0 Build Identifier: Every time I do: USS-Liberty:~ # mount -t cifs //192.168.99.78/elements -o username=hattons /mnt/elements Password for hattons(a)//192.168.99.78/elements: followed by ‘ls /mnt’, I get 2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764] etc. I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to get stuck on other processes. I haven’t been using Linux for several years, but in the good old days, this wasn’t supposed to happen. Reproducible: Always Steps to Reproduce: 1. # mount -t cifs //192.168.99.78/<share> -o username=<user> /mnt/<mount point> 2. ‘ls /mnt’ 3. Actual Results: I get repeated messages of the form 2024-06-27T03:48:38.093101-04:00 USS-Liberty kernel: [ 2664.161932][ C0] watchdog: BUG: soft lockup - CPU#0 stuck for 1643s! [ls:5764] I can’t ‘kill -9 5764’, ‘reboot’, ‘halt’, ‘init s’, etc. Other CPUs start to get stuck on other processes. Expected Results: Expected the remote share to either be mounted an ls to show me the contents of /mnt, or receive an error indicating a failure of the mount and/or ls commands. This is very deterministic. I have nothing to compare it to because it is my first Linux install in years, and I don't have a second machine to test with. There is, however, this: https://forums.opensuse.org/t/mount-t-cifs-then-ls-mnt-causes-soft-lockup-c… Unfortunately, I did a reinstall since I last crashed the machine, so I don't have logs. If you can't reproduce the result, I will try again. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1227450] New: JeOS-efi-pxe.aarch64 fails to build on 15.5
by bugzilla_noreply＠suse.com 05 Jul '24

05 Jul '24

https://bugzilla.suse.com/show_bug.cgi?id=1227450 Bug ID: 1227450 Summary: JeOS-efi-pxe.aarch64 fails to build on 15.5 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Live Medium Assignee: fvogt(a)suse.com Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- For some reason the image fails to build now because "pgrep" is missing, which is needed indirectly: [ 419s] dracut: dracut module 'network-legacy' will not be installed, because command 'pgrep' could not be found! [ 419s] dracut: 62bluetooth: Could not find any command of '/usr/lib/bluetooth/bluetoothd /usr/libexec/bluetooth/bluetoothd'! [ 419s] dracut: dracut module 'dmraid' will not be installed, because command 'dmraid' could not be found! [ 419s] dracut: dracut module 'network-legacy' will not be installed, because command 'pgrep' could not be found! [ 419s] dracut: dracut module 'network' depends on 'network-legacy', which can't be installed [ 419s] dracut: dracut module 'kiwi-dump' depends on 'network', which can't be installed I don't know which change causes this, but the easiest fix is probably to just add it to the image? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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