[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2018-07-25 Thread bugproxy
*** This bug is a duplicate of bug 1709171 *** https://bugs.launchpad.net/bugs/1709171 --- Comment From danie...@br.ibm.com 2018-07-25 17:46 EDT--- Issue is fixed in ubuntu18.04: root@ubuntu1804:~# uname -a Linux ubuntu1804 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:37:15 UTC

[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2017-10-04 Thread bugproxy
*** This bug is a duplicate of bug 1709171 *** https://bugs.launchpad.net/bugs/1709171 --- Comment From nfont...@us.ibm.com 2017-10-04 10:10 EDT--- (In reply to comment #16) > Hi Nathan, > > > I wouldn't consider this a duplicate of 1709171. The patch referred to in > > this bz is a

[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2017-10-03 Thread bugproxy
*** This bug is a duplicate of bug 1709171 *** https://bugs.launchpad.net/bugs/1709171 --- Comment From danie...@br.ibm.com 2017-10-03 20:03 EDT--- Hi Nathan, > I wouldn't consider this a duplicate of 1709171. The patch referred to in > this bz is a more complete fix than just

[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2017-10-03 Thread bugproxy
*** This bug is a duplicate of bug 1709171 *** https://bugs.launchpad.net/bugs/1709171 --- Comment From nfont...@us.ibm.com 2017-10-03 17:15 EDT--- (In reply to comment #14) > > bug 1709171 now disables CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE, so this bug > > may be a duplicate of that?

[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2017-10-02 Thread bugproxy
--- Comment From danie...@br.ibm.com 2017-10-02 09:54 EDT--- > bug 1709171 now disables CONFIG_MEMORY_HOTPLUG_DEFAULT_ONLINE, so this bug > may be a duplicate of that? Yes, this bug is now a duplicate of 1709171. -- You received this bug notification because you are a member of Kernel

[Kernel-packages] [Bug 1710922] Comment bridged from LTC Bugzilla

2017-08-16 Thread bugproxy
--- Comment From danie...@br.ibm.com 2017-08-16 14:37 EDT--- > Did this issue start happening after an update/upgrade? Was there a prior > kernel version where you were not having this particular problem? First time I've noticed this issue was with a 4.11 kernel in Ubuntu 17.10 about a