March 2024 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1211428] New: Steam deck speaker is quiet.
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211428 Bug ID: 1211428 Summary: Steam deck speaker is quiet. 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: monkeyboyted(a)yahoo.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hi everyone, Steam deck speakers finally works in both speakers. Speaker-test works. However, I also notice the sound is quiet compared to SteamOS. Can you fix it? speaker-test -Dplughw:1,1 -c2 Linux steamdeck.lan 6.4.0-rc2-1.g679133f-default #1 SMP PREEMPT_DYNAMIC Sun May 14 21:09:47 UTC 2023 (679133f) x86_64 x86_64 x86_64 GNU/Linux LSB Version: n/a Distributor ID: openSUSE Description: openSUSE Tumbleweed Release: 20230514 Codename: n/a -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 1219132] New: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware
by bugzilla_noreply＠suse.com 24 May '24

24 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1219132 Bug ID: 1219132 Summary: [Build 20240123] [6.7.1] Sysctl Sysctl_kernel_sched_energy_aware Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3889391/modules/Sysc tl/steps/136 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: openQA Blocker: Yes ## Observation # Test messages # Sysctl_kernel_sched_energy_aware # failure: ValueError: invalid literal for int() with base 10: '' Possibly this is a kernel issue - possibly the kernel just no longer exposes this and the test should not care. Please advise openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-sys-param-check@64bit fails in [Sysctl](https://openqa.opensuse.org/tests/3889391/modules/Sysctl/steps/136) ## Test suite description RAM size is set to 2048, some kernel parameters change with total RAM https://github.com/openSUSE/sys-param-check ## Reproducible Fails since (at least) Build [20240123](https://openqa.opensuse.org/tests/3888589) ## Expected result Last good: [20240122](https://openqa.opensuse.org/tests/3886345) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=opensus… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1211761] New: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines
by bugzilla_noreply＠suse.com 17 May '24

17 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1211761 Bug ID: 1211761 Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 URL: https://bugzilla.kernel.org/show_bug.cgi?id=217479 ; https://gitlab.freedesktop.org/drm/nouveau/-/issues/21 4 OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: mrmazda(a)earthlink.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Original Summary: vtty[1-6] nouveau framebuffers produce vast snow/raster on right and bottom border areas on the larger resolution of two displays, in the absence of both plymouth and video= on linu lines FTR: Upstream bugs: https://bugzilla.kernel.org/show_bug.cgi?id=217479 (includes most detail, w/ dmesg) https://gitlab.freedesktop.org/drm/nouveau/-/issues/214 To reproduce: 1-connect two unequal native resolution displays to a Tesla or Firmi GPU 2-don't have plymouth in use (I don't ever have it installed, so don't know whether it impacts) 3-don't include e.g. video=1440x900@60 directive on Grub's linu lines 4-boot TW 5-switch to a vtty, e.g. Ctrl-Alt-F3 Actual behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected (light text on black background) 3-Higher resolution display uses same pixels as lower resolution display, with light text on black background, leaving right side and bottom raster instead of black Expected behavior: 1-Both displays utilize the resolution (same pixel grid) of the lower resolution display 2-Lower resolution display behaves as expected 3-Entire higher resolution display's background is black instead of portions in raster Workaround: add e.g. video=1440x900@60 to Grub's linu lines, which causes both displays to use the same nominal mode on the full display space. Occurs with TW 6.3.2, 6.2.12 & 6.2.4 kernel-default, and with 6.2.15 on Fedora 38 and Mageia 9. Does not occur with TW 6.1.12 kernel-default on NVidia, or with AMD Caicos (Terascale2) GPU, or with Intel Eaglelake GPU. Tested only on legacy booting (no UEFI support). Others might describe what I call "raster" as multicolored snow. nosimplefb=1 doesn't change anything. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1213148] New: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2
by bugzilla_noreply＠suse.com 02 May '24

