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
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.
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
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)
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
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
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
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
>
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.
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:~#
Merge request at
https://salsa.debian.org/kernel-team/initramfs-tools/merge_requests/23
with Marco's patch.
Regards,
Salvatore
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
Observing similar issues after kmod upgrade from version 26-3 to
26+20191223-1.
initramfs is built, despite of errors reported and all systems affected
are bootable without problems for me.
Temporary file claimed as missing
(/var/tmp/mkinitramfs_iC46xD/lib/modules/5.4.8/modules.builtin.bin ) is
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...).
[...]
Setting up kmod (26+20191223-1) ...
update-initramfs: deferring update
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
15 matches
Mail list logo
