group.of.nepali.translators team mailing list archive

[Stefan Bader <stefan.bader@xxxxxxxxxxxxx>]

** Also affects: linux (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1730660

Title:
  Set PANIC_TIMEOUT=10 on Power Systems

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New

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/kernel/panic should be 10. It's 0 for xenial, zesty and artful. After the fix, it's 10.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730660/+subscriptions