Bug#948257: initramfs-tools: Issue confirmation

[xiscu]

Package: initramfs-tools
Version: 0.135
Followup-For: Bug #948257

Dear Maintainer,
I can confirm that issue:

Processing triggers for initramfs-tools (0.135) ...
update-initramfs: Generating /boot/initrd.img-5.3.0-3-amd64
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
WARNING: Unknown X keysym "dead_belowmacron"
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file 
'/tmp/user/0/mkinitramfs_wGhhWc/lib/modules/5.3.0-3-amd64/modules.builtin.bin'
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file 
'/tmp/user/0/mkinitramfs_wGhhWc/lib/modules/5.3.0-3-amd64/modules.builtin.bin'

Thanks in advance,
xiscu

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 34M Jan 11 12:14 /boot/initrd.img-5.3.0-3-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.3.0-3-amd64 root=/dev/mapper/r5--vg-root ro panic=5 quiet

-- resume
RESUME=/dev/mapper/r5--vg-swap_1
-- /proc/filesystems
btrfs
ext3
ext2
ext4

-- lsmod
Module  Size  Used by
ctr16384  3
ccm20480  9
bluetooth 659456  0
drbg   28672  1
ansi_cprng 16384  0
ecdh_generic   16384  1 bluetooth
ecc32768  1 ecdh_generic
msr16384  0
iwlmvm327680  0
snd_hda_codec_hdmi 65536  1
mac80211  872448  1 iwlmvm
snd_hda_codec_conexant24576  1
x86_pkg_temp_thermal20480  0
intel_powerclamp   20480  0
snd_hda_codec_generic94208  1 snd_hda_codec_conexant
ledtrig_audio  16384  2 snd_hda_codec_generic,snd_hda_codec_conexant
libarc416384  1 mac80211
binfmt_misc24576  1
kvm_intel 299008  0
i915 1949696  6
mei_wdt16384  0
intel_rapl_msr 20480  0
snd_hda_intel  49152  4
kvm   770048  1 kvm_intel
snd_hda_codec 159744  4 
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel
drm_kms_helper212992  1 i915
iwlwifi   282624  1 iwlmvm
snd_hda_core  102400  5 
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
irqbypass  16384  1 kvm
intel_cstate   16384  0
intel_uncore  147456  0
snd_hwdep  16384  1 snd_hda_codec
asus_nb_wmi28672  0
intel_rapl_perf16384  0
asus_wmi   36864  1 asus_nb_wmi
snd_pcm   118784  4 
snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
evdev  28672  13
cfg80211  831488  3 iwlmvm,iwlwifi,mac80211
joydev 28672  0
pcspkr 16384  0
drm   552960  7 drm_kms_helper,i915
sparse_keymap  16384  1 asus_wmi
snd_timer  40960  1 snd_pcm
serio_raw  20480  0
iTCO_wdt   16384  0
processor_thermal_device20480  0
mei_me 45056  1
iTCO_vendor_support16384  1 iTCO_wdt
snd98304  16 
snd_hda_codec_generic,snd_hda_codec_conexant,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_timer,snd_pcm
intel_rapl_common  28672  2 intel_rapl_msr,processor_thermal_device
rfkill 28672  6 asus_wmi,bluetooth,cfg80211
mei   122880  3 mei_wdt,mei_me
sg 40960  0
i2c_algo_bit   16384  1 i915
soundcore  16384  1 snd
watchdog   28672  2 iTCO_wdt,mei_wdt
intel_soc_dts_iosf 20480  1 processor_thermal_device
intel_pch_thermal  16384  0
acpi_als   20480  0
int3402_thermal16384  0
battery20480  0
int3400_thermal20480  0
int340x_thermal_zone16384  2 int3402_thermal,processor_thermal_device
nft_counter16384  1
kfifo_buf  16384  1 acpi_als
ac 16384  0
asus_wireless  20480  0
industrialio   90112  2 acpi_als,kfifo_buf
dell_smo8800   20480  0
acpi_thermal_rel   16384  1 int3400_thermal
intel_smartconnect 16384  0
button 20480  0
nft_ct 20480  1
nf_conntrack  167936  1 nft_ct
nf_defrag_ipv6 24576  1 nf_conntrack
nf_defrag_ipv4 16384  1 nf_conntrack
nf_tables_set  32768  1
nf_tables 163840  17 nft_ct,nft_counter,nf_tables_set
nfnetlink  16384  1 nf_tables
coretemp   20480  0
ip_tables  32768  0
x_tables   49152  1 ip_tables
autofs453248  3
ext4  757760  2
crc16  16384  2 bluetooth,ext4
mbcache16384  1 ext4
jbd2  131072  1 ext4
crc32c_generic 16384  0
btrfs1486848  0
zstd_decompress90112  1 btrfs
zstd_compress 184320  1 bt

Processed: reassign 948593 to cryptsetup-initramfs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 948593 cryptsetup-initramfs
Bug #948593 [src:linux] Unable to open LUKS device (error allocating crypto 
tfm) for aes / cbc-essiv:sha256 sha1 LUKS header
Bug reassigned from package 'src:linux' to 'cryptsetup-initramfs'.
No longer marked as found in versions linux/5.4.8-1.
Ignoring request to alter fixed versions of bug #948593 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
948593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948593
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#948257: Is there a fix coming down the pike?

[sixerjman]

Can we expect a fix soon in whatever package causes the console spam? It's
a rude awakening to get hit by these messages first thing in the morning
when doing maintenance.

Bug#948041: impossible to update libbpf without updating the kernel

[Sudip Mukherjee]

X-Debbugs-Cc: debian-de...@lists.debian.org

On Fri, Jan 03, 2020 at 08:23:58PM +, Sudip Mukherjee wrote:
> On Fri, Jan 3, 2020 at 7:49 PM Bastian Blank  wrote:
> >
> > Hi Marco
> >
> > On Fri, Jan 03, 2020 at 06:59:36PM +0100, Marco d'Itri wrote:
> > > On Jan 03, Sudip Mukherjee  wrote:
> > > > Do we package libbpf from their github repo independent of the kernel
> > > > update? Then we will need to remove the libbpf building bits from the
> > > > Debian kernel source and create a separate package for libbpf.
> > > This is what some of the upstream libbpf developers requested us to do.
> >
> > What I don't understand is, if the kernel git tree is the primary
> > location for this library, why should we use an external copy?
> >
> > What are the benefits of doing so?
> 
> The only benefit will be that we will be able to update the libraries
> irrespective of kernel update. libbpf v0.0.6 has been released in
> December but we will not be able to move to that version. The
> userspace application using this library is deprived of the benefit of
> the fixes that v0.0.6 brings.

Any thoughts on this please...

I have now done an initial packaging and can open an ITP if everyone
thinks we should move this out of debian kernel packaging.

And, I think I should also point out here that libtraceevent developers
are also moving to a separate repo which will have their final releases
rather then using the kernel repo. I will open a separate bug report for
them after they have decided where they want their new repo. And, libperf
might also follow suit after libtraceevent.

It might be better if we decide now what we want to do and tell them
accordingly.


--
Regards
Sudip