| 2020-06-01 17:49:25 |
Adam Bell |
bug |
|
|
added bug |
| 2020-06-01 17:59:50 |
Launchpad Janitor |
linux-raspi2 (Ubuntu): status |
New |
Confirmed |
|
| 2020-06-01 20:05:03 |
Brent DeGraaf |
bug |
|
|
added subscriber Brent DeGraaf |
| 2020-06-01 20:42:01 |
John Agosta |
bug |
|
|
added subscriber John Agosta |
| 2020-06-02 13:55:29 |
Oliver Grawert |
linux-raspi2 (Ubuntu): importance |
Undecided |
Critical |
|
| 2020-06-02 16:57:21 |
Brent DeGraaf |
attachment added |
|
image.png https://bugs.launchpad.net/bugs/1881631/+attachment/5379838/+files/image.png |
|
| 2020-06-02 17:19:20 |
Brent DeGraaf |
attachment removed |
image.png https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1881631/+attachment/5379838/+files/image.png |
|
|
| 2020-06-03 03:57:28 |
Hui Wang |
description |
Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options.
This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing.
Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error.
The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. |
The CONFIG_NLS_ASCII was already set to Y in the raspi-5.4 kernel
and bionic kernel by Juerg, now do the same change in the
raspi2-5.3 kernel.
[Impact]
users reported that the raspi ubuntu core has some problem to mount
filessytem, need to enable the NLS_ASCII and make it built-in.
[Fix]
change it from m to y just as the focal and bionic raspi kernel.
[Test Case]
building the kernel and boot the kernel, it could mount the
filesystem successfully.
[Regression Risk]
Low, just changing a kconfig to y from m.
Remounting log mounts in Ubuntu core are failing on arm64 builds due to missing CONFIG_NLS_ASCII in the arm64 kernel build options.
This option is enabled on the other kernel builds but somehow was overlooked on arm64 appears to affect our ability to access logs via journalctl with data from prior to restart because certain mounts are failing.
Other Raspberry Pi kernel builds, such as the armhf build, have the option enabled and so do not encounter the mount error.
The kernel option that needs to be turned on to resolve this is CONFIG_NLS_ASCII. It needs to be set to either 'm' or 'y'. Most of the other chips have it set to 'y', keeping it built-in. |
|
| 2020-06-03 03:57:37 |
Hui Wang |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-06-03 03:57:37 |
Hui Wang |
bug task added |
|
linux-raspi2 (Ubuntu Eoan) |
|
| 2020-06-05 05:59:54 |
Khaled El Mously |
linux-raspi2 (Ubuntu Eoan): status |
New |
Fix Committed |
|
| 2020-07-01 10:28:43 |
Launchpad Janitor |
linux-raspi2 (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-07-01 10:28:43 |
Launchpad Janitor |
cve linked |
|
2020-0543 |
|
| 2020-07-01 10:28:43 |
Launchpad Janitor |
cve linked |
|
2020-10711 |
|
| 2020-07-01 10:28:43 |
Launchpad Janitor |
cve linked |
|
2020-13143 |
|
| 2021-05-17 15:43:39 |
John Agosta |
removed subscriber John Agosta |
|
|
|
