Set PANIC_TIMEOUT=10 on Power Systems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Thadeu Lima de Souza Cascardo | ||
Xenial |
Fix Released
|
High
|
Unassigned | ||
Zesty |
Fix Released
|
High
|
Unassigned | ||
Artful |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
When stopping CPUs fail when doing kdump, the system will hang indefinitively, instead of rebooting. With this option set, it will reboot after 10 seconds when that happens.
This setting has been the default for trusty, where panic_timeout is 10. Later releases set it to 0.
[Test Case]
When booting a kernel, /proc/sys/
[Regression Potential]
For users that rely on the setting as 0, they will see their system reboot 10 seconds after a panic. They can set it back to 0 or other value. Though, on some rare cases, the system might not boot enough for this setting to be set. Balancing that with the case where kdump is used and the system is expected to boot, we expect the 10 seconds setting is okay.
===
For ppc64le, in some rare crash cases, kdump won't load unless timeout is greater than 0. Only 10 has been tested by IBM, so using a smaller value may not work.
CVE References
Changed in linux (Ubuntu): | |
status: | New → Triaged |
assignee: | nobody → Thadeu Lima de Souza Cascardo (cascardo) |
importance: | Undecided → High |
description: | updated |
Changed in linux (Ubuntu): | |
status: | Triaged → In Progress |
Changed in linux (Ubuntu Artful): | |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in linux (Ubuntu Zesty): | |
importance: | Undecided → High |
status: | New → Fix Committed |
Changed in linux (Ubuntu Xenial): | |
importance: | Undecided → High |
status: | New → Fix Committed |
Patches have been sent to the mailing list. Awaiting ACKs.