Ubuntu-LE lpar won't boot with vTPM enabled

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

Upstream commit 84eb186bc37c0900b53077ca21cf6dd15823a232

Sent patch to ML.

------- Comment From <email address hidden> 2015-02-16 12:45 EDT-------
==== State: Assigned by: sowsrira on 16 February 2015 06:42:58 ====

Checking this now. More updates little later.

------- Comment From <email address hidden> 2015-02-16 15:15 EDT-------
==== State: Assigned by: sowsrira on 16 February 2015 09:06:11 ====

-> Copied the patches specified by Luciano, to test lpar and installed:

root@br13p29:~# cd /tmp/vTPM
root@br13p29:/tmp/vTPM# ls
linux-headers-3.18.0-13_3.18.0-13.14+121407_all.deb
linux-headers-3.18.0-13-generic_3.18.0-13.14+121407_ppc64el.deb
linux-image-3.18.0-13-generic_3.18.0-13.14+121407_ppc64el.deb

root@br13p29:/tmp/vTPM# sudo dpkg -i linux-*-3.18.0-13*.deb
Selecting previously unselected package linux-headers-3.18.0-13.
(Reading database ... 53685 files and directories currently installed.)
Preparing to unpack linux-headers-3.18.0-13_3.18.0-13.14+121407_all.deb ...
Unpacking linux-headers-3.18.0-13 (3.18.0-13.14+121407) ...
[ 9733.279108] sda2: WRITE SAME failed. Manually zeroing.
Selecting previously unselected package linux-headers-3.18.0-13-generic.
Preparing to unpack linux-headers-3.18.0-13-generic_3.18.0-13.14+121407_ppc64el.deb ...
Unpacking linux-headers-3.18.0-13-generic (3.18.0-13.14+121407) ...
Selecting previously unselected package linux-image-3.18.0-13-generic.
Preparing to unpack linux-image-3.18.0-13-generic_3.18.0-13.14+121407_ppc64el.deb ...
Done.
Unpacking linux-image-3.18.0-13-generic (3.18.0-13.14+121407) ...
Setting up linux-headers-3.18.0-13 (3.18.0-13.14+121407) ...
Setting up linux-headers-3.18.0-13-generic (3.18.0-13.14+121407) ...
Setting up linux-image-3.18.0-13-generic (3.18.0-13.14+121407) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
update-initramfs: Generating /boot/initrd.img-3.18.0-13-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinux-3.18.0-13-generic
Found initrd image: /boot/initrd.img-3.18.0-13-generic
Found linux image: /boot/vmlinux-3.18.0-8-generic
Found initrd image: /boot/initrd.img-3.18.0-8-generic
[ 9901.951723] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 9901.996240] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 9902.026909] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[ 9902.037979] FAT-fs (sda1): bogus number of reserved sectors
[ 9902.132427] FAT-fs (sda1): bogus number of reserved sectors
[ 9902.203685] qnx4: no qnx4 filesystem (no root dir).
[ 9902.207529] ufs: You didn't specify the type of your ufs filesystem
[ 9902.207529]
[ 9902.207529] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...
[ 9902.207529]
[ 9902.207529] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[ 9902.213054] ufs: ufs_fill_super(): bad magic number
[ 9902.916866] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 9902.922651] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 9902.928845] EXT4-fs (sdb1): VFS: Can't find ext4 filesystem
[ 9902.935619] FAT-fs (sdb1): bogu...

------- Comment From <email address hidden> 2015-02-16 15:51 EDT-------
cde00 (<email address hidden>) added native attachment /tmp/AIXOS05213840/tpmhang.log on 2015-02-16 09:51:32

------- Comment From <email address hidden> 2015-02-16 20:05 EDT-------
==== State: Assigned by: sowsrira on 16 February 2015 13:54:42 ====

vTPM is still enabled:

