[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#849532: flash-kernel does not remove dtb backups



On 2017-01-02, Martin Michlmayr wrote:
> * Heinrich Schuchardt <xypron.glpk@gmx.de> [2016-12-28 10:10]:
>> The .bak file should not be created on the first install of a Linux kernel.
>
> Yeah, that's a separate issue but it's definitely something I noticed
> too.  The DTB handling code is run several times under some
> circumstances, see e.g. the log below.

For one thing, flash-kernel has hooks in both the kernel and
initramfs-tools directories:

  $ dpkg -L flash-kernel | grep -E 'post' | grep flash-kernel
  /etc/initramfs/post-update.d/flash-kernel
  /etc/kernel/postinst.d/zz-flash-kernel
  /etc/kernel/postrm.d/zz-flash-kernel

So, at the very least, on a new kernel install, it's likely to be called
at least twice.


> I'm afraid to touch that code and hope Ian will look into it at some
> point.
>
> ...
> Taking backup of tegra210-p2371-2180.dtb.
> Installing new tegra210-p2371-2180.dtb.
> flash-kernel: deferring update (trigger activated)
> /etc/kernel/postinst.d/zz-flash-kernel:
> DTB: tegra210-p2371-2180.dtb
> Installing /usr/lib/linux-image-4.9.0-trunk-arm64/nvidia/tegra210-p2371-2180.dtb into /boot/dtbs/4.9.0-trunk-arm64/tegra210-p2371-2180.dtb
> Taking backup of tegra210-p2371-2180.dtb.
> Installing new tegra210-p2371-2180.dtb.
> Installing /usr/lib/linux-image-4.9.0-trunk-arm64/nvidia/tegra210-p2371-2180.dtb into /boot/dtbs/4.9.0-trunk-arm64/tegra210-p2371-2180.dtb
> Taking backup of tegra210-p2371-2180.dtb.
> Installing new tegra210-p2371-2180.dtb.
> flash-kernel: deferring update (trigger activated)
> Processing triggers for flash-kernel (3.73) ...
> DTB: tegra210-p2371-2180.dtb
> Installing /usr/lib/linux-image-4.9.0-trunk-arm64/nvidia/tegra210-p2371-2180.dtb into /boot/dtbs/4.9.0-trunk-arm64/tegra210-p2371-2180.dtb
> Taking backup of tegra210-p2371-2180.dtb.
> Installing new tegra210-p2371-2180.dtb.
> flash-kernel: installing version 4.9.0-trunk-arm64
> Generating boot script u-boot image... done.
> Taking backup of boot.scr.
> Installing new boot.scr.

But this is obviously more than just that... and I've seen it too. *sigh*


live well,
  vagrant

Attachment: signature.asc
Description: PGP signature


Reply to: