Kernel WARN @drivers/base/memory.c:200 during DLPAR memory operation
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Tim Gardner | ||
Vivid |
Fix Released
|
Undecided
|
Tim Gardner | ||
Wily |
Fix Released
|
Undecided
|
Tim Gardner | ||
Xenial |
Fix Released
|
Medium
|
Tim Gardner |
Bug Description
---Problem Description---
Kernel WARN @drivers/
Contact Information = Sachin Sant / <email address hidden>
---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://
devices.
dynamicrm_
rsct.core_
rsct.core.
src_3.2.
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/
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,
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
Jun 4 19:44:47 alp9 kernel: [44170.234709] LR [c0000000006699b0] memory_
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_
Jun 4 19:44:47 alp9 kernel: [44170.234716] [c0000003dbf13c40] [c0000000006476f4] device_
Jun 4 19:44:47 alp9 kernel: [44170.234718] [c0000003dbf13c80] [c00000000066987c] store_mem_
Jun 4 19:44:47 alp9 kernel: [44170.234721] [c0000003dbf13cc0] [c000000000643618] dev_attr_
Jun 4 19:44:47 alp9 kernel: [44170.234724] [c0000003dbf13d00] [c00000000035afd0] sysfs_kf_
Jun 4 19:44:47 alp9 kernel: [44170.234726] [c0000003dbf13d40] [c000000000359f0c] kernfs_
Jun 4 19:44:47 alp9 kernel: [44170.234730] [c0000003dbf13d90] [c0000000002b450c] vfs_write+
Jun 4 19:44:47 alp9 kernel: [44170.234732] [c0000003dbf13de0] [c0000000002b53bc] SyS_write+
Jun 4 19:44:47 alp9 kernel: [44170.234735] [c0000003dbf13e30] [c000000000009258] system_
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 <email address hidden> - 2015-06-05 01:28:00 ==
The DLPAR memory operation succeeds and is not affected by this warning.
== Comment: #3 - Nathan D. Fontenot <email address hidden> - 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 <email address hidden> - 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 2bbcb8788311a40
tags: | added: architecture-ppc64le bugnameltc-125934 severity-high targetmilestone-inin--- |
tags: |
added: severity-medium removed: severity-high |
tags: |
added: targetmilestone-inin14043 removed: targetmilestone-inin--- |
Changed in ubuntu: | |
assignee: | nobody → Taco Screen team (taco-screen-team) |
affects: | ubuntu → linux (Ubuntu) |
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Canonical Kernel Team (canonical-kernel-team) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux (Ubuntu Vivid): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → In Progress |
Changed in linux (Ubuntu Vivid): | |
status: | In Progress → Fix Committed |
Changed in linux (Ubuntu Wily): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-vivid verification-done-wily removed: verification-needed-vivid verification-needed-wily |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1463654/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]