Kdump boot fails due to Kernel OOPS @tpm_ibmvtpm_probe (PowerVM)

Bug #1468605 reported by bugproxy
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kexec-tools (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

== Comment: #0 - SACHIN P. SANT <email address hidden> - 2015-06-04 06:03:17 ==
---Steps to Reproduce---
1) Using latest daily ISO install 14.04.02 as a Power VM guest. The LPAR has vTPM functionality enabled.
2) Upgrade the kernel to 3.19 level (3.19.0-18-generic)
3) Configure kdump. A fix is required to configure kdump. Refer to defect (https://bugzilla.linux.ibm.com/show_bug.cgi?id=125712)

# kdump-config load
Modified cmdline:BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet vt.handoff=7 irqpoll maxcpus=1 nousb elfcorehdr=155200K
segment[0].mem:0x8000000 memsz:24641536
segment[1].mem:0x9780000 memsz:65536
segment[2].mem:0x9790000 memsz:65536
segment[3].mem:0x97a0000 memsz:65536
segment[4].mem:0x97b0000 memsz:20971520
segment[5].mem:0xec70000 memsz:262144
 * loaded kdump kernel

# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinux-3.19.0-18-generic root=UUID=3ea23bcf-7269-432f-bacc-f82c6cdd774e ro splash quiet crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M vt.handoff=7
#

4) Trigger a crash. Kdump boot fails with a kernel panic

I'm in purgatory
 -> smp_release_cpus()
spinning_secondaries = 0
 <- smp_release_cpus()
 <- setup_system()
[ 0.877197] Unable to handle kernel paging request for data at address 0x00000010
[ 0.877232] Faulting instruction address: 0xc00000000863a044
[ 0.877241] Oops: Kernel access of bad area, sig: 11 [#1]
[ 0.877246] SMP NR_CPUS=2048 NUMA pSeries
[ 0.877255] Modules linked in:
[ 0.877264] CPU: 8 PID: 1 Comm: swapper/8 Not tainted 3.19.0-18-generic #18~14.04.1-Ubuntu
[ 0.877273] task: c000000086bc0000 ti: c000000086c00000 task.ti: c000000086c00000
[ 0.877280] NIP: c00000000863a044 LR: c000000008639f54 CTR: 00000000003fd734
[ 0.877288] REGS: c000000086c03580 TRAP: 0300 Not tainted (3.19.0-18-generic)
[ 0.877294] MSR: 8000000100009033 <SF,EE,ME,IR,DR,RI,LE> CR: 24002022 XER: 20000010
[ 0.877314] CFAR: c000000008639f60 DAR: 0000000000000010 DSISR: 40000000 SOFTE: 1
GPR00: 0000000024002022 c000000086c03800 c00000000944c760 0000000000000100
GPR04: fffffff000000500 0000000000000000 0000000000000000 0000000000000010
GPR08: 0000000000000008 0000000000000000 0000000000000001 0000000000000000
GPR12: fffffffffffffff0 c00000000e7f4800 c00000000800bdd8 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR24: 0000000000000000 c000000086dece00 c000000008a86cb0 fffffffffffffff0
GPR28: 0000000000000000 c0000000823c9848 c00000008608ad00 c0000000823c9800
[ 0.877409] NIP [c00000000863a044] tpm_ibmvtpm_probe+0x2e4/0x580
[ 0.877417] LR [c000000008639f54] tpm_ibmvtpm_probe+0x1f4/0x580
[ 0.877423] Call Trace:
[ 0.877430] [c000000086c03800] [c000000008639e6c] tpm_ibmvtpm_probe+0x10c/0x580 (unreliable)
[ 0.877442] [c000000086c038a0] [c000000008033a1c] vio_bus_probe+0x1bc/0x480
[ 0.877451] [c000000086c03940] [c00000000864b15c] driver_probe_device+0xec/0x470
[ 0.877461] [c000000086c039d0] [c00000000864b69c] __driver_attach+0x11c/0x120
[ 0.877469] [c000000086c03a10] [c00000000864817c] bus_for_each_dev+0x9c/0x110
[ 0.877478] [c000000086c03a60] [c00000000864a8fc] driver_attach+0x3c/0x60
[ 0.877486] [c000000086c03a90] [c00000000864a2d8] bus_add_driver+0x208/0x320
[ 0.877495] [c000000086c03b20] [c00000000864c31c] driver_register+0x9c/0x180
[ 0.877504] [c000000086c03b90] [c0000000080322f8] __vio_register_driver+0x78/0xc0
[ 0.877513] [c000000086c03c10] [c000000008df6de8] ibmvtpm_module_init+0x2c/0x40
[ 0.877523] [c000000086c03c30] [c00000000800b4bc] do_one_initcall+0x11c/0x270
[ 0.877532] [c000000086c03d00] [c000000008da4100] kernel_init_freeable+0x264/0x34c
[ 0.877543] [c000000086c03dc0] [c00000000800bdfc] kernel_init+0x2c/0x130
[ 0.877553] [c000000086c03e30] [c00000000800956c] ret_from_kernel_thread+0x5c/0x70
[ 0.877561] Instruction dump:
[ 0.877567] 38e00000 f8410018 7d2c4b78 4e800421 e8410018 4bfffea0 60420000 38600064
[ 0.877583] 4bb04c35 60000000 e93e0008 38600100 <80890010> 4ba46121 60000000 7c6907b4
[ 0.877607] ---[ end trace c0064a96755f8f13 ]---
[ 0.881558]
[ 2.881696] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.881696]
[ 2.885423] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.885423]

== Comment: #6 - HON CHING LO <email address hidden> - 2015-06-04 16:39:23 ==
The patch was sent upstream and under review. I'll post the commit as soon as it's available.

== Comment: #9 - HON CHING LO <email address hidden> - 2015-06-08 15:42:40 ==
Upstream submission for the patch:

https://sourceforge.net/p/tpmdd/mailman/message/34136266/

bugproxy (bugproxy)
tags: added: architecture-ppc64le bugnameltc-125877 severity-critical targetmilestone-inin14043
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

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/FindRightPackage. 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/1468605/+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.]

tags: added: bot-comment
affects: ubuntu → kexec-tools (Ubuntu)
Revision history for this message
bugproxy (bugproxy) wrote : Logs
  • Logs Edit (7.0 KiB, application/octet-stream)

------- Comment (attachment only) From <email address hidden> 2015-08-03 09:19 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2015-08-17 06:45 EDT-------
When will this fix be integrated into 14.04.03 stream ?

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2015-10-07 05:18 EDT-------
Tested with latest build for 14.04.03. The problem is fixed.

root@ubuntu:/var/crash/201510070111# ls
dmesg.201510070111 dump.201510070111
root@ubuntu:/var/crash/201510070111# cat /etc/issue
Ubuntu 14.04.3 LTS \n \l

root@ubuntu:/var/crash/201510070111# uname -a
Linux ubuntu 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:21:52 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux
root@ubuntu:/var/crash/201510070111#

root@ubuntu:/var/crash/201510070111# cat dmesg.201510070111 | grep tpm
[ 0.376740] tpm_ibmvtpm 30000003: CRQ initialization completed
root@ubuntu:/var/crash/201510070111#

Luciano Chavez (lnx1138)
Changed in kexec-tools (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.