Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Same problem on my computer kmod -V kmod version 26 +XZ -ZLIB +LIBCRYPTO -EXPERIMENTAL uname -ar 5.4.0-2-amd64 #1 SMP Debian 5.4.8-1 (2020-01-05) x86_64 GNU/Linux On Mon, 06 Jan 2020 10:02:05 +0530 crvi wrote: > Package: kmod > Version: 26+20191223-1 > Severity: important > > Dear Maintainer, > > * What led up to the situation? > > apt-get dist-upgrade > > * What exactly did you do (or not do) that was effective (or > ineffective)? > > apt-get dist-upgrade > > * What was the outcome of this action? > > Processing triggers for initramfs-tools (0.135) ... > update-initramfs: Generating /boot/initrd.img-5.4.0-1-amd64 > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open > builtin file > '/var/tmp/mkinitramfs_DRc0S1/lib/modules/5.4.0-1-amd64/modules.builtin.bin > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open > builtin file > '/var/tmp/mkinitramfs_DRc0S1/lib/modules/5.4.0-1-amd64/modules.builtin.bin > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open > builtin file > '/var/tmp/mkinitramfs_DRc0S1/lib/modules/5.4.0-1-amd64/modules.builtin.bin > > * What outcome did you expect instead? > > Successful ramfs generation > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable-debug > APT policy: (500, 'unstable-debug'), (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-1-amd64 (SMP w/1 CPU core) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages kmod depends on: > ii libc6 2.29-8 > ii libkmod2 26+20191223-1 > ii liblzma5 5.2.4-1+b1 > ii libssl1.1 1.1.1d-2 > ii lsb-base 11.1.0 > > kmod recommends no packages. > > kmod suggests no packages. > > -- no debconf information
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Package: initramfs-tools Version: 0.135 Followup-For: Bug #948257 Just want to confirm Pierrick's observation that rolling back kmod and libkmod2 to version 26-3 fixes the logspam.
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Bjørn Mork writes:
> Marco d'Itri writes:
>
>> Control: severity -1 normal
>> Control: tags -1 patch
>> Control: reassign -1 initramfs-tools
>>
>> On Jan 06, crvi wrote:
>>
>>>* What outcome did you expect instead?
>>>
>>> Successful ramfs generation
>> Do you have any reason to believe that the initrfamfs was not generated
>> successfully?
>>
>> This is only cosmetic, and it needs to be fixed in /usr/sbin/mkinitramfs
>> by copying modules.builtin.bin too:
>>
>> -for x in modules.builtin modules.order; do
>> +for x in modules.builtin modules.builtin.bin modules.order; do
>
> modules.builtin.bin is created, and always regenerated, by depmod based
> on modules.builtin. Requiring modules.builtin.bin to exist before
> running depmod makes no sense at all.
>
> So what change made depmod spit out this pointless warning? You should
> fix that bug instead insisting that some other package paper over it.
FYI: the bug is Debian-specific and introduced long ago with this patch:
bjorn@miraculix:/tmp/kmod-26+20191223$ cat debian/patches/verbose_missing_bin
Description: Report an error when some .bin files do not exist
Author: Marco d'Itri
Bug-Debian: http://bugs.debian.org/684901
---
--- a/libkmod/libkmod.c
+++ b/libkmod/libkmod.c
@@ -503,7 +503,7 @@ static char *lookup_builtin_file(struct
idx = index_file_open(fn);
if (idx == NULL) {
- DBG(ctx, "could not open builtin file '%s'\n", fn);
+ ERR(ctx, "could not open builtin file '%s'\n", fn);
return NULL;
}
@@ -575,7 +575,7 @@ char *kmod_search_moddep(struct kmod_ctx
idx = index_file_open(fn);
if (idx == NULL) {
- DBG(ctx, "could not open moddep file '%s'\n", fn);
+ ERR(ctx, "could not open moddep file '%s'\n", fn);
return NULL;
}
Non-existing files is expected for libkmod in some situations, like the
current example when depmod is looking up a module while generating
dependencies for it.
Bjørn
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Hi Benjamin,
On Wed, Jan 08, 2020 at 01:07:20PM +0100, Salvatore Bonaccorso wrote:
> Hi Benjamin,
>
> On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
> [...]
> > Looks like the modules are built before lttng-sessiond is started:
> > Setting up lttng-modules-dkms (2.11.0-2) ...
> > Loading new lttng-modules-2.11.0 DKMS files...
> > Building for 5.4.0-2-amd64
> > Building initial module for 5.4.0-2-amd64
> > Done.
> >
> > lttng-lib-ring-buffer.ko:
> > Running module version sanity check.
> > - Original module
> >- No original module exists within this kernel
> > - Installation
> >- Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
> >
> > [...]
> >
> > depmod...
> >
> > DKMS: install completed.
> > Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> > /etc/kernel/header_postinst.d/dkms:
> > dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> > Setting up sudo (1.8.29-1) ...
> > Setting up babeltrace (1.5.7-2) ...
> > Setting up liburcu6:amd64 (0.11.1-2) ...
> > Setting up linux-headers-amd64 (5.4.8-1) ...
> > Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> > Setting up lttng-tools (2.11.0-3) ...
> >
> > Still, it doesn't work.
> >
> > > Simply restarting the sessiond should fix this.
> >
> > I tried restarting lttng-sessiond or rebooting the machine but it was no
> > help, lttng-sessiond always reports:
> > Error: Failed to load kmod library resources
> > Warning: No kernel tracer available
> >
> > A quick look into the code shows that is:
> > src/bin/lttng-sessiond/modprobe.c
> > kmod_set_log_fn(*ctx, log_kmod, NULL);
> > ret = kmod_load_resources(*ctx);
> > if (ret < 0) {
> > ERR("Failed to load kmod library resources");
> > goto error;
> > }
> >
> > I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> > following:
> > 8071 lttng-sessiond 2 0
> > /lib/modules/5.4.0-2-amd64/modules.dep.bin
> > 8071 lttng-sessiond 2 0
> > /lib/modules/5.4.0-2-amd64/modules.alias.bin
> > 8071 lttng-sessiond 2 0
> > /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> > 8071 lttng-sessiond 2 0
> > /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
> >
> > On another machine which I haven't yet updated and where lttng still
> > works, I see:
> > 193519 lttng-sessiond 2 0
> > /lib/modules/5.4.0-1-amd64/modules.dep.bin
> > 193519 lttng-sessiond 2 0
> > /lib/modules/5.4.0-1-amd64/modules.alias.bin
> > 193519 lttng-sessiond 2 0
> > /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> > 193519 lttng-sessiond 2 0
> > /lib/modules/5.4.0-1-amd64/modules.builtin.bin
> >
> > Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> > relevant but it's an empty file...
> >
> > After downgrading libkmod2 from
> > Version: 26+20191223-1
> > to
> > Version: 26-3
> > the issue with lttng is no longer apparent:
> > root@vsid:/tmp# lttng list --kernel
> > Kernel events:
> > -
> > asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> > asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> > asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type:
> > tracepoint)
> > [...]
> >
>
> Should we track this in a separate bug from #948257?
So here is what I think is part of what is going on (unless there is
something broken in my analysis):
Since 898490c010b5 ("moduleparam: Save information about built-in
modules in separate file")[1] which is in 5.2-rc1, there is a new
modules.builtin.modinfo provided.
[1]:
This one is installed in the -unsigned binary packages but not copied
over into the signing template, so the signed linux image packages do
not contain it.
Now with kmod/26+20191223-1 we have 60084cf1cb24 ("libkmod: Add parser
for modules.builtin.modinfo")[2] adding the parser and [3] and [4]
using that.
[2]:
[3]:
[4]:
Salvatore
Re: Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Marco d'Itri writes: > Control: severity -1 normal > Control: tags -1 patch > Control: reassign -1 initramfs-tools > > On Jan 06, crvi wrote: > >>* What outcome did you expect instead? >> >> Successful ramfs generation > Do you have any reason to believe that the initrfamfs was not generated > successfully? > > This is only cosmetic, and it needs to be fixed in /usr/sbin/mkinitramfs > by copying modules.builtin.bin too: > > -for x in modules.builtin modules.order; do > +for x in modules.builtin modules.builtin.bin modules.order; do modules.builtin.bin is created, and always regenerated, by depmod based on modules.builtin. Requiring modules.builtin.bin to exist before running depmod makes no sense at all. So what change made depmod spit out this pointless warning? You should fix that bug instead insisting that some other package paper over it. Bjørn
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Hi Benjamin,
On Wed, Jan 08, 2020 at 09:24:30AM +0900, Benjamin Poirier wrote:
[...]
> Looks like the modules are built before lttng-sessiond is started:
> Setting up lttng-modules-dkms (2.11.0-2) ...
> Loading new lttng-modules-2.11.0 DKMS files...
> Building for 5.4.0-2-amd64
> Building initial module for 5.4.0-2-amd64
> Done.
>
> lttng-lib-ring-buffer.ko:
> Running module version sanity check.
>- Original module
> - No original module exists within this kernel
>- Installation
> - Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
>
> [...]
>
> depmod...
>
> DKMS: install completed.
> Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
> /etc/kernel/header_postinst.d/dkms:
> dkms: running auto installation service for kernel 5.4.0-2-amd64:.
> Setting up sudo (1.8.29-1) ...
> Setting up babeltrace (1.5.7-2) ...
> Setting up liburcu6:amd64 (0.11.1-2) ...
> Setting up linux-headers-amd64 (5.4.8-1) ...
> Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
> Setting up lttng-tools (2.11.0-3) ...
>
> Still, it doesn't work.
>
> > Simply restarting the sessiond should fix this.
>
> I tried restarting lttng-sessiond or rebooting the machine but it was no
> help, lttng-sessiond always reports:
> Error: Failed to load kmod library resources
> Warning: No kernel tracer available
>
> A quick look into the code shows that is:
> src/bin/lttng-sessiond/modprobe.c
> kmod_set_log_fn(*ctx, log_kmod, NULL);
> ret = kmod_load_resources(*ctx);
> if (ret < 0) {
> ERR("Failed to load kmod library resources");
> goto error;
> }
>
> I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
> following:
> 8071 lttng-sessiond 2 0
> /lib/modules/5.4.0-2-amd64/modules.dep.bin
> 8071 lttng-sessiond 2 0
> /lib/modules/5.4.0-2-amd64/modules.alias.bin
> 8071 lttng-sessiond 2 0
> /lib/modules/5.4.0-2-amd64/modules.symbols.bin
> 8071 lttng-sessiond 2 0
> /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
>
> On another machine which I haven't yet updated and where lttng still
> works, I see:
> 193519 lttng-sessiond 2 0
> /lib/modules/5.4.0-1-amd64/modules.dep.bin
> 193519 lttng-sessiond 2 0
> /lib/modules/5.4.0-1-amd64/modules.alias.bin
> 193519 lttng-sessiond 2 0
> /lib/modules/5.4.0-1-amd64/modules.symbols.bin
> 193519 lttng-sessiond 2 0
> /lib/modules/5.4.0-1-amd64/modules.builtin.bin
>
> Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
> relevant but it's an empty file...
>
> After downgrading libkmod2 from
> Version: 26+20191223-1
> to
> Version: 26-3
> the issue with lttng is no longer apparent:
> root@vsid:/tmp# lttng list --kernel
> Kernel events:
> -
> asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type:
> tracepoint)
> asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type:
> tracepoint)
> asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type:
> tracepoint)
> [...]
>
Should we track this in a separate bug from #948257?
Regards,
Salvatore
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
On 2020/01/07 10:12, Michael Jeanson wrote:
> On 2020-01-06 7:46 p.m., Benjamin Poirier wrote:
> > I'm not sure if it's related but I saw almost the same error on last
> > upgrade (but for 5.4.0-2):
> >
> > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not
> > open builtin file
> > '/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin'
> >
> > and I now get:
> >
> > root@vsid:~# lttng list --kernel
> > Error: Unable to list kernel events: Kernel tracer not available
> > root@vsid:~# journalctl -u lttng-sessiond.service
> > [...]
> > Jan 07 09:33:20 vsid lttng-sessiond[403]: Error: Failed to load kmod
> > library resources
> > Jan 07 09:33:20 vsid lttng-sessiond[403]: Warning: No kernel tracer
> > available
> >
> > lttng-modules-dkms is installed. I can load the modules manually but I
> > still get the same error.
> >
>
> Hi,
>
> If you had just installed the lttng-modules-dkms and lttng-tools packages,
> it's possible that the lttng-sessiond deamon was started before the kernel
> modules were built and so it couldn't load them.
Looks like the modules are built before lttng-sessiond is started:
Setting up lttng-modules-dkms (2.11.0-2) ...
Loading new lttng-modules-2.11.0 DKMS files...
Building for 5.4.0-2-amd64
Building initial module for 5.4.0-2-amd64
Done.
lttng-lib-ring-buffer.ko:
Running module version sanity check.
- Original module
- No original module exists within this kernel
- Installation
- Installing to /lib/modules/5.4.0-2-amd64/updates/dkms/
[...]
depmod...
DKMS: install completed.
Setting up linux-headers-5.4.0-2-amd64 (5.4.8-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 5.4.0-2-amd64:.
Setting up sudo (1.8.29-1) ...
Setting up babeltrace (1.5.7-2) ...
Setting up liburcu6:amd64 (0.11.1-2) ...
Setting up linux-headers-amd64 (5.4.8-1) ...
Setting up liblttng-ctl0:amd64 (2.11.0-3) ...
Setting up lttng-tools (2.11.0-3) ...
Still, it doesn't work.
> Simply restarting the sessiond should fix this.
I tried restarting lttng-sessiond or rebooting the machine but it was no
help, lttng-sessiond always reports:
Error: Failed to load kmod library resources
Warning: No kernel tracer available
A quick look into the code shows that is:
src/bin/lttng-sessiond/modprobe.c
kmod_set_log_fn(*ctx, log_kmod, NULL);
ret = kmod_load_resources(*ctx);
if (ret < 0) {
ERR("Failed to load kmod library resources");
goto error;
}
I didn't dig into libkmod, but I noticed (using opensnoop.bt) the
following:
8071 lttng-sessiond 2 0
/lib/modules/5.4.0-2-amd64/modules.dep.bin
8071 lttng-sessiond 2 0
/lib/modules/5.4.0-2-amd64/modules.alias.bin
8071 lttng-sessiond 2 0
/lib/modules/5.4.0-2-amd64/modules.symbols.bin
8071 lttng-sessiond 2 0
/lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin
On another machine which I haven't yet updated and where lttng still
works, I see:
193519 lttng-sessiond 2 0
/lib/modules/5.4.0-1-amd64/modules.dep.bin
193519 lttng-sessiond 2 0
/lib/modules/5.4.0-1-amd64/modules.alias.bin
193519 lttng-sessiond 2 0
/lib/modules/5.4.0-1-amd64/modules.symbols.bin
193519 lttng-sessiond 2 0
/lib/modules/5.4.0-1-amd64/modules.builtin.bin
Not sure if /lib/modules/5.4.0-2-amd64/modules.builtin.alias.bin is
relevant but it's an empty file...
After downgrading libkmod2 from
Version: 26+20191223-1
to
Version: 26-3
the issue with lttng is no longer apparent:
root@vsid:/tmp# lttng list --kernel
Kernel events:
-
asoc_snd_soc_bias_level_start (loglevel: TRACE_EMERG (0)) (type:
tracepoint)
asoc_snd_soc_bias_level_done (loglevel: TRACE_EMERG (0)) (type:
tracepoint)
asoc_snd_soc_dapm_start (loglevel: TRACE_EMERG (0)) (type:
tracepoint)
[...]
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
On 2020-01-06 7:46 p.m., Benjamin Poirier wrote: > I'm not sure if it's related but I saw almost the same error on last > upgrade (but for 5.4.0-2): > > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open > builtin file > '/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin' > > and I now get: > > root@vsid:~# lttng list --kernel > Error: Unable to list kernel events: Kernel tracer not available > root@vsid:~# journalctl -u lttng-sessiond.service > [...] > Jan 07 09:33:20 vsid lttng-sessiond[403]: Error: Failed to load kmod library > resources > Jan 07 09:33:20 vsid lttng-sessiond[403]: Warning: No kernel tracer available > > lttng-modules-dkms is installed. I can load the modules manually but I > still get the same error. > Hi, If you had just installed the lttng-modules-dkms and lttng-tools packages, it's possible that the lttng-sessiond deamon was started before the kernel modules were built and so it couldn't load them. Simply restarting the sessiond should fix this. Cheers, Michael
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
On Mon, 6 Jan 2020 at 20:58, Marco d'Itri wrote: > >* What outcome did you expect instead? > > > > Successful ramfs generation > Do you have any reason to believe that the initrfamfs was not generated > successfully? > No. I just meant successful command completion. A reboot worked fine. So, no serious issues.
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
I'm not sure if it's related but I saw almost the same error on last upgrade (but for 5.4.0-2): depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_J2sneW/lib/modules/5.4.0-2-amd64/modules.builtin.bin' and I now get: root@vsid:~# lttng list --kernel Error: Unable to list kernel events: Kernel tracer not available root@vsid:~# journalctl -u lttng-sessiond.service [...] Jan 07 09:33:20 vsid lttng-sessiond[403]: Error: Failed to load kmod library resources Jan 07 09:33:20 vsid lttng-sessiond[403]: Warning: No kernel tracer available lttng-modules-dkms is installed. I can load the modules manually but I still get the same error.
Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Merge request at https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/23 with Marco's patch. Regards, Salvatore
Re: Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Control: severity -1 normal Control: tags -1 patch Control: reassign -1 initramfs-tools On Jan 06, crvi wrote: >* What outcome did you expect instead? > > Successful ramfs generation Do you have any reason to believe that the initrfamfs was not generated successfully? This is only cosmetic, and it needs to be fixed in /usr/sbin/mkinitramfs by copying modules.builtin.bin too: -for x in modules.builtin modules.order; do +for x in modules.builtin modules.builtin.bin modules.order; do -- ciao, Marco signature.asc Description: PGP signature
Processed: Re: Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Processing control commands: > severity -1 normal Bug #948257 [kmod] depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Severity set to 'normal' from 'serious' > tags -1 patch Bug #948257 [kmod] depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Added tag(s) patch. > reassign -1 initramfs-tools Bug #948257 [kmod] depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Bug reassigned from package 'kmod' to 'initramfs-tools'. No longer marked as found in versions kmod/26+20191223-1. Ignoring request to alter fixed versions of bug #948257 to the same values previously set -- 948257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
