RISC-V kernel config is out of sync with other archs
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux (Ubuntu) |
Fix Released
|
Undecided
|
Emil Renner Berthing | ||
Bug Description
[Impact]
* Some drivers are available on other architectures but not on RISC-V.
* Some things might work or look differently in RISC-V.
Eg. RISC-V has an additional terminal font enabled.
* The RISC-V kernel benefits less from testing done on other
architectures.
[Test Plan]
* Install the kernel on RISC-V and see what modules and features are
enabled.
* After aligning the RISC-V kernel config there should be fewer
differences to other architectures.
[Where problems could occur]
* Some options that are disabled on other architectures may be needed
on RISC-V.
* Some modules or features may be broken on RISC-V.
[Other Info]
* When RISC-V config and annotations were added to the generic kernel
the config was copied from the linux-riscv tree without modifications.
This revealed a lot of differences to the other architectures and many
of them were not annotated, so presumably the configs had just drifted
apart over time.
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote Missing required logs. | #1 |
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| Changed in linux (Ubuntu): | |
| status: | Incomplete → In Progress |
| assignee: | nobody → Emil Renner Berthing (esmil) |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in linux (Ubuntu): | |
| status: | In Progress → Fix Released |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote | #3 |
| tags: | added: kernel-spammed-jammy-linux-azure-6.5-v2 verification-needed-jammy-linux-azure-6.5 |
| Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote | #4 |
| tags: | added: kernel-spammed-jammy-linux-aws-6.5-v2 verification-needed-jammy-linux-aws-6.5 |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1981437
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.