| 2024-02-19 11:22:18 |
Łukasz Zemczak |
bug |
|
|
added bug |
| 2024-02-19 11:22:24 |
Łukasz Zemczak |
nominated for series |
|
Ubuntu Jammy |
|
| 2024-02-19 11:22:24 |
Łukasz Zemczak |
bug task added |
|
flash-kernel (Ubuntu Jammy) |
|
| 2024-02-19 11:22:29 |
Łukasz Zemczak |
flash-kernel (Ubuntu): status |
New |
Invalid |
|
| 2024-02-19 11:22:31 |
Łukasz Zemczak |
flash-kernel (Ubuntu Jammy): status |
New |
In Progress |
|
| 2024-02-19 11:22:33 |
Łukasz Zemczak |
flash-kernel (Ubuntu Jammy): importance |
Undecided |
Critical |
|
| 2024-02-19 11:22:40 |
Łukasz Zemczak |
flash-kernel (Ubuntu Jammy): assignee |
|
Dave Jones (waveform) |
|
| 2024-02-19 11:22:44 |
Łukasz Zemczak |
flash-kernel (Ubuntu Jammy): milestone |
|
ubuntu-22.04.4 |
|
| 2024-02-19 11:26:46 |
Dave Jones |
description |
Since the beginning of the year, all jammy -allwinner kernel based images are failing to build, aka. the nezha and licheerv subarch ones. It looks like the problem is with the new allwinner kernel, now needing some changes to flash-kernel to properly handle it during DTB preparation. |
[ Impact ]
The new allwinner kernel in jammy (20.04) no longer has the "-allwinner" flavour suffix, but "-generic". This results in flash-kernel failing to match the kernel when running (and f-k failing to run causes apt upgrade to fail). The "Kernel-Flavor:" field for all boards which are currently limited to "allwinner riscv64" should be changed to "any"; this matches the state in noble.
[ Test Plan ]
There are three entries in the f-k database which are affected:
* Allwinner D1 Nezha
* Sipeed Lichee RV
* Sipeed Lichee RV Dock
Ideally, a jammy image should be tested on each of these three boards as follows:
* Install jammy image
* Enable proposed (https://wiki.ubuntu.com/Testing/EnableProposed)
* sudo apt install -t jammy-proposed flash-kernel
* sudo apt update; sudo apt full-upgrade
* Upgrade should run successfully without apt dying during flash-kernel
* Verify freshly installed kernel is from the 6.5 series and is "-generic" flavour
* sudo reboot
* Check system reboots and is operational afterward
[ Regression Potential ]
Database changes in flash-kernel should only affect the listed boards, and the move to "any" makes the entry less restrictive which is generally a "safer" change. However if, for any reason, one of these boards has an unsupported kernel flavour with a later version installed, that will cause a regression as flash-kernel will now select that kernel for installation. This shouldn't be the case in any supported configuration, but is a possibility to be aware of.
[ Original Description ]
Since the beginning of the year, all jammy -allwinner kernel based images are failing to build, aka. the nezha and licheerv subarch ones. It looks like the problem is with the new allwinner kernel, now needing some changes to flash-kernel to properly handle it during DTB preparation. |
|
| 2024-02-19 11:26:52 |
Dave Jones |
summary |
Jammy RISC-V nezha and licheerv (allwinner kernel) images failing to build |
[SRU] Jammy RISC-V nezha and licheerv (allwinner kernel) images failing to build |
|
| 2024-02-19 11:29:04 |
Dave Jones |
attachment added |
|
1-2054304.debdiff https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2054304/+attachment/5747267/+files/1-2054304.debdiff |
|
| 2024-02-19 12:17:17 |
Łukasz Zemczak |
flash-kernel (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2024-02-19 12:17:18 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2024-02-19 12:17:20 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2024-02-19 12:17:23 |
Łukasz Zemczak |
tags |
|
verification-needed verification-needed-jammy |
|
| 2024-02-19 17:13:01 |
Heinrich Schuchardt |
tags |
verification-needed verification-needed-jammy |
verification-done verification-done-jammy |
|
| 2024-02-19 18:18:57 |
Launchpad Janitor |
flash-kernel (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2024-02-19 18:19:00 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
