kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #107478
[Bug 1420575] Re: Ubuntu-LE lpar won't boot with vTPM enabled
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 <leann.ogasawara@xxxxxxxxxxxxx> Mon, 09 Mar 2015 10:08:29 -0700
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
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/1420575
Title:
Ubuntu-LE lpar won't boot with vTPM enabled
Status in linux package in Ubuntu:
Fix Released
Bug description:
[Impact]
Ubuntu-LE lpar on PowerVM system doesn't boot when vTPM is enabled.
It will fail to boot, showing B200A101 reference code on the HMC.
Without vTPM, the lpar boots up just fine.
[Fix]
commit 84eb186bc37c0900b53077ca21cf6dd15823a232 upstream (not in v3.19)
[Test Case]
Boot system with vTPM enabled, ensure system doesn't fail to boot.
--
Here is the console output when attempting to activate the lpar with vTPM enabled after which it fails to boot:
Enter Number of Running Partition (q to quit): 24
24
Opening Virtual Terminal On Partition br13p29 . . .
Open in progress
Open Completed.
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
1 = SMS Menu 5 = Default Boot List
8 = Open Firmware Prompt 6 = Stored Boot List
Memory Keyboard Network Speaker
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM STARTING SOFTWARE IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM PLEASE WAIT... IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM
\
Elapsed time since release of system processors: 0 mins 11 secs
error: no suitable video mode found.
GNU GRUB version 2.02~beta2-21
+----------------------------------------------------------------------------+
|*Ubuntu |
| Advanced options for Ubuntu |
| Ubuntu Vivid Vervet (development branch) (15.04) (on /dev/sda2) |
| Advanced options for Ubuntu Vivid Vervet (development branch) (15.04) (on >|
| |
| |
| |
| |
| |
| |
| |
| |
+----------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, `e' to edit the commands
before booting or `c' for a command-line.
The highlighted entry will be executed automatically in 0s.
Loading Linux 3.18.0-8-generic ...
Loading initial ramdisk ...
OF stdout device is: /vdevice/vty@30000000
Preparing to boot Linux version 3.18.0-8-generic (buildd@fisher01) (gcc version 4.9.2 (Ubuntu 4.9.2-10ubuntu1) ) #9-Ubuntu SMP Mon Jan 5 22:52:15 UTC 2015 (Ubuntu 3.18.0-8.9-generic 3.18.1)
Detected machine type: 0000000000000101
Max number of cores passed to firmware: 256 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... done
command line: BOOT_IMAGE=/boot/vmlinux-3.18.0-8-generic root=UUID=e3bd0893-3e9a-4aaa-924b-0becb28a184e ro splash quiet
memory layout at init:
memory_limit : 0000000000000000 (16 MB aligned)
alloc_bottom : 000000000b4f0000
alloc_top : 0000000010000000
alloc_top_hi : 0000000010000000
rmo_top : 0000000010000000
ram_top : 0000000010000000
instantiating rtas at 0x000000000eca0000... done
instantiating sml at 0x000000000ec70000... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x000000000b500000 -> 0x000000000b5016ff
Device tree struct 0x000000000b510000 -> 0x000000000b540000
Calling quiesce...
returning from prom_init
-> smp_release_cpus()
spinning_secondaries = 7
<- smp_release_cpus()
<- setup_system()
[ 0.586900] Unable to handle kernel paging request for data at address 0x00000028
[ 0.586921] Faulting instruction address: 0xc000000000645614
[ 0.586927] Oops: Kernel access of bad area, sig: 11 [#1]
[ 0.586930] SMP NR_CPUS=2048 NUMA pSeries
[ 0.586936] Modules linked in:
[ 0.586941] CPU: 6 PID: 1 Comm: swapper/0 Not tainted 3.18.0-8-generic #9-Ubuntu
[ 0.586946] task: c000000279580000 ti: c000000279600000 task.ti: c000000279600000
[ 0.586950] NIP: c000000000645614 LR: c0000000000338f0 CTR: c0000000006455c0
[ 0.586954] REGS: c0000002796035f0 TRAP: 0300 Not tainted (3.18.0-8-generic)
[ 0.586958] MSR: 8000000100009033 <SF,EE,ME,IR,DR,RI,LE> CR: 82000022 XER: 20000010
[ 0.586969] CFAR: c0000000006455ec DAR: 0000000000000028 DSISR: 40000000 SOFTE: 1
GPR00: c0000000000338f0 c000000279603870 c000000001426710 c000000276902400
GPR04: 0000000000000001 c00000000b500332 c000000000a7b960 c00000000b538d9c
GPR08: 0000000000000008 0000000000000000 0000000000000000 0000000000000000
GPR12: c0000000006455c0 c00000000e7f3600 c00000000000bde8 0000000000000000
GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR20: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
GPR24: 0000000000000000 c00000000137f9a8 c000000276902800 c00000000137fa20
GPR28: c000000001474a68 c000000276902400 c00000000137f9a8 c000000276902400
[ 0.587023] NIP [c000000000645614] tpm_ibmvtpm_get_desired_dma+0x54/0x70
[ 0.587029] LR [c0000000000338f0] vio_bus_probe+0x2c0/0x480
[ 0.587032] Call Trace:
[ 0.587035] [c000000279603870] [c00000027fffeb00] 0xc00000027fffeb00 (unreliable)
[ 0.587041] [c0000002796038a0] [c0000000000338f0] vio_bus_probe+0x2c0/0x480
[ 0.587047] [c000000279603940] [c00000000065363c] driver_probe_device+0xec/0x4a0
[ 0.587052] [c0000002796039d0] [c000000000653bac] __driver_attach+0x11c/0x120
[ 0.587057] [c000000279603a10] [c00000000065055c] bus_for_each_dev+0x9c/0x110
[ 0.587062] [c000000279603a60] [c000000000652dbc] driver_attach+0x3c/0x60
[ 0.587068] [c000000279603a90] [c000000000652768] bus_add_driver+0x208/0x320
[ 0.587072] [c000000279603b20] [c00000000065486c] driver_register+0x9c/0x180
[ 0.587077] [c000000279603b90] [c000000000032078] __vio_register_driver+0x78/0xd0
[ 0.587082] [c000000279603c10] [c000000000de5fd8] ibmvtpm_module_init+0x2c/0x40
[ 0.587089] [c000000279603c30] [c00000000000b4dc] do_one_initcall+0x12c/0x280
[ 0.587094] [c000000279603d00] [c000000000d94174] kernel_init_freeable+0x25c/0x33c
[ 0.587099] [c000000279603dc0] [c00000000000be0c] kernel_init+0x2c/0x140
[ 0.587104] [c000000279603e30] [c000000000009568] ret_from_kernel_thread+0x5c/0x74
[ 0.587109] Instruction dump:
[ 0.587111] e93f00e8 2fa90000 419e0024 e9290120 80690028 3c630001 38210030 e8010010
[ 0.587119] ebe1fff8 7c0803a6 4e800020 39200000 <80690028> 3c630001 38210030 e8010010
[ 0.587131] ---[ end trace abfb9dc75b29309e ]---
[ 0.589187]
[ 2.589254] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.589254]
[ 2.593773] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b
[ 2.593773]
These are the patches needed, base on the error I see from the bug
report. However, please note that I have not tested them to confirm.
> http://sourceforge.net/p/tpmdd/mailman/message/32960386/
This was accepted upstream. However, as you mentioned that you
couldn't find it in the 3.19, I'll have to follow up with you on this.
> http://sourceforge.net/p/tpmdd/mailman/message/33351549/
This one is in the process of getting accepted. It was just reviewed,
but I need reformat the patch to resubmit it.
>Hmm, if it was accepted before 3.19 it should appear in 3.19, unless it was reverted, which doesn't seem to be the case.
Right, it "should" appear in 3.19, but not necessarily. In this case, the patch wouldn't be available in the 3.19 kernel. The TPM maintainers bundled the vtpm patch with many others and somehow missed the last merge window in submitting to Linus. They had then resubmitted a pull request on Jan 17, 2015. Therefore, the patch will be available in 3.20 instead.
The fix is now available in the git repository at:
https://github.com/PeterHuewe/linux-tpmdd/commit/84eb186bc37c0900b53077ca21cf6dd15823a232
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420575/+subscriptions
