Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #66036 > unrolled thread

Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Started bydebian <d3bianl1nuks@gmail.com>
First post2020-01-08 23:00 +0100
Last post2020-01-13 13:30 +0100
Articles 6 — 6 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' debian <d3bianl1nuks@gmail.com> - 2020-01-08 23:00 +0100
    Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Ben Hutchings <ben@decadent.org.uk> - 2020-01-09 00:10 +0100
      Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Jörg-Volker Peetz <jvpeetz@web.de> - 2020-01-10 13:00 +0100
      Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Ilkka Prusi <ilkka.prusi@gmail.com> - 2020-01-12 23:10 +0100
        Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Pierrick CHANTEUX <chanteux@ipgp.fr> - 2020-01-13 11:20 +0100
          Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin' Bjørn Mork <bjorn@mork.no> - 2020-01-13 13:30 +0100

#66036 — Bug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'

Fromdebian <d3bianl1nuks@gmail.com>
Date2020-01-08 23:00 +0100
SubjectBug#948257: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_XXXXXXX/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Message-ID<zmrwR-4gX-15@gated-at.bofh.it>
so, what's to be done now? Marco d'Itri says that this error is 
pointless, Bjørn says that this is normal and this behaviour is expected 
sometimes (kmod looking for nonexistent stuff)

is it just a harmless error "spam"? update the system as usual and just 
ignore the error "waterfall" in the console? use the patch (the edited 
line in /usr/sbin/mkinitramfs) and then update?

[toc] | [next] | [standalone]


#66037

FromBen Hutchings <ben@decadent.org.uk>
Date2020-01-09 00:10 +0100
Message-ID<zmsCB-5aj-1@gated-at.bofh.it>
In reply to#66036

[Multipart message — attachments visible in raw view] — view raw

On Wed, 2020-01-08 at 16:48 -0500, debian wrote:
> so, what's to be done now? Marco d'Itri says that this error is 
> pointless, Bjørn says that this is normal and this behaviour is expected 
> sometimes (kmod looking for nonexistent stuff)
> 
> is it just a harmless error "spam"? update the system as usual and just 
> ignore the error "waterfall" in the console? use the patch (the edited 
> line in /usr/sbin/mkinitramfs) and then update?

Printing spurious error messages is a bug, and we will fix it (whether
in kmod or in initramfs-tools, is to be decided).

But since (so far as I know) there hasn't been any regression in the
functioning of the resulting initramfs, the bug doesn't need to be
fixed right this instant.

Ben.

-- 
Ben Hutchings
Anthony's Law of Force: Don't force it, get a larger hammer.


[toc] | [prev] | [next] | [standalone]


#66051

FromJörg-Volker Peetz <jvpeetz@web.de>
Date2020-01-10 13:00 +0100
Message-ID<zn17k-Ll-3@gated-at.bofh.it>
In reply to#66037
These error messages also appear in the 'make modules_install' step when
building a standard Linux kernel.

Regards,
Jörg.

[toc] | [prev] | [next] | [standalone]


#66064

FromIlkka Prusi <ilkka.prusi@gmail.com>
Date2020-01-12 23:10 +0100
Message-ID<znTAK-b4-5@gated-at.bofh.it>
In reply to#66037
On Wed, 08 Jan 2020 23:07:22 +0000 Ben Hutchings <ben@decadent.org.uk> 
wrote:
> On Wed, 2020-01-08 at 16:48 -0500, debian wrote:
> Printing spurious error messages is a bug, and we will fix it (whether
> in kmod or in initramfs-tools, is to be decided).
> 

So the change causing it should be reverted until it has been decided 
and fixed.

--
  - Ilkka

[toc] | [prev] | [next] | [standalone]


#66066

FromPierrick CHANTEUX <chanteux@ipgp.fr>
Date2020-01-13 11:20 +0100
Message-ID<zo4Zb-7Ou-3@gated-at.bofh.it>
In reply to#66064
Hello,

This bug resulted in complete system breakage and I couldn't boot
anymore (systemd failing to load Kernel modules). I can guarantee that
this isn't only cosmetic.

I believe this isn't related to initramfs-tools, because downgrading
kmod and libkmod2 from version 26+20191223-1 to version 26-3 fixes the
issue. Initramfs now build (and run) correctly.

Regards,
-- 
Pierrick CHANTEUX

[toc] | [prev] | [next] | [standalone]


#66067

FromBjørn Mork <bjorn@mork.no>
Date2020-01-13 13:30 +0100
Message-ID<zo710-y4-5@gated-at.bofh.it>
In reply to#66066
Pierrick CHANTEUX <chanteux@ipgp.fr> writes:

> This bug resulted in complete system breakage and I couldn't boot
> anymore (systemd failing to load Kernel modules). I can guarantee that
> this isn't only cosmetic.
>
> I believe this isn't related to initramfs-tools, because downgrading
> kmod and libkmod2 from version 26+20191223-1 to version 26-3 fixes the
> issue. Initramfs now build (and run) correctly.

IMHO this is probably an unrelated bug in the same kmod upgrade.  You
should report it as such, which the full log output and a subject
decribing the issue instead of the bogus error message.

The logspam caused by the lookup_builtin_file() bug makes it hard to
spot real errors, but hopefully there is some clue to your problem there
too.



Bjørn

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web