| 2019-04-15 17:39:59 |
Dimitri John Ledkov |
bug |
|
|
added bug |
| 2019-04-15 17:40:28 |
Dimitri John Ledkov |
tags |
|
bot-stop-nagging |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Bionic) |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Cosmic) |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Xenial) |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Ee-series |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Ee-series) |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Disco |
|
| 2019-04-15 17:40:42 |
Dimitri John Ledkov |
bug task added |
|
linux (Ubuntu Disco) |
|
| 2019-04-15 17:41:55 |
Dimitri John Ledkov |
summary |
CONFIG_LOG_BUF_SHIFT is too low on arm64 |
CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64 |
|
| 2019-04-15 18:00:12 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2019-04-15 18:00:15 |
Ubuntu Kernel Bot |
linux (Ubuntu Bionic): status |
New |
Incomplete |
|
| 2019-04-15 18:00:19 |
Ubuntu Kernel Bot |
linux (Ubuntu Cosmic): status |
New |
Incomplete |
|
| 2019-04-15 18:00:22 |
Ubuntu Kernel Bot |
linux (Ubuntu Xenial): status |
New |
Incomplete |
|
| 2019-04-16 09:07:24 |
Dimitri John Ledkov |
description |
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
Please backport this to xenial and up. |
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up. |
|
| 2019-04-16 09:08:17 |
Dimitri John Ledkov |
linux (Ubuntu Disco): status |
Incomplete |
Confirmed |
|
| 2019-04-16 09:08:18 |
Dimitri John Ledkov |
linux (Ubuntu Cosmic): status |
Incomplete |
Confirmed |
|
| 2019-04-16 09:08:21 |
Dimitri John Ledkov |
linux (Ubuntu Bionic): status |
Incomplete |
Confirmed |
|
| 2019-04-16 09:08:23 |
Dimitri John Ledkov |
linux (Ubuntu Xenial): status |
Incomplete |
Confirmed |
|
| 2019-04-16 09:08:25 |
Dimitri John Ledkov |
linux (Ubuntu Ee-series): status |
New |
Confirmed |
|
| 2019-04-16 09:28:32 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu) |
|
| 2019-04-16 09:29:19 |
Dimitri John Ledkov |
description |
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up. |
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before running the tests. |
|
| 2019-04-16 12:19:48 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-04-23 13:16:57 |
Dimitri John Ledkov |
description |
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before running the tests. |
[Impact]
* Too small dmsg kernel buf ring size leads to loosing/missing early boot kernel messages which happen before journald starts slurping them up and storing them on disc. This results in messages similar to this one on boot "missed NN kernel messages on boot". This is especially pronounced on arm64 as the default setting there is way lower than any other 32bit or 64bit architecture we ship. Also amd64 appears to have the highest setting of 18 among all architectures we ship. The best course of action to bump all 64bit arches to 18, and keep all 32bit arches at the current & upstream default of 17.
[Test Case]
* $ cat /boot/config-`uname -r` | grep CONFIG_LOG_BUF_SHIFT
on 64bit arches result should be: CONFIG_LOG_BUF_SHIFT=18
on 32bit arches result should be: CONFIG_LOG_BUF_SHIFT=17
* run systemd adt test, the boot-and-services test case should not fail journald tests with "missed kernel messages" visible in the error logs.
[Regression Potential]
* Increasing the size of the log_buf, will increase kernel memory usage which cannot be reclaimed. It will now become 256kb on arm64, ppc64el, s390x instead of 8kB/128kb/128kb respectively. 32bit arches remain unchanged at 128kb.
[Other Info]
* Original bug report
CONFIG_LOG_BUF_SHIFT
policy<{
'amd64' : '18',
'arm64' : '14',
'armhf' : '17',
'i386' : '17',
'ppc64el': '17',
's390x' : '17'}>
Please set CONFIG_LOG_BUF_SHIFT to at least 17 on arm64.
Potentially bump all 64-bit arches to 18 (or higher!) as was done on amd64, meaning set 18 on arm64 s390x ppc64el.
I have a systemd autopkgtest test that asserts that we see Linux kernel command line in the dmesg (journalctl -k -b). And it is consistently failing on arm64 scalingstack KVM EFI machines with messages of "missing 81 kernel messages".
config LOG_BUF_SHIFT
int "Kernel log buffer size (16 => 64KB, 17 => 128KB)"
range 12 25
default 17
depends on PRINTK
help
Select the minimal kernel log buffer size as a power of 2.
The final size is affected by LOG_CPU_MAX_BUF_SHIFT config
parameter, see below. Any higher size also might be forced
by "log_buf_len" boot parameter.
Examples:
17 => 128 KB
16 => 64 KB
15 => 32 KB
14 => 16 KB
13 => 8 KB
12 => 4 KB
14 sounds like redictiously low for arm64. given that 17 is default across 32-bit arches, and 18 is default on amd64.
On a related note, we have CONFIG_PRINTK_SAFE_LOG_BUF_SHIFT policy<{'amd64': '13', 'arm64': '13', 'armhf': '13', 'i386': '13', 'ppc64el': '13', 's390x': '13'}>
I'm not sure if we want to bump these up to LOG_BUF_SHIFT size or not.
Please backport this to xenial and up.
=== systemd ===
systemd, boot-and-services test case can bump the ring buffer before running the tests. |
|
| 2019-05-08 17:15:25 |
Kleber Sacilotto de Souza |
linux (Ubuntu Disco): status |
Confirmed |
Fix Committed |
|
| 2019-05-17 09:31:40 |
Ubuntu Kernel Bot |
tags |
bot-stop-nagging |
bot-stop-nagging verification-needed-disco |
|
| 2019-05-20 13:19:36 |
Dimitri John Ledkov |
tags |
bot-stop-nagging verification-needed-disco |
bot-stop-nagging verification-done-disco |
|
| 2019-05-20 13:19:42 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Xenial) |
|
|
| 2019-05-20 13:19:48 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Bionic) |
|
|
| 2019-05-20 13:19:54 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Cosmic) |
|
|
| 2019-05-20 13:20:06 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Disco) |
|
|
| 2019-05-20 13:20:11 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu Eoan) |
|
|
| 2019-05-20 13:20:15 |
Dimitri John Ledkov |
bug task deleted |
systemd (Ubuntu) |
|
|
| 2019-06-04 09:17:48 |
Launchpad Janitor |
linux (Ubuntu Disco): status |
Fix Committed |
Fix Released |
|
| 2019-06-09 16:55:00 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
Confirmed |
Fix Released |
|
| 2019-06-27 05:37:43 |
Evgeny Vereshchagin |
bug watch added |
|
https://github.com/systemd/systemd/issues/11104 |
|
| 2019-06-28 16:14:57 |
Kleber Sacilotto de Souza |
linux (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2019-06-28 16:15:00 |
Kleber Sacilotto de Souza |
linux (Ubuntu Cosmic): status |
Confirmed |
Fix Committed |
|
| 2019-06-28 16:15:05 |
Kleber Sacilotto de Souza |
linux (Ubuntu Xenial): status |
Confirmed |
Fix Committed |
|
| 2019-07-03 11:05:36 |
Ubuntu Kernel Bot |
tags |
bot-stop-nagging verification-done-disco |
bot-stop-nagging verification-done-disco verification-needed-xenial |
|
| 2019-07-03 13:02:56 |
Ubuntu Kernel Bot |
tags |
bot-stop-nagging verification-done-disco verification-needed-xenial |
bot-stop-nagging verification-done-disco verification-needed-cosmic verification-needed-xenial |
|
| 2019-07-03 13:06:57 |
Ubuntu Kernel Bot |
tags |
bot-stop-nagging verification-done-disco verification-needed-cosmic verification-needed-xenial |
bot-stop-nagging verification-done-disco verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
|
| 2019-07-03 18:19:18 |
Dan Streetman |
tags |
bot-stop-nagging verification-done-disco verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
bot-stop-nagging verification-done-disco verification-done-xenial verification-needed-bionic verification-needed-cosmic |
|
| 2019-07-03 18:31:40 |
Dan Streetman |
tags |
bot-stop-nagging verification-done-disco verification-done-xenial verification-needed-bionic verification-needed-cosmic |
bot-stop-nagging verification-done-cosmic verification-done-disco verification-done-xenial verification-needed-bionic |
|
| 2019-07-03 20:08:49 |
Dan Streetman |
tags |
bot-stop-nagging verification-done-cosmic verification-done-disco verification-done-xenial verification-needed-bionic |
bot-stop-nagging verification-done-bionic verification-done-cosmic verification-done-disco verification-done-xenial |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
linux (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2018-12126 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2018-12127 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2018-12130 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2019-11085 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2019-11091 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2019-11815 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2019-11833 |
|
| 2019-07-22 10:53:34 |
Launchpad Janitor |
cve linked |
|
2019-11884 |
|
| 2019-07-24 20:29:02 |
Launchpad Janitor |
linux (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2019-07-24 20:29:02 |
Launchpad Janitor |
cve linked |
|
2019-2054 |
|
| 2019-08-14 21:04:59 |
Terry Rudd |
linux (Ubuntu Cosmic): status |
Fix Committed |
Invalid |
|