02 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1213148 Bug ID: 1213148 Summary: Atomisp results in tumbleweed being unable to boot on some atom computers since kernel 6.2 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 64bit OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: catice567(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Since kernel 6.2, my Tumbleweed refuses to boot because of intel isp. Ubuntu had this problem but they fixed it by disabling atomisp. I have a request to the openSUSE kernel maintainers: Can you please disable atomisp in your kernel, especially since this will affect Leap later on next year? -- You are receiving this mail because: You are the assignee for the bug.

1 6

[Bug 1221607] New: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup
by bugzilla_noreply＠suse.com 29 Apr '24

29 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221607 Bug ID: 1221607 Summary: Slowroll keeps reinstalling kernel and virtualbox on every zypper dup 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: llrainey15(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- zypper dup keeps installing the same 2 entries over and over slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Sun Mar 17 06:43:50 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (39.2 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (1.9 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:15:26 CDT 2024 slowroll:~ # Broadcast message from root@slowroll on pts/5 (Mon 2024-03-18 07:16:41 CDT): The system will reboot now! Connection to llr2 closed by remote host. Connection to llr2 closed. llrainey@LLR2:~> t2x 06 Last login: Mon Mar 18 07:14:23 CDT 2024 from 10.0.2.2 on ssh Have a lot of fun... slowroll:~ # zypper ref ; zypper -n dup Repository 'base-non-oss' is up to date. Repository 'base-oss' is up to date. Repository 'h264' is up to date. Repository 'packman' is up to date. Repository 'update' is up to date. All repositories have been refreshed. Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following 2 NEW packages are going to be installed: kernel-default-6.7.4-1.1 virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1 The following package requires a system reboot: kernel-default-6.7.4-1.1 2 new packages to install. Overall download size: 166.3 MiB. Already cached: 0 B. After the operation, additional 242.7 MiB will be used. Note: System reboot required. Continue? [y/n/v/...? shows all options] (y): y Retrieving: kernel-default-6.7.4-1.1.x86_64 (base-oss) (1/2), 165.8 MiB Retrieving: kernel-default-6.7.4-1.1.x86_64.rpm .............[done (30.6 MiB/s)] Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 (base-oss) (2/2), 546.5 KiB Retrieving: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64.[done (2.1 MiB/s)] Checking for file conflicts: .............................................[done] dracut[I]: Executing: /usr/bin/dracut -f /boot/initrd-6.7.4-1-default 6.7.4-1-default Lines Delete dracut[I]: *** Creating initramfs image file '/boot/initrd-6.7.4-1-default' done *** CA enrolled. Skip /etc/uefi/certs/1F673297.crt (1/2) Installing: kernel-default-6.7.4-1.1.x86_64 ........................[done] (2/2) Installing: virtualbox-kmp-default-7.0.14_k6.7.4_1-2.1.x86_64 ......[done] Running post-transaction scripts .........................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. Mon Mar 18 07:18:32 CDT 2024 -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1221504] New: bluetooth errors on every kernel starting
by bugzilla_noreply＠suse.com 26 Apr '24

26 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1221504 Bug ID: 1221504 Summary: bluetooth errors on every kernel starting Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: opendreas(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I have a Dell Precision 7530 with Intel Wireless-AC 9260 Bluetooth Adapter and kernel 6.4.0-150600.9.2. Errors constantly appear when booting the system, but bluetooth works with my headphones, although there are some audio artifacts at the beginning when playing sound. Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth daemon 5.71 Mär 16 17:49:38 precision bluetoothd[1073]: Starting SDP server Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support csip plugin Mär 16 17:49:38 precision bluetoothd[1073]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support micp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support vcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support mcp plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bass plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support bap plugin Mär 16 17:49:38 precision bluetoothd[1073]: src/plugin.c:plugin_init() System does not support admin plugin Mär 16 17:49:38 precision bluetoothd[1073]: Bluetooth management interface 1.22 initialized Mär 16 17:49:38 precision dbus-daemon[1074]: [system] Activating systemd to hand-off: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1' (uid=0 pid=1073 comm="/usr/lib/bluetooth/bluetoothd ") Mär 16 17:49:38 precision bluetoothd[1073]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Battery Provider Manager created Mär 16 17:49:38 precision bluetoothd[1073]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution Mär 16 17:49:38 precision bluetoothd[1073]: Failed to clear UUIDs: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision bluetoothd[1073]: Too small Add Device complete event Mär 16 17:49:38 precision bluetoothd[1073]: Failed to add UUID: Failed (0x03) Mär 16 17:49:38 precision (smartd)[1105]: smartd.service: Referenced but unset environment variable evaluates to an empty string: smartd_opts Looks like this is the error https://bugzilla.kernel.org/show_bug.cgi?id=217651 Here's a fix https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… -- You are receiving this mail because: You are the assignee for the bug.

1 21

[Bug 1220814] New: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?)
by bugzilla_noreply＠suse.com 21 Apr '24

21 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220814 Bug ID: 1220814 Summary: kernel 6.7.6-1-default Oops: unable to handle page faults and workqueue lockup (udev related?) Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: michael.burge77(a)gmail.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873182 --> https://bugzilla.suse.com/attachment.cgi?id=873182&action=edit full journalctl of the third crash I have an old portable with a wonky dc power jack which tends to generate a few quick AC0<->BAT0 events in succession. Starting with kernel 6.7.6-1-default the system locks up. Log is full of ``` Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:02 ost (udev-worker)[23694]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Process '/usr/sbin/tlp auto' terminated by signal KILL. Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to wait for spawned command '/usr/sbin/tlp auto': Input/output error Mar 01 17:34:17 ost (udev-worker)[24044]: AC0: Failed to execute '/usr/sbin/tlp auto', ignoring: Input/output error Mar 01 17:34:17 ost plasmashell[2682]: plasma-pk-updates: acPluggedChanged onBattery: false -> true Mar 01 17:34:17 ost kernel: BUG: unable to handle page fault for address: 0000000000007b8a Mar 01 17:34:17 ost kernel: #PF: supervisor read access in kernel mode Mar 01 17:34:17 ost kernel: #PF: error_code(0x0000) - not-present page ``` until it locks up with ``` Mar 01 18:11:29 ost kernel: note: kworker/11:5[23457] exited with irqs disabled Mar 01 18:11:50 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:54 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:55 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:11:58 ost plasmashell[5912]: [5912:0301/181158.744595:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. Mar 01 18:12:05 ost systemd-logind[1443]: Power key pressed short. Mar 01 18:12:06 ost kernel: BUG: workqueue lockup - pool cpus=11 node=0 flags=0x0 nice=0 stuck for 37s! ``` at which point only holding down the power button works. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1219180] New: Missing framebuffer during boot on aarch64
by bugzilla_noreply＠suse.com 16 Apr '24

16 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1219180 Bug ID: 1219180 Summary: Missing framebuffer during boot on aarch64 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/3891664/modules/ansi ble/steps/31 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tzimmermann(a)suse.com Target Milestone: --- Found By: openQA Blocker: --- Unless the initrd is built with the platform native DRM driver (e.g. virtio_gpu), there is no graphical output during boot. This also means that entering a passphrase for unlocking the root fs is not possible. On x86 it uses the EFI framebuffer successfully, but on aarch64 dmesg has no trace of efifb/simplefb/simpledrm. ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-sdboot-aarch64-microos-wizard@aarch64 fails in [ansible](https://openqa.opensuse.org/tests/3891664/modules/ansible/steps/31) ## Test suite description Like MicroOS, but use neither combustion nor ignition for the intial configuration, so jeos-firstboot runs. ## Reproducible Fails since (at least) Build [20231129](https://openqa.opensuse.org/tests/3771195) ## Expected result Last good: [20231127](https://openqa.opensuse.org/tests/3763820) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=microo… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1220541] New: kexec does a full reboot with kernel 6.7.6-1.1
by bugzilla_noreply＠suse.com 15 Apr '24

15 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1220541 Bug ID: 1220541 Summary: kexec does a full reboot with kernel 6.7.6-1.1 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: me(a)pavinjoseph.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Tested on identical systems with kexec-tools 2.0.27-3.2 (on both) and kernel 6.7.5-1.1 (on working system) and 6.7.6-1.1 (on faulty system). Faulty system (fully updated as of Feb 28 2024) is on Tumbleweed release 20240226. Working system is on release 20240222. Issue reproduced on working system by doing zypper ref and zypper in kernel-default to upgrade just the kernel to the latest version. Issue happens after the next cold boot and persists. -- You are receiving this mail because: You are the assignee for the bug.

1 7

[Bug 1218184] New: Eliminate the need for 'OBS source links': convert to _multibuild
by bugzilla_noreply＠suse.com 10 Apr '24

10 Apr '24

https://bugzilla.suse.com/show_bug.cgi?id=1218184 Bug ID: 1218184 Summary: Eliminate the need for 'OBS source links': convert to _multibuild Classification: SUSE ALP - SUSE Adaptable Linux Platform Product: Dolomite Version: Milestone 5 Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)suse.de Reporter: fcrozat(a)suse.com CC: dimstar(a)opensuse.org, dleuenberger(a)suse.com, fcrozat(a)suse.com, jslaby(a)suse.com, kernel-bugs(a)opensuse.org, mls(a)suse.com, msuchanek(a)suse.com, qa-bugs(a)suse.de, tiwai(a)suse.com Depends on: 1211226 Target Milestone: --- Group: SUSE Enterprise Partner Found By: --- Blocker: --- +++ This bug was initially created as a clone of Bug #1211226 +++ In order to prepare for 'git based source management', we need to fix up a few technical issues. One such issue is 'source links' not being supported in git (i.e in OBS we have openSUSE:Factory/kernel-source as the main package plus a bunch of 'linked packages', each with the name of the additional spec files) The solution is, technically seem, rather simple: using _multibuild multibuild support on OBS is known in two variants, one using a single spec file and conditionals inside the spec file based on @BUILD_FLAVOR@ (probably the more known way) but OBS also supports 'just' listing the additional spec files as 'flavors' the _multibuild to be added to the kernel-source (main package) can be generated like this:  #!/bin/sh echo "<multibuild>" > _multibuild for pkg in *.spec; do test "{$pkg}" == "kernel-source.spec" && continue echo " <package>${pkg/.spec/}</package>" >> _multibuild; done echo "</multibuild>" >> _multibuild  the spec files do not need to be changed in anyway with this method -- You are receiving this mail because: You are on the CC list for the bug.

1 59