(0) root @ brhmc12: /root
# date;lssyscfg -r lpar -m alp7fp1 | grep -i p29
Mon Feb 16 13:57:03 CST 2015
name=br13p29,lpar_id=10,lpar_env=aixlinux,state=Running,resource_config=1,os_version=Linux/Debian 3.18.0-8-generic Unknown,logical_serial_num=106786VA,default_profile=br13p29_vscsi-md_srr,curr_profile=br13p29_vscsi-md_srr,work_group_id=none,shared_proc_pool_util_auth=0,allow_perf_collection=0,power_ctrl_lpar_ids=none,boot_mode=norm,lpar_keylock=norm,auto_start=0,redundant_err_path_reporting=0,rmc_state=inactive,rmc_ipaddr=10.33.17.203,time_ref=0,lpar_avail_priority=127,desired_lpar_proc_compat_mode=default,curr_lpar_proc_compat_mode=POWER8,suspend_capable=1,remote_restart_capable=0,simplified_remote_restart_capable=0,sync_curr_profile=0,affinity_group_id=none,vtpm_enabled=1 <-----

------- Comment From <email address hidden> 2015-02-17 09:35 EDT-------
==== State: Assigned by: sowsrira on 17 February 2015 03:29:01 ====

Yesterday (2/16) at 10:50PM IST and 11:20AM CST, the system alp7fp1 logged the following two SRCs in ASM, which I think is related to the activity for this defect from yesterday.

Can you confirm?

Error/Event Logs

Serviceable/Customer attention events &#8730; Log ID Time Failing subsystem Severity SRC Reported
530AB999 2015-02-16 17:20:24 I/O Adapter Subsystem Unrecoverable Error B4000202 &#8730;
530AB998 2015-02-16 17:20:24 System Hypervisor Firmware Unrecoverable Error B400F104 &#8730;

B4000202

Explanation
An unrecoverable assert has occurred.
Response
Collect a resource dump for the firmware resource that logged the error.

B400F104

Explanation
System firmware Error
Response
Send the resource dump to the next level of support.

Current state of br13p29 lpar:
------------------------------

(0) root @ brhmc12: /root
# lssyscfg -r lpar -F name,state,lpar_id,os_version -m alp7fp1|grep p29
br13p29,Running,10,Unknown

With ref code:

(0) root @ brhmc12: /root
# lsrefcode -m alp7fp1 -r lpar|grep -i p29
lpar_name=br13p29,lpar_id=10,time_stamp=02/16/2015 20:13:19,refcode=D200A200,word2=03800000,word3=00000011,word4=00000007

D200A200

Explanation
Begin partition power down. SRC word 3 contains the reason for the power off.
Problem determination

SRC word 3 power down reasons

1: White button power down (also known as delayed power off)
2: Partition requested power down
3: Partition requested end of life
4: System wide shutdown
5: Attention link loader
6: Attention MSD
7: Panel function 3 requested
8: Panel function 8 requested
9: Panel function 22 requested
A: Panel function 34 requested

I'm a bit confused about the following comments. Have you re-tested with 84eb186bc37c0900b53077ca21cf6dd15823a232 and found that it isn't sufficient to fix the original issue?

------- Comment From <email address hidden> 2015-02-23 17:16 EDT-------
(In reply to comment #32)
> I'm a bit confused about the following comments. Have you re-tested with
> 84eb186bc37c0900b53077ca21cf6dd15823a232 and found that it isn't sufficient
> to fix the original issue?

Hi Chris,

In kernel configs with both IMA and vTPM enabled, it was found we can encounter a hang on boot. A patch was submitted upstream and tested with the upstream kernel and the Ubuntu kernel that fixes it. So, along with the previous two fixes, this new fix will also be necessary to fix the LE issues with vTPM

http://sourceforge.net/p/tpmdd/mailman/tpmdd-devel/thread/1424477484.26401.17.camel%40oc8377654763.ibm.com/#msg33479104

------- Comment From <email address hidden> 2015-02-24 15:15 EDT-------
==== State: Assigned by: sowsrira on 24 February 2015 09:09:01 ====

Can we get a patch for the HST test lpars to run Ubuntu-LE with vTPM enabled?
I don't know how long it would take for us to get an image with the integrated fix.

------- Comment From <email address hidden> 2015-03-02 16:05 EDT-------
==== State: Assigned by: derrickk on 02 March 2015 10:00:04 ====

What is the latest update here??

Two things about this bug:

a) I understand that this bug severity is much higher than 'Medium' as it is set. Can it be changed to 'high'?

