October 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1191513] New: Dracut doesn't add modules defined in /etc/dracut.conf.d after updating kernel
by bugzilla_noreply＠suse.com 09 Oct '21

09 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191513 Bug ID: 1191513 Summary: Dracut doesn't add modules defined in /etc/dracut.conf.d after updating kernel 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: christophe(a)krop.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For some reason, the X session doesn't start if the nvidia modules is not in my initrd images. To do that, I have a config file in /etc/dracut.conf.d: # cat /etc/dracut.conf.d/10-DRIVER.conf force_drivers+=" nvidia nvidia_drm nvidia_modeset drm_kms_helper nvidia_uvm drm " *BUT* After updating the kernel, these modules are not added to the initrd image. Example after installing kernel-default-devel-5.14.6-2.1.x86_64 from journalctl: oct. 09 18:28:05 yuuko [RPM][618]: install kernel-default-devel-5.14.6-2.1.x86_64: success oct. 09 18:28:05 yuuko [RPM][618]: install kernel-default-devel-5.14.6-2.1.x86_64: success But: # lsinitrd -k 5.14.6-2-default | grep nvidia -rw-r--r-- 1 root root 18 Jul 26 2020 etc/modprobe.d/nvidia.conf -rw-r--r-- 1 root root 70 Sep 27 15:56 etc/modules-load.d/nvidia.conf -rw-r--r-- 1 root root 178 Sep 20 23:59 usr/lib/modprobe.d/09-nvidia-modprobe-bbswitch-G04.conf -rw-r--r-- 1 root root 49 Sep 20 23:59 usr/lib/modprobe.d/09-nvidia-modprobe-pm-G05.conf -rw-r--r-- 1 root root 1513 Sep 27 19:14 usr/lib/modprobe.d/50-nvidia-default.conf -rw-r--r-- 1 root root 18 Sep 21 15:04 usr/lib/modprobe.d/nvidia-default.conf Now if I invoke dracut manually: # dracut --force --hostonly --kver 5.14.6-2-default dracut: Executing: /usr/bin/dracut --force --hostonly --kver 5.14.6-2-default dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: dracut module 'systemd-repart' will not be installed, because command 'systemd-repart' could not be found! dracut: dracut module 'dbus-broker' will not be installed, because command 'dbus-broker' could not be found! dracut: dracut module 'rngd' will not be installed, because command 'rngd' could not be found! dracut: dracut module 'tpm2-tss' will not be installed, because command 'tpm2' could not be found! dracut: dracut module 'nvmf' will not be installed, because command 'nvme' could not be found! dracut: dracut module 'memstrack' will not be installed, because command 'memstrack' could not be found! dracut: memstrack is not available dracut: If you need to use rd.memdebug>=4, please install memstrack and procps-ng dracut: dracut module 'squash' will not be installed, because command 'mksquashfs' could not be found! dracut: dracut module 'squash' will not be installed, because command 'unsquashfs' could not be found! dracut: *** Including module: systemd *** dracut: *** Including module: systemd-initrd *** dracut: *** Including module: i18n *** dracut: *** Including module: btrfs *** dracut: *** Including module: crypt *** dracut: *** Including module: dm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 60-persistent-storage-dm.rules dracut: Skipping udev rule: 55-dm.rules dracut: *** Including module: kernel-modules *** dracut: *** Including module: kernel-modules-extra *** dracut: *** Including module: lvm *** dracut: Skipping udev rule: 64-device-mapper.rules dracut: Skipping udev rule: 56-lvm.rules dracut: Skipping udev rule: 60-persistent-storage-lvm.rules dracut: *** Including module: rootfs-block *** dracut: *** Including module: suse-btrfs *** dracut: *** Including module: suse-xfs *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: Skipping udev rule: 70-persistent-net.rules dracut: *** Including module: biosdevname *** dracut: *** Including module: dracut-systemd *** dracut: *** Including module: haveged *** dracut: *** Including module: ostree *** dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including module: suse *** dracut: *** Including module: suse-initrd *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done *** dracut: *** Hardlinking files *** dracut: *** Hardlinking files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin *** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: rd.driver.pre=btrfs dracut: rd.driver.pre=nvidia rd.driver.pre=nvidia_drm rd.driver.pre=nvidia_modeset rd.driver.pre=drm_kms_helper rd.driver.pre=nvidia_uvm rd.driver.pre=drm dracut: rd.luks.uuid=luks-e4d03a64-a035-4778-a9d3-5843b1f7bfb7 dracut: rd.lvm.lv=system/root rd.lvm.lv=system/swap dracut: root=/dev/mapper/system-root rootfstype=btrfs rootflags=rw,noatime,nodiratime,compress=zstd:3,ssd,space_cache,autodefrag,subvolid=256,subvol=/@,subvol=@ dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Creating image file '/boot/initrd-5.14.6-2-default' *** dracut: *** Creating initramfs image file '/boot/initrd-5.14.6-2-default' done *** Does the job and now the modules are correctly added: # lsinitrd -k 5.14.6-2-default | grep nvidia -rw-r--r-- 1 root root 18 Jul 26 2020 etc/modprobe.d/nvidia.conf -rw-r--r-- 1 root root 70 Sep 27 15:56 etc/modules-load.d/nvidia.conf drwxr-xr-x 3 root root 0 Oct 4 22:59 usr/lib/firmware/nvidia drwxr-xr-x 2 root root 0 Oct 4 22:59 usr/lib/firmware/nvidia/470.74 -rw-r--r-- 1 root root 35995584 Sep 21 15:02 usr/lib/firmware/nvidia/470.74/gsp.bin -rw-r--r-- 1 root root 178 Sep 20 23:59 usr/lib/modprobe.d/09-nvidia-modprobe-bbswitch-G04.conf -rw-r--r-- 1 root root 49 Sep 20 23:59 usr/lib/modprobe.d/09-nvidia-modprobe-pm-G05.conf -rw-r--r-- 1 root root 1513 Oct 4 22:59 usr/lib/modprobe.d/50-nvidia-default.conf -rw-r--r-- 1 root root 18 Sep 21 15:04 usr/lib/modprobe.d/nvidia-default.conf -rw-r--r-- 1 root root 138472 Oct 4 22:59 usr/lib/modules/5.14.6-2-default/updates/nvidia-drm.ko -rw-r--r-- 1 root root 42261464 Oct 4 22:59 usr/lib/modules/5.14.6-2-default/updates/nvidia.ko -rw-r--r-- 1 root root 1595712 Oct 4 22:59 usr/lib/modules/5.14.6-2-default/updates/nvidia-modeset.ko -rw-r--r-- 1 root root 2183240 Oct 4 22:59 usr/lib/modules/5.14.6-2-default/updates/nvidia-uvm.ko -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1191483] New: linux-glibc-devel contains scsi headers not upstream
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191483 Bug ID: 1191483 Summary: linux-glibc-devel contains scsi headers not upstream 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: msuchanek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- . -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1190193] Sabre Lite i.MX6 image contains invalid modules in dracut configuration
by bugzilla_noreply＠suse.com 08 Oct '21

