Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open bui  (Read 8057 times)

Offline Carnophage

  • User
  • Posts: 40
    • http://carnophage.wordpress.com
Not sure how severe it is but I encountered https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257 after today's full upgrade.
Code: [Select]
5 packages can be upgraded. Run 'apt list --upgradable' to see them.                                                                                                                                                                                           
Listing... Gotowe                                                                                                                                                                                                                                             
kmod/unstable 26+20191223-1 amd64 [upgradable from: 26-3]                                                                                                                                                                                                     
libcpupower2/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1]                                                                                                                                                                                                 
libkmod2/unstable 26+20191223-1 amd64 [upgradable from: 26-3]                                                                                                                                                                                                 
linux-cpupower/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1]                                                                                                                                                                                               
linux-libc-dev/unstable 5.4.8-1 amd64 [upgradable from: 5.4.6-1]
Code: [Select]
# LANG=C update-initramfs -k 5.4.8-towo.1-siduction-amd64 -u                                                                                                                                                                                     [583/3394]
update-initramfs: Generating /boot/initrd.img-5.4.8-towo.1-siduction-amd64                                                                                                                                                                                     
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin'                                                                           
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin'                                                                           
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/var/tmp/mkinitramfs_mQ4YXU/lib/modules/5.4.8-towo.1-siduction-amd64/modules.builtin.bin(…)


Offline samoht

  • User
  • Posts: 478
Confirmed here!

Quote
...
Control: severity -1 serious

raising the severity in case there can be a real major system breakage
(not tested) and also because of the huge number of errors, which can
hide important information (other errors...).
...

Offline Carnophage

  • User
  • Posts: 40
    • http://carnophage.wordpress.com
It looks like connected with https://lore.kernel.org/linux-modules/CAKi4VA+QrgGNWSKwZx5NFQWtFdF_M=6_V4_LrV7dEhqvncePdw@mail.gmail.com/T/#m777690a71d45cd7c4544edf721cdfb50d3ded8ca

my lack of deeper kernel/C knowledge does not allow me to judge if this error is indeed critical or not (it might be just lack of this additional info about builtin modules)
« Last Edit: 2020/01/06, 11:18:27 by Carnophage »

Offline hendrikL

  • Administrator
  • User
  • *****
  • Gravatar
  • Posts: 929

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257

I recommend to be patient and wait with d-u/full-upgrade till it is fixed!
« Last Edit: 2020/01/06, 12:03:12 by hendrikL »

Offline paxmark2

  • User
  • Posts: 85
I had quite a few error messages yesterday via kmod apt full-upgrade in Deb Sid 386 with wayland i3w.  Will see how it goes.  Time to retire the old atom netbook anyway. 

Offline hendrikL

  • Administrator
  • User
  • *****
  • Gravatar
  • Posts: 929
That "Bug" is not a bug but a bug!?
More an error, it is spitting out a huge ton of an error message that has to be fixed,
so far I understand.



https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948257#105
Quote
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.

« Last Edit: 2020/01/14, 08:53:09 by hendrikL »