b) Also, can we include the patch included at comment #10? It seems to be accepted and should appear upstream soon.

------- Comment From <email address hidden> 2015-03-02 18:25 EDT-------
The following patches must be applied in order to fix this bug:

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

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

https://sourceforge.<email address hidden>/#msg33479104

They were all accepted and submitted upstream. The last patch was just recently submitted i.e. please wait for it to be appear upstream soon. Thanks!

We've already picked up and applied commit 84eb186b to our Vivid kernel, ie.

  commit 84eb186bc37c0900b53077ca21cf6dd15823a232
  Author: Hon Ching (Vicky) Lo <email address hidden>
  Date: Sun Nov 30 15:01:28 2014 +0100

    tpm: Fix NULL return in tpm_ibmvtpm_get_desired_dma

We still need to cherry-pick eb71f8a5:

  commit eb71f8a5e33fa1066fb92f0111ab366a341e1f6c
  Author: honclo <email address hidden>
  Date: Thu Feb 12 21:02:24 2015 -0500

    Added Little Endian support to vtpm module

And we still need to pick the last patch which is currently in the TPM Device Driver Maintainer's tree -> git://github.com/PeterHuewe/linux-tpmdd.git

  commit 2aee7fb855f221639bc3ed5a15c6d758fe0cf0fa
  Author: <email address hidden> <email address hidden>
  Date: Fri Feb 20 18:11:24 2015 -0600

    tpm/ibmvtpm: Additional LE support for tpm_ibmvtpm_send

------- Comment From <email address hidden> 2015-03-05 12:15 EDT-------
==== State: Assigned by: sowsrira on 05 March 2015 06:11:28 ====

Applied the test kernel patches provided by Vicky, reboot the lpar, shutdown to enable vTPM and reactivated with vTPM enabled.

The lpar now boots up with vTPM enabled, with patched kernel.
Details below.

root@br13p29:~/SW294167# pwd
/root/SW294167
root@br13p29:~/SW294167# ls
linux-headers-3.18.0-13_3.18.0-13.14+test4_all.deb
linux-headers-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb
linux-image-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb
linux-image-extra-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb
root@br13p29:~/SW294167# sudo dpkg -i linux-*-3.18.0-13*.deb
(Reading database ... 78251 files and directories currently installed.)
Preparing to unpack linux-headers-3.18.0-13_3.18.0-13.14+test4_all.deb ...
Unpacking linux-headers-3.18.0-13 (3.18.0-13.14+test4) over (3.18.0-13.14+121407) ...
[13771.481033] sdb2: WRITE SAME failed. Manually zeroing.
Preparing to unpack linux-headers-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb ...
Unpacking linux-headers-3.18.0-13-generic (3.18.0-13.14+test4) over (3.18.0-13.14+121407) ...
Preparing to unpack linux-image-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb ...
Done.
Unpacking linux-image-3.18.0-13-generic (3.18.0-13.14+test4) over (3.18.0-13.14+121407) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
Selecting previously unselected package linux-image-extra-3.18.0-13-generic.
Preparing to unpack linux-image-extra-3.18.0-13-generic_3.18.0-13.14+test4_ppc64el.deb ...
Unpacking linux-image-extra-3.18.0-13-generic (3.18.0-13.14+test4) ...
Setting up linux-headers-3.18.0-13 (3.18.0-13.14+test4) ...
Setting up linux-headers-3.18.0-13-generic (3.18.0-13.14+test4) ...
Setting up linux-image-3.18.0-13-generic (3.18.0-13.14+test4) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Not updating initrd symbolic links since we are being updated/reinstalled
(3.18.0-13.14+121407 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(3.18.0-13.14+121407 was configured last, according to dpkg)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
update-initramfs: Generating /boot/initrd.img-3.18.0-13-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.18.0-13-generic /boot/vmlinux-3.18.0-13-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinux-3.18.0-13-generic
Found initrd image: /boot/initrd.img-3.18.0-13-generic
Found linux image: /boot/vmlinux-3.18.0-8-generic
Found initrd image: /boot/initrd.img-3.18.0-8-generic
[14064.149269] EXT4-fs (sda1): VFS: Can't find ext4 filesystem
[14064.161063] EXT4-fs (sda1): VFS: Can't find ext4 filesyst...

This bug was fixed in the package linux - 3.19.0-8.8

---------------
linux (3.19.0-8.8) vivid; urgency=low

  [ Andy Whitcroft ]

  * ubuntu: vbox -- elide the new symlinks and reconstruct on clean:
    - LP: #1426113
  * rebase to stable v3.19.1

  [ John Johansen ]

  * SAUCE: (no-up): apparmor: fix mediation of fs unix sockets
    - LP: #1408833

  [ Leann Ogasawara ]

  * Release Tracking Bug
    - LP: #1429940

  [ Upstream Kernel Changes ]

  * xen: correct bug in p2m list initialization
  * net/mlx5_core: Fix configuration of log_uar_page_sz
    - LP: #1419938
  * tpm/ibmvtpm: Additional LE support for tpm_ibmvtpm_send
    - LP: #1420575
  * net/mlx4_core: Maintain a persistent memory for mlx4 device
    - LP: #1422481
  * net/mlx4_core: Set device configuration data to be persistent across
    reset
    - LP: #1422481
  * net/mlx4_core: Refactor the catas flow to work per device
    - LP: #1422481
  * net/mlx4_core: Enhance the catas flow to support device reset
    - LP: #1422481
  * net/mlx4_core: Activate reset flow upon fatal command cases
    - LP: #1422481
  * net/mlx4_core: Manage interface state for Reset flow cases
    - LP: #1422481
  * net/mlx4_core: Handle AER flow properly
    - LP: #1422481
  * net/mlx4_core: Enable device recovery flow with SRIOV
    - LP: #1422481
  * net/mlx4_core: Reset flow activation upon SRIOV fatal command cases
    - LP: #1422481
  * tg3: Hold tp->lock before calling tg3_halt() from tg3_init_one()
    - LP: #1428111
  * rebase to v3.19.1
    - LP: #1410704
    - LP: #1411193
    - LP: #1400215
 -- Leann Ogasawara <email address hidden> Mon, 09 Mar 2015 10:08:29 -0700

------- Comment From <email address hidden> 2015-03-23 02:51 EDT-------
The fix is verified in the 3.19.0-8 kernel.

From /var/log/dmesg :

[ 0.000000] Kernel command line: BOOT_IMAGE=/vmlinux-3.19.0-8-generic root=/dev/mapper/idahop05--vg-root ro splash quiet ima_tcb

[ 0.394042] tpm_ibmvtpm 30000005: CRQ initialization completed

--------
root@idahop05:/var/log# uname -a

Linux idahop05 3.19.0-8-generic #8-Ubuntu SMP Tue Mar 10 13:07:58 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

--------
root@idahop05:~# ls -l /dev/tpm0
crw------- 1 root root 10, 224 Mar 17 14:23 /dev/tpm0

------- Comment From <email address hidden> 2015-03-26 12:45 EDT-------
==== State: Working by: sowsrira on 26 March 2015 07:43:29 ====

I had tested the patch successfully. As Manjunath B. Muttur will be taking over the test partition, I'm re-assigning this to him to be able to verify before getting closed.

Thanks.
Sowmya.