Bug#922478: upgrade linux-image-4.9.0-8-armmp-lpae:armhf from 4.9.130-2 to 4.9.144-3 renders Bananapi and Lamobo R1 unbootable
Hi,
Cyril Brulebois schrieb am 17.02.2019 19:38:
> Hi folks,
>
> Jürgen Löb <j.loeb@loeb-it.de> (2019-02-16):
>> Package: linux-image-4.9.0-8-armmp-lpae
>> Version: 4.9.144-3
>> Severity: serious
>>
>> Updated my Lamobo R1 board with apt update;apt upgrade
>>
>> After the update uboot is struck at "Starting kernel". There is no
>> further output after "Starting kernel". Same happens on Bananapi 1
>> board. Unfortunately there is no more useful information.
> […]
>
> Summing up, it looks like everybody in cc is confirming the regression
> happens between 4.9.130-2 and 4.9.144-3, with and without lpae, on
> various boards. Any chance you could check what happens with the
> 4.9.135-1 intermediary version that can be found on snapshot.debian.org?
>
> https://snapshot.debian.org/package/linux/4.9.135-1/
>
> This might help narrow it down when the regression happened.
>
> (And please use reply-all so that everyone is kept in the loop.)
So, I also tested 4.9.135-1 on a Bananapi board and can confirm it works.
I would suspect the issue is caused by Debian's kernel configuration or changes. The Kernel CI project has ARM hardware, including the Bananapi board and does tests of stable kernel updates to verify that the kernel boots. At least with multi_v7_defconfig and sunxi_defconfig, upstream 4.9.144 does boot on Allwinner-based hardware, see: https://kernelci.org/soc/allwinner/job/stable-rc/kernel/v4.9.144/
On a sidenote: This issue makes me wonder if Debian's approach to kernel updates (i.e. not bumping the version number/ABI and overwriting the kernel image and modules) is really the best option. IMHO Ubuntu's handling of kernel updates is more robust. It would have made things much easier today if I could have simply selected an older kernel in the bootloader, rather than having to recover one from a backup.
Kind regards,
Timo
Reply to: