Indeed it has been merged, albeit with a slightly different commit
subject (which is why I did not find it). I'm marking this fix released
for Xenial since the v4.4 based kernel will be uploaded real soon now.

** Also affects: linux (Ubuntu Xenial)
   Importance: Medium
     Assignee: Canonical Kernel Team (canonical-kernel-team)
       Status: Triaged

** Changed in: linux (Ubuntu Xenial)
       Status: Triaged => Fix Released

** Changed in: linux (Ubuntu Xenial)
     Assignee: Canonical Kernel Team (canonical-kernel-team) => Tim Gardner 
(timg-tpi)

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

** Changed in: linux (Ubuntu Wily)
       Status: New => In Progress

** Changed in: linux (Ubuntu Wily)
     Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

** Changed in: linux (Ubuntu Vivid)
       Status: New => In Progress

** Changed in: linux (Ubuntu Vivid)
     Assignee: (unassigned) => Tim Gardner (timg-tpi)

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

Title:
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  In Progress
Status in linux source package in Wily:
  In Progress
Status in linux source package in Xenial:
  Fix Released

Bug description:
  ---Problem Description---
  Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
   
  Contact Information = Sachin Sant / ss...@in.ibm.com 
   
  ---uname output---
  3.19.0-18-generic
   
  ---Patches Installed---
  A patched powerpc-ibm-utils package is required
   
  Machine Type = POWER8 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1) Using latest daily ISO install 14.04.02 as a Power VM guest
  2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
  3) Ensure ksh and powerpc-ibm-utils packages are installed.
  4) Download following DLPAR packages from 
http://ausgsa.ibm.com/projects/r/rsctdev/builds/muthu/rmuts006a/ppc64le/

  devices.chrp.base.servicerm_2.5.0.1-15111_ppc64el.deb
  dynamicrm_2.0.1-3_ppc64el.deb
  rsct.core_3.2.0.6-15111_ppc64el.deb
  rsct.core.utils_3.2.0.6-15111_ppc64el.deb
  src_3.2.0.6-15111_ppc64el.deb

  5) Install the packages.
  6) Perform a add memory operation via HMC
   
  Stack trace output:

  alp9 kernel: [44170.234662] ------------[ cut here ]------------
  alp9 kernel: [44170.234667] WARNING: at 
/build/buildd/linux-lts-vivid-3.19.0/drivers/base/memory.c:200
  alp9 kernel: [44170.234668] Modules linked in: rpadlpar_io rpaphp pseries_rng 
rtc_generic
  alp9 kernel: [44170.234675] CPU: 2 PID: 1391 Comm: systemd-udevd Not tainted 
3.19.0-18-generic #18~14.04.1-Ubuntu
  alp9 kernel: [44170.234677] task: c0000003dbea7c80 ti: c0000003dbf10000 
task.ti: c0000003dbf10000
  Jun  4 19:44:47 alp9 kernel: [44170.234678] NIP: c000000000668f34 LR: 
c0000000006699b0 CTR: 0000000000000000
  Jun  4 19:44:47 alp9 kernel: [44170.234680] REGS: c0000003dbf13910 TRAP: 0700 
  Not tainted  (3.19.0-18-generic)
  Jun  4 19:44:47 alp9 kernel: [44170.234680] MSR: 8000000000029033 
<SF,EE,ME,IR,DR,RI,LE>  CR: 28042888  XER: 20000000
  Jun  4 19:44:47 alp9 kernel: [44170.234686] CFAR: c000000000668ed8 SOFTE: 1 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR00: c0000000006699b0 
c0000003dbf13b90 c00000000144c760 0000000000000001 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR04: 0000000000000779 
0000000000000100 0000000000078000 f000000001de4000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR08: c0000000013ac760 
0000000000000001 0000000000007790 00000000003fffff 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR12: c00000000172cb00 
c00000000e831200 00000100074a0010 0000000000000000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR16: 0000000010032230 
00000000100311d0 00003fffcb59bf20 0000000000000003 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR20: 00000000100527f8 
00000000100322b0 0000000001312d00 00000100074af7f0 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR24: 00000000100322d0 
00003fffcb59bf20 c0000003dbf13e00 0000000000000000 
  Jun  4 19:44:47 alp9 kernel: [44170.234686] GPR28: 0000000000001000 
0000000000000000 0000000000077000 0000000000077900 
  Jun  4 19:44:47 alp9 kernel: [44170.234707] NIP [c000000000668f34] 
pages_correctly_reserved+0x134/0x1c0
  Jun  4 19:44:47 alp9 kernel: [44170.234709] LR [c0000000006699b0] 
memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234710] Call Trace:
  Jun  4 19:44:47 alp9 kernel: [44170.234711] [c0000003dbf13b90] 
[0000000000000006] 0x6 (unreliable)
  Jun  4 19:44:47 alp9 kernel: [44170.234714] [c0000003dbf13c00] 
[c0000000006699b0] memory_subsys_online+0x70/0x140
  Jun  4 19:44:47 alp9 kernel: [44170.234716] [c0000003dbf13c40] 
[c0000000006476f4] device_online+0xb4/0x120
  Jun  4 19:44:47 alp9 kernel: [44170.234718] [c0000003dbf13c80] 
[c00000000066987c] store_mem_state+0x8c/0x150
  Jun  4 19:44:47 alp9 kernel: [44170.234721] [c0000003dbf13cc0] 
[c000000000643618] dev_attr_store+0x68/0xa0
  Jun  4 19:44:47 alp9 kernel: [44170.234724] [c0000003dbf13d00] 
[c00000000035afd0] sysfs_kf_write+0x80/0xb0
  Jun  4 19:44:47 alp9 kernel: [44170.234726] [c0000003dbf13d40] 
[c000000000359f0c] kernfs_fop_write+0x18c/0x1f0
  Jun  4 19:44:47 alp9 kernel: [44170.234730] [c0000003dbf13d90] 
[c0000000002b450c] vfs_write+0xdc/0x260
  Jun  4 19:44:47 alp9 kernel: [44170.234732] [c0000003dbf13de0] 
[c0000000002b53bc] SyS_write+0x6c/0x110
  Jun  4 19:44:47 alp9 kernel: [44170.234735] [c0000003dbf13e30] 
[c000000000009258] system_call+0x38/0xd0
  Jun  4 19:44:47 alp9 kernel: [44170.234736] Instruction dump:
  Jun  4 19:44:47 alp9 kernel: [44170.234737] 419e0024 788a2428 7d095214 
2fa80000 41de0014 7d29502a 38e74000 7928ffe3 
  Jun  4 19:44:47 alp9 kernel: [44170.234740] 4082ff7c 3d02fff6 892808e3 
69290001 <0b090000> 2fa90000 40de0068 38600000 
  Jun  4 19:44:47 alp9 kernel: [44170.234744] ---[ end trace f8d28c560fa5c980 
]---
   

  System Dump Info:
    The system is not configured to capture a system dump.
   
  == Comment: #1 - SACHIN P. SANT <ss...@in.ibm.com> - 2015-06-05 01:28:00 ==
  The DLPAR memory operation succeeds and is not affected by this warning.

  == Comment: #3 - Nathan D. Fontenot <nfont...@us.ibm.com> - 2015-06-05 
07:11:45 ==
  Looking at this issue further, it appears to only happen when adding memory 
that was previously removed. When adding memory that has not been assigned to 
the partition yet the warnings are not generated.

  Need to look into the memory remove code paths to make sure we are
  releasing the memory properly.

  == Comment: #4 - Nathan D. Fontenot <nfont...@us.ibm.com> - 2015-06-05 
07:59:17 ==
  I will have to verify in the Ubuntu source, but this seems like this is an 
issue that was solved previously by commit 
2bbcb8788311a40714b585fc11b51da6ffa2ab92.

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/base/memory.c?id=2bbcb8788311a40714b585fc11b51da6ffa2ab92

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463654/+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

Reply via email to