[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-08-04 Thread Launchpad Bug Tracker 
This bug was fixed in the package makedumpfile - 1:1.5.9-5ubuntu0.1

---
makedumpfile (1:1.5.9-5ubuntu0.1) xenial; urgency=medium

  [ Hari Bathini  ]
  * Fix networked kdump failure to reach remote server.
Avoids "Network is unreachable" message when trying to do remote dumps on
either SSH or NFS. (LP: #1571590)

  * Replace maxcpus by nr_cpus
nr_cpus is a hard limit that has an impact on the (kdump) kernel
memory consumption, while it is not the case with maxcpus=1, as we can
theoretically hotplug cpus with maxcpus=1 (LP: #1568952)

  * define_stampdir() : Loop on hostname -I for 5 sec to get IP address
if HOSTTAG=ip. The network stack may not be ready when kdump-config runs.
Give it some time before reverting HOSTTAG to hostname if an IP address
cannot be found. (LP: #1599561)

  * Add cio_ignore result to /etc/default/kdump-tools on s390x
In order to have crashkernel=128M to work correctly on the s390
architecture the result of cio_ignore -u -k needs to be appended to the
KDUMP_CMDLINE_APPEND variable in /etc/default/kdump-tools. This patch
adds the required logic to do the proper modification.  (LP: #1570775)

  * debian/rules : drop the dh_installinit override
Uses a syntax which is no longer supported and generate an error on
install. (LP: #1599491)

 -- Louis Bouchard   Fri, 22 Jul 2016
10:15:20 +0200

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Released
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Use a more restrictive kernel boot option to limit CPU numbers to 1

  [Impact]
  Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)

  [Fix]
  Change the maxcpus boot parameter used in the kexec command by nr_cpus.

  [Test Case]
  kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.

  [Regression]
  None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.

  [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.

  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Userspace tool: kdump-tools  version 1:1.5.9-5

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  >
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  >
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list:

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-07-25 Thread bugproxy 
** Tags removed: targetmilestone-inin--- verification-needed
** Tags added: targetmilestone-inin16041 verification-done

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Use a more restrictive kernel boot option to limit CPU numbers to 1

  [Impact]
  Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)

  [Fix]
  Change the maxcpus boot parameter used in the kexec command by nr_cpus.

  [Test Case]
  kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.

  [Regression]
  None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.

  [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.

  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Userspace tool: kdump-tools  version 1:1.5.9-5

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  >
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  >
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-07-22 Thread Adam Conrad 
Hello bugproxy, or anyone else affected,

Accepted makedumpfile into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/makedumpfile/1:1.5.9-5ubuntu0.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: makedumpfile (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  Fix Committed
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Use a more restrictive kernel boot option to limit CPU numbers to 1

  [Impact]
  Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)

  [Fix]
  Change the maxcpus boot parameter used in the kexec command by nr_cpus.

  [Test Case]
  kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.

  [Regression]
  None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.

  [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.

  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Userspace tool: kdump-tools  version 1:1.5.9-5

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  >
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  >
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-07-21 Thread Louis Bouchard 
** Changed in: makedumpfile (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: makedumpfile (Ubuntu Xenial)
   Importance: Undecided => Low

** Description changed:

+ [SRU justification]
+ Use a more restrictive kernel boot option to limit CPU numbers to 1
+ 
+ [Impact]
+ Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)
+ 
+ [Fix]
+ Change the maxcpus boot parameter used in the kexec command by nr_cpus.
+ 
+ [Test Case]
+ kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.
+ 
+ [Regression]
+ None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.
+ 
+ [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
-  
+ 
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
-  
- Userspace tool: kdump-tools  version 1:1.5.9-5 
+ 
+ Userspace tool: kdump-tools  version 1:1.5.9-5
  
  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
- > 
+ >
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
- > 
+ >
  > Thanks.
  
  Hi Kevin,
  
  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b
  
  About other architectures, I am not really sure.
  
  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.
  
  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:
  
  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
-  KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
-  KDUMP_DIR="/var/lib/kdump"
-  MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
+  KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
+  KDUMP_DIR="/var/lib/kdump"
+  MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
-  KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
-  [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;
+  KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
+  [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;
  
  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  In Progress
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  [SRU justification]
  Use a more restrictive kernel boot option to limit CPU numbers to 1

  [Impact]
  Will significantly lower crashkernel memory usage on some architectures 
(namely ppc64el)

  [Fix]
  Change the maxcpus boot parameter used in the kexec command by nr_cpus.

  [Test Case]
  kexec-config show will display maxcpus=1 without the change. It will show 
nr_cpus=1 with the proposed change.

  [Regression]
  None expected, nr_cpus is a more generic parameter and is more restrictive 
than the previous parameter.

  [Original Problem Description of the problem]
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.

  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux

  Userspace tool: kdump-tools  version 1:1.5.9-5

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  >
  > Would you please validate that nr_cpus is

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-07-11 Thread Louis Bouchard 
This has been fixed in version 1.6.0-1 available in Yakkety.

** Changed in: makedumpfile (Ubuntu Yakkety)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-06-10 Thread Louis Bouchard 
Hello,

I am preparing a new release following a new upstream version and will
implement that change.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-06-10 Thread Louis Bouchard 
** Also affects: makedumpfile (Ubuntu Yakkety)
   Importance: Undecided
 Assignee: Taco Screen team (taco-screen-team)
   Status: New

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

** Changed in: makedumpfile (Ubuntu Xenial)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  New
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Yakkety:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-04-12 Thread Louis Bouchard 
Hello,

I am not against the modification but would like to understand better the 
rationale behind this. According to the kernel doc we have : 
maxcpus=[SMP] Maximum number of processors that an SMP kernel   
   
should make use of.  maxcpus=n : n >= 0 limits the  
   
kernel to using 'n' processors.  n=0 is a special case, 
   
it is equivalent to "nosmp", which also disables
   
the IO APIC.
   

   
nr_cpus=[SMP] Maximum number of processors that an SMP kernel   
   
could support.  nr_cpus=n : n >= 1 limits the kernel to 
   
supporting 'n' processors. Later in runtime you can not 
   
use hotplug cpu feature to put more cpu back to online. 
   
just like you compile the kernel NR_CPUS=n  
   

I personally would be inclined to use maxcpus=0 and totally disable SMP
but I am opened to other options.

Kind regards,

...Louis

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1568952] Re: ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1" in kdump-tools

2016-04-11 Thread Kevin W. Rudd 
** Package changed: ubuntu => makedumpfile (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1568952

Title:
  ISST-LTE:pVM:thymelp2:ubuntu 16.04: change "maxcpus=1" to "nr_cpus=1"
  in kdump-tools

Status in makedumpfile package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Ping Tian Han - 2016-04-07 23:04:30 ==
  ---Problem Description---
  Because canonical  has fixed bug 137281 ( LP: #1560552 ) in 4.4.0-17-generic, 
the kernel now supports "nr_cpus=1". So we should update the "maxcpus=1" to 
"nr_cpus=1" in /etc/default/kdump-tools I think.
   
  ---uname output---
  Linux thymelp2 4.4.0-17-generic #33-Ubuntu SMP Tue Mar 29 17:15:31 UTC 2016 
ppc64le ppc64le ppc64le GNU/Linux
   
  Userspace tool: kdump-tools  version 1:1.5.9-5 

  == Comment: #2 - Hari Krishna Bathini - 2016-04-11 04:36:14 ==
  (In reply to comment #1)
  > Hari.
  > 
  > Would you please validate that nr_cpus is consistent across architectures
  > and should become the new default?
  > 
  > Thanks.

  Hi Kevin,

  I know nr_cpus=1 is supported on x86 based on this patch
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=14cb6dcf0a023f5977461c94d8d5a163c937979b

  About other architectures, I am not really sure.

  But looking at the kdump-tools source package, it seems like other 
architectures
  are using maxcpus=1 to boot kdump kernel unless there is architecture specific
  overrides that are missing in the source. Canonical might be able to answer 
better.

  If other aren't using or willing to use nr_cpus=1, we may need a patch
  of this kind:

  diff --git a/kdump-config b/kdump-config
  index 0ff0e6f..aba300e 100755
  --- a/kdump-config
  +++ b/kdump-config
  @@ -48,7 +48,11 @@ KDUMP_COREDIR=${KDUMP_COREDIR:=/var/crash}
   KDUMP_DUMP_DMESG=${KDUMP_DUMP_DMESG:=1}
   KDUMP_DIR="/var/lib/kdump"
   MAKEDUMP_ARGS=${MAKEDUMP_ARGS:="-c -d 31"}
  -KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +if [ "$ARCH" = "ppc64le" ]; then
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll nr_cpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +else
  +   KDUMP_CMDLINE_APPEND=${KDUMP_CMDLINE_APPEND:="irqpoll maxcpus=1 nousb 
systemd.unit=kdump-tools.service"}
  +fi
   KDUMP_KERNEL_HOOK="/etc/kernel/postinst.d/kdump-tools"
   [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ;

  == Comment: #4 - Kevin W. Rudd - 2016-04-11 11:08:16 ==
  Mirroring to Canonical for their review and feedback.

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp