[Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Matthias Klose]

reopening for focal. still seen in almost every autopkg test
(2020-03-24)

** Changed in: kmod (Ubuntu Focal)
       Status: Fix Released => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  New
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  New

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
       |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware                            1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1864992/+subscriptions