[SRU] Jammy RISC-V nezha and licheerv (allwinner kernel) images failing to build

Bug #2054304 reported by Łukasz Zemczak
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
flash-kernel (Ubuntu)
Invalid
Critical
Unassigned
Jammy
Fix Released
Critical
Dave Jones

Bug Description

[ 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.

Changed in flash-kernel (Ubuntu):
status: New → Invalid
Changed in flash-kernel (Ubuntu Jammy):
status: New → In Progress
importance: Undecided → Critical
assignee: nobody → Dave Jones (waveform)
milestone: none → ubuntu-22.04.4
Revision history for this message
Dave Jones (waveform) wrote :
description: updated
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
Revision history for this message
Dave Jones (waveform) wrote :
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Łukasz, or anyone else affected,

Accepted flash-kernel into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/flash-kernel/3.104ubuntu19 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in flash-kernel (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Heinrich Schuchardt (xypron) wrote :

We don't provide images for "Sipeed Lichee RV". There are only two boards to tests:

* Nezha D1
* Sipeed Lichee RV Dock

Revision history for this message
Heinrich Schuchardt (xypron) wrote (last edit ):

On the Lichee RV Dock flash-kernel_3.104ubuntu19_riscv64 works fine with Linux 5.19.0-1015-allwinner.

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

On the HiFive SiFive Unmatched flash-kernel_3.104ubuntu19_riscv64 works fine with Linux 6.5.0-17-generic #17.1.1~22.04.1-Ubuntu.

Revision history for this message
Heinrich Schuchardt (xypron) wrote :

On the Allwinner Nezha D1 flash-kernel_3.104ubuntu19_riscv64 works fine with Linux 5.19.0-1015-allwinner.

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Łukasz Zemczak (sil2100) wrote :

Thank you for all the testing! I'll be releasing this early as it's a critical issue for .4.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package flash-kernel - 3.104ubuntu19

---------------
flash-kernel (3.104ubuntu19) jammy; urgency=medium

  * Use "any" kernel flavor for allwinner-based RISC-V boards, as the new
    kernel is a "-generic" flavor (LP: #2054304)

 -- Dave Jones <email address hidden> Mon, 19 Feb 2024 11:02:55 +0000

Changed in flash-kernel (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for flash-kernel has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.