08 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190193 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Assignee|kernel-bugs(a)opensuse.org |guillaume.gardet(a)arm.com -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190871] Higher than normal frequency for idle
by bugzilla_noreply＠suse.com 07 Oct '21

07 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190871 Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |giovanni.gherdovich(a)suse.co | |m -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1190871] Higher than normal frequency for idle
by bugzilla_noreply＠suse.com 07 Oct '21

07 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1190871 https://bugzilla.suse.com/show_bug.cgi?id=1190871#c10 --- Comment #10 from Giovanni Gherdovich <giovanni.gherdovich(a)suse.com> --- Hello, before getting into the detail of this report I need to clarify the difference between two kinds of frequency measurements: average frequency over active time (also called "BusyMHz") and average frequency over entire time (or "AvgMHz"). * BusyMHz: a CPU can be active, i.e. executing instructions (this is called "CO State") or switched off, inactive. There are several inctive states, called C1, C2, C3 etc. depending on how big of a portion of a CPU is taken offline. A CPU enters an inactive state to save energy; when in such state, it isn't executing anything and we can say the clock frequency is zero. BusyMHz is the average clock frequency (during the sampled interval) if we only consider C0 time, and dismiss all the time that's spent in all other C-States. You can be idling a lot (lots of non-C0 time) and still have a high BusyMHz, simply because of some brief activity spike (eg. processing interrupts). When the machine is not under load what's important is that AvgMHz is low, see next item. * AvgMHz: if we include all the non-C0 time (during which the CPU was powered off to some extent) in our average frequency calculation, we get AvgMHz. When not under load, this is expected to be near zero. Your measurement before and after the change were done using lscpu; there are two problems with that: 1. lscpu measures BusyMHz; the sampling time is very brief (less than 10 ms). This is not a good indication of "cpu is spinning fast even if I not doing anything". Again, BusyMHz can be high even if the machine is not under load. 2. lscpu only shows BusyMHz for the first cpu, CPU#0. It seems like this is an Intel CPU and I expect it to have multiple cores; the reason for the change in lscpu output could simply be something that used to be processed elsewhere is now processed on CPU#0. Without data on the full set of CPUs, we can't tell. Regarding how to measure the CPU frequency, the designated tool is turbostat(8), which in openSUSE is packaged in the cpupower package. Please run (as root) the following: turbostat --interval 1 This will sample all the data that's needed at intervals of 1 second, especially AvgMHz and BusyMHz from above, and Busy% which will tell the percentage of C0 time with respect to the total. What we want for an idle system is low values of AvgMHz and Busy%. Please let turbostat run for a minute or so, save the entire output and post as an attachment (including the header information, which shows a number of power-management related indicators). Also please show the entire `lscpu` output for information on the CPU model. Thanks, -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1189469] New: Linux Kernel 5.13.8 Crashes
by bugzilla_noreply＠suse.com 07 Oct '21

07 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1189469 Bug ID: 1189469 Summary: Linux Kernel 5.13.8 Crashes 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: mmanno(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm running k3d (4.4.6) on Tumbleweed's 5.13.8-1 kernel to install Kubernetes in Docker 20.10.6_ce-1.2. After installing Kubernetes with `k3d cluster create`, I try to install Epinio for testing. After some time, the kernel crashes and the machine reboots when the timeout in `/proc/sys/kernel/panic` is reached. Sometimes the crash occurs during the first installation of Epinio and its components, sometimes the crash occurs later, during testing. Even an incomplete installation will eventually crash the kernel. Other team members report a similar problem with the latest kernel. Going back to kernel 5.3.12-1 is the only workaround. I tried to create a kdump for the crash. Not sure if I should attach that, as it's 184mb? Here is the backtrace from dmesg: [ 1433.295401] general protection fault, probably for non-canonical address 0xb00fcd7a229657cd: 0000 [#1] SMP NOPTI [ 1433.295414] CPU: 0 PID: 26175 Comm: runc Kdump: loaded Tainted: G W OE 5.13.8-1-debug #1 openSUSE Tumbleweed [ 1433.295422] Hardware name: Dell Inc. Precision 5820 Tower X-Series/0X75JG, BIOS 2.4.0 07/06/2020 [ 1433.295426] RIP: 0010:kmem_cache_alloc_node_trace+0x79/0x2d0 [ 1433.295438] Code: 89 c6 48 85 c0 0f 84 b4 00 00 00 0f 1f 44 00 00 48 c7 44 24 10 00 00 00 00 e9 2a 01 00 00 0f 1f 44 00 00 41 8b 56 28 48 01 c2 <4c> 8b 02 48 89 d1 4d 33 86 b8 00 00 00 48 0f c9 49 31 c8 48 8d 4b [ 1433.295444] RSP: 0018:ffffab13052e3c88 EFLAGS: 00010282 [ 1433.295450] RAX: b00fcd7a229656cd RBX: 0000000000010a86 RCX: 0000000000000400 [ 1433.295454] RDX: b00fcd7a229657cd RSI: 0000000000000dc0 RDI: ffff8a7f00042a00 [ 1433.295458] RBP: 0000000000000dc0 R08: ffff8a8e52e34140 R09: ffff8a7f0809f800 [ 1433.295462] R10: 0000000000000011 R11: 0000000001320122 R12: ffff8a7f00042a00 [ 1433.295466] R13: 0000000000000000 R14: ffff8a7f00042a00 R15: ffffffffa34e6905 [ 1433.295470] FS: 00007f12e5e31f20(0000) GS:ffff8a8e52e00000(0000) knlGS:0000000000000000 [ 1433.295475] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 1433.295479] CR2: 00007f4f471adf08 CR3: 000000030dcfe006 CR4: 00000000003706f0 [ 1433.295483] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 1433.295486] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 1433.295490] Call Trace: [ 1433.295498] alloc_fair_sched_group+0xf5/0x1d0 [ 1433.295511] sched_create_group+0x2f/0x80 [ 1433.295522] cpu_cgroup_css_alloc+0xf/0x30 [ 1433.295529] cgroup_apply_control_enable+0x14e/0x330 [ 1433.295541] cgroup_mkdir+0x21f/0x470 [ 1433.295549] kernfs_iop_mkdir+0x54/0x80 [ 1433.295557] vfs_mkdir+0x12c/0x1e0 [ 1433.295565] do_mkdirat+0x127/0x150 [ 1433.295573] do_syscall_64+0x5e/0xb0 [ 1433.295585] ? syscall_exit_to_user_mode+0x18/0x40 [ 1433.295591] ? do_syscall_64+0x6e/0xb0 [ 1433.295599] ? syscall_exit_to_user_mode+0x18/0x40 [ 1433.295603] ? do_syscall_64+0x6e/0xb0 [ 1433.295610] ? syscall_exit_to_user_mode+0x18/0x40 [ 1433.295615] ? do_syscall_64+0x6e/0xb0 [ 1433.295622] ? do_syscall_64+0x6e/0xb0 [ 1433.295628] entry_SYSCALL_64_after_hwframe+0x44/0xae [ 1433.295637] RIP: 0033:0x4becdb [ 1433.295642] Code: fa ff eb bd e8 26 be fa ff e9 61 ff ff ff cc e8 3b 8d fa ff 48 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [ 1433.295647] RSP: 002b:000000c0000e8670 EFLAGS: 00000202 ORIG_RAX: 0000000000000102 [ 1433.295652] RAX: ffffffffffffffda RBX: 000000c00002e000 RCX: 00000000004becdb [ 1433.295656] RDX: 00000000000001ed RSI: 000000c0001401b0 RDI: ffffffffffffff9c [ 1433.295659] RBP: 000000c0000e86c8 R08: 0000000000000001 R09: 0000000000000001 [ 1433.295662] R10: 000000c0001401b0 R11: 0000000000000202 R12: ffffffffffffffff [ 1433.295665] R13: 0000000000000004 R14: 0000000000000003 R15: 0000000000000038 [ 1433.295674] Modules linked in: xt_owner xt_REDIRECT ipt_REJECT vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_statistic xt_mark vxlan ip6_udp_tunnel udp_tunnel xt_multiport xt_comment overlay xt_nat xt_tcpudp veth af_packet xt_conntrack xt_MASQUERADE nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib br_netfilter bridge stp llc nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_tables ebtable_nat ebtable_broute ip6table_nat ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_nat dm_thin_pool nf_conntrack dm_persistent_data dm_bio_prison dm_bufio nf_defrag_ipv6 nf_defrag_ipv4 iptable_mangle iptable_raw iptable_security ip_set nfnetlink ebtable_filter ebtables ip6table_filter rfkill ip6_tables iptable_filter ip_tables x_tables bpfilter intel_rapl_msr intel_rapl_common isst_if_common dmi_sysfs squashfs pktcdvd nfit libnvdimm snd_hda_codec_realtek snd_hda_codec_generic iTCO_wdt [ 1433.295771] intel_pmc_bxt x86_pkg_temp_thermal intel_powerclamp ledtrig_audio snd_hda_codec_hdmi coretemp iTCO_vendor_support dell_smm_hwmon kvm_intel snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec dell_wmi snd_hda_core snd_hwdep dell_smbios kvm dcdbas snd_pcm mei_me snd_timer sparse_keymap xfs irqbypass video e1000e snd dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof efi_pstore mei i2c_i801 ioatdma soundcore i2c_smbus dca nls_iso8859_1 nls_cp437 tiny_power_button vfat fat libcrc32c acpi_tad button loop fuse configfs uas usb_storage amdgpu crct10dif_pclmul crc32_pclmul crc32c_intel drm_ttm_helper ttm ghash_clmulni_intel iommu_v2 gpu_sched i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt xhci_pci fb_sys_fops xhci_pci_renesas cec xhci_hcd rc_core drm nvme usbcore nvme_core aesni_intel sr_mod crypto_simd cryptd cdrom serio_raw wmi vmd sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua msr efivarfs -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 1190434] crash is unable to find debuginfo of usrmerged kernel
by bugzilla_noreply＠suse.com 06 Oct '21

06 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1190434 http://bugzilla.opensuse.org/show_bug.cgi?id=1190434#c1 Ludwig Nussel <lnussel(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kernel-bugs(a)opensuse.org |dmair(a)suse.com --- Comment #1 from Ludwig Nussel <lnussel(a)suse.com> --- https://build.opensuse.org/request/show/923547 The search path is quite messy. There seem to be at least two code paths and there are references to /usr/src/redhat for example. Reassign to maintainer to decide whether aforementioned fix is good enough. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191247] audio goes to mono after waking up from sleep
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191247 http://bugzilla.opensuse.org/show_bug.cgi?id=1191247#c12 --- Comment #12 from Andrea P <pandre.x(a)gmail.com> --- (In reply to Takashi Iwai from comment #11) > Oh, and now I see you have Audient device in the card 0, judging from > alsa-info.sh output. In that case, test is like > aplay -Dplughw:0 somefile.wav > > The card index varies dynamically, so please check the output of "cat > /proc/asound/cards" beforehand. here I am! so, long story short: it doesn't matter what I do, after suspend the audio goes mono. In any single attempt I've checked if my sound card index was correct and it was. I tried to login as root and restart the usb module and as a matter of fact, it works straight away. so no "device or resource busy" anymore, but still, once I restart it the audio is still in mono. No idea if pulseaudio/pipewire still works even on Linux console, sorry. What else can I do for you? Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191322] Optimize building initrd when updating system
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191322 https://bugzilla.suse.com/show_bug.cgi?id=1191322#c3 Martin Wilck <martin.wilck(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #3 from Martin Wilck <martin.wilck(a)suse.com> --- (In reply to Takashi Iwai from comment #1) > There has been already discussions and some ongoing works about the > optimization of initrd creation. Indeed. We have an open feature request for SLE, and I'm actively working on this topic for the upcoming SUSE labs conference. There are plenty of ways to optimize this, and dare say I've explored most of them. We still have some way to go until all of this is properly tested and ready for release. (In reply to Michal Suchanek from comment #2) > posttrans is broken - it only runs on install, not on uninstall. > > When uninstalling the ramdisk has to be rebuilt right away. It's true in principle, but we'll be able to deal with this restriction. We shouldn't rebuild the initrd *at all* when we remove a kernel subpackage like kernel-default-extra. We currently don't anyway, because of bug 1191200, and haven't been doing it for more than a decade, without anyone complaining. In the vast majority of cases, when a kernel subpackage is removed, the corresponding base package is removed as well (because it happens in the course of a kernel update or purge-kernels run). Rebuilding the initrd for a kernel that's going to be removed a few seconds later is obviously a waste of time. In the remaining cases, someone may have installed kernel-default-extra or some other subpackage, realizes that he doesn't need/want it any more, and uninstalls it. He wouldn't do this if the kernel-default-extra contained any modules that were essential for his system to boot. And even if there were any (some crypto modules from -extra tend to be added to the initrd always), what harm would be done if they remain in the initrd while the package they belong to has been removed? The only reason to do that would be some abstract "correctness". But in practice, this doesn't justify to waste the users's time by rebuilding the initrd in the common case, when it's absolutely pointless. It's true that when the %preun or %postun scripts of a kernel subpackage is run, we have no way to determine whether or not the base package is going to be removed. AFAICT it's not possible to retrieve this information without changes in rpm, libzypp, or both. Therefore we have to make a guess, and we should guess that the base package will be removed, because it's the common case, and because we can't do harm if we guess wrong. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191260] kernel 5.14.8 post scriptlets failing
by bugzilla_noreply＠suse.com 05 Oct '21

05 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191260 https://bugzilla.suse.com/show_bug.cgi?id=1191260#c16 --- Comment #16 from Martin Wilck <martin.wilck(a)suse.com> --- > So is_supported is completely redundant. It isn't, and I told you why. You don't buy it, and I didn't expect you would. No point in continuing this debate, we both have far more important things to do. I hope we agree at least that the current code, with or without early exit, is far better readable and maintainable than anything we had during the years when the scriptlets were embedded in the rpm. If there's a real bug, show me. -- You are receiving this mail because: You are on the CC list for the bug.

1 0