[LTC Test] Ubuntu 18.04: tm_trap_test failed on P8 compat mode guest

Default Comment by Bridge

Default Comment by Bridge

Default Comment by Bridge

Bionic request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-April/091525.html

------- Comment From <email address hidden> 2018-04-16 05:47 EDT-------
When are we getting patches included ?

------- Comment From <email address hidden> 2018-04-22 08:44 EDT-------
(In reply to comment #15)
> When are we getting patches included ?

I just checked and this patch is already included in Ubuntu's tree starting at kernel Ubuntu-4.15.0-17.18, which is already on the proposed archive.

$ git tag --contains 46064a7b8975e551d59803cbaa73223fb38655ed
Ubuntu-4.15.0-16.17
Ubuntu-4.15.0-17.18
Ubuntu-4.15.0-18.19
Ubuntu-4.15.0-19.20

Default Comment by Bridge

This bug was fixed in the package linux - 4.15.0-19.20

---------------
linux (4.15.0-19.20) bionic; urgency=medium

  * linux: 4.15.0-19.20 -proposed tracker (LP: #1766021)

  * Kernel 4.15.0-15 breaks Dell PowerEdge 12th Gen servers (LP: #1765232)
    - Revert "blk-mq: simplify queue mapping & schedule with each possisble CPU"
    - Revert "genirq/affinity: assign vectors to all possible CPUs"

linux (4.15.0-18.19) bionic; urgency=medium

  * linux: 4.15.0-18.19 -proposed tracker (LP: #1765490)

  * [regression] Ubuntu 18.04:[4.15.0-17-generic #18] KVM Guest Kernel:
    meltdown: rfi/fallback displacement flush not enabled bydefault (kvm)
    (LP: #1765429)
    - powerpc/pseries: Fix clearing of security feature flags

  * signing: only install a signed kernel (LP: #1764794)
    - [Packaging] update to Debian like control scripts
    - [Packaging] switch to triggers for postinst.d postrm.d handling
    - [Packaging] signing -- switch to raw-signing tarballs
    - [Packaging] signing -- switch to linux-image as signed when available
    - [Config] signing -- enable Opal signing for ppc64el
    - [Packaging] printenv -- add signing options

  * [18.04 FEAT] Sign POWER host/NV kernels (LP: #1696154)
    - [Packaging] signing -- add support for signing Opal kernel binaries

  * Please cherrypick s390 unwind fix (LP: #1765083)
    - s390/compat: fix setup_frame32

  * Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L]
    [ipr] (LP: #1751813)
    - d-i: move ipr to storage-core-modules on ppc64el

  * drivers/gpu/drm/bridge/adv7511/adv7511.ko missing (LP: #1764816)
    - SAUCE: (no-up) rename the adv7511 drm driver to adv7511_drm

  * Miscellaneous Ubuntu changes
    - [Packaging] Add linux-oem to rebuild test blacklist.

linux (4.15.0-17.18) bionic; urgency=medium

  * linux: 4.15.0-17.18 -proposed tracker (LP: #1764498)

  * Eventual OOM with profile reloads (LP: #1750594)
    - SAUCE: apparmor: fix memory leak when duplicate profile load

linux (4.15.0-16.17) bionic; urgency=medium

  * linux: 4.15.0-16.17 -proposed tracker (LP: #1763785)

  * [18.04] [bug] CFL-S(CNP)/CNL GPIO testing failed (LP: #1757346)
    - [Config]: Set CONFIG_PINCTRL_CANNONLAKE=y

  * [Ubuntu 18.04] USB Type-C test failed on GLK (LP: #1758797)
    - SAUCE: usb: typec: ucsi: Increase command completion timeout value

  * Fix trying to "push" an already active pool VP (LP: #1763386)
    - SAUCE: powerpc/xive: Fix trying to "push" an already active pool VP

  * hisi_sas: Revert and replace SAUCE patches w/ upstream (LP: #1762824)
    - Revert "UBUNTU: SAUCE: scsi: hisi_sas: export device table of v3 hw to
      userspace"
    - Revert "UBUNTU: SAUCE: scsi: hisi_sas: config for hip08 ES"
    - scsi: hisi_sas: modify some register config for hip08
    - scsi: hisi_sas: add v3 hw MODULE_DEVICE_TABLE()

  * Realtek card reader - RTS5243 [VEN_10EC&DEV_5260] (LP: #1737673)
    - misc: rtsx: Move Realtek Card Reader Driver to misc
    - updateconfigs for Realtek Card Reader Driver
    - misc: rtsx: Add support for RTS5260
    - misc: rtsx: Fix symbol clashes

  * Mellanox [mlx5] [bionic] UBSAN: Undefined behaviour in
    ./include/linux/net_dim.h (LP: #1...

Joseph, Thanks for the fix.

We would like to have the fix backported to 16.04 kernels also, since this problem is on those kernel also. Could you please target this bug against artful and xenial also?

Thanks

I built Artful and Xenial test kernels with the back port. The test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
http://kernel.ubuntu.com/~jsalisbury/lp1762928/artful

Can you test this kernel and see if it resolves this bug?

Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages.

Thanks in advance!

------- Comment From <email address hidden> 2018-04-26 03:37 EDT-------
(In reply to comment #26)
> I built Artful and Xenial test kernels with the back port. The test kernels
> can be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
> http://kernel.ubuntu.com/~jsalisbury/lp1762928/artful
>
> Can you test this kernel and see if it resolves this bug?
>
> Note, to test this kernel, you need to install both the linux-image and
> linux-image-extra .deb packages.
>
> Thanks in advance!

Thanks for the packages..

1. artful: tested on latest ubuntu 18.04 host: results are PASS
2. xenial: given at link > http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial does not have ppc64el related packages ..

------- Comment From <email address hidden> 2018-04-26 04:04 EDT-------
Adding to above.. in artful I see a new failure:

========================================
test: tm_unavailable_test
tags: git_version:69bfd470
Checking if FP/VEC registers are sane after a FP unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP ok VEC corrupted! high = 0 low = 0
If MSR.FP=1 MSR.VEC=0: FP ok VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC corrupted! high = 0 low = 0
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
Checking if FP/VEC registers are sane after a VEC unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP corrupted! high = 0 low = 0 VEC ok
If MSR.FP=1 MSR.VEC=0: FP corrupted! high = 0x2000 low = 0 VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC ok
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
Checking if FP/VEC registers are sane after a VSX unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP ok VEC ok
If MSR.FP=1 MSR.VEC=0: FP corrupted! high = 0x2000 low = 0 VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC corrupted! high = 0 low = 0
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
result: failed!
failure: tm_unavailable_test
not ok 1..10 selftests: tm-unavailable [FAIL]
selftests: tm-trap
========================================

where as tm_trap is a PASS...

------- Comment From <email address hidden> 2018-04-26 08:10 EDT-------
(In reply to comment #28)
> Adding to above.. in artful I see a new failure:

Please open a different bug for this one, since this requires a new patch.
> where as tm_trap is a PASS...

Good. Let's consider the artful kernel good at this time and ready to be committed.

Thanks for the quick tests.

------- Comment From <email address hidden> 2018-04-26 08:47 EDT-------
(In reply to comment #29)
> (In reply to comment #28)
> > Adding to above.. in artful I see a new failure:
>
> Please open a different bug for this one, since this requires a new patch.

The possible new patch would be f48e91e87e67b56bef63393d1a02c6e22c1d7078, but we can treat it on this new bug.

ppc64el versions of the Xenial test kernel are now available here:

 http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial

Xenial required the following two prereq commits:
d96f234f47af ("powerpc: Avoid load hit store in setup_sigcontext()")
d11994314b2b ("powerpc: signals: Stop using current in signal code")

------- Comment From <email address hidden> 2018-05-05 10:31 EDT-------
Yesterday, the decision was made at Padma's daily KVM meeting to only track System Firmware Mustfix issues using the LC GA1 Mustfix label since that is all that applies to the Supermicro team. The OS Kernel/KVM issues will be managed with a spreadsheet tracked by the KVM team and also in the internal slack channel. Removing the Mustfix label.

------- Comment From <email address hidden> 2018-05-08 04:22 EDT-------
(In reply to comment #31)
> ppc64el versions of the Xenial test kernel are now available here:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1762928/xenial
>
> Xenial required the following two prereq commits:
> d96f234f47af ("powerpc: Avoid load hit store in setup_sigcontext()")
> d11994314b2b ("powerpc: signals: Stop using current in signal code")

Test results:

selftests: tm-resched-dscr
========================================
test: tm_resched_dscr
tags: git_version:f142f08
Binding to cpu 8
main test running as pid 4949
Check DSCR TM context switch: OK
success: tm_resched_dscr
ok 1..1 selftests: tm-resched-dscr [PASS]
selftests: tm-syscall
========================================
test: tm_syscall
tags: git_version:f142f08
Testing transactional syscalls for 10 seconds...
5799695 active and suspended transactions behaved correctly.
(There were 1666 transaction retries.)
success: tm_syscall
ok 1..2 selftests: tm-syscall [PASS]
selftests: tm-signal-msr-resv
========================================
test: tm_signal_msr_resv
tags: git_version:f142f08
success: tm_signal_msr_resv
ok 1..3 selftests: tm-signal-msr-resv [PASS]
selftests: tm-signal-stack
========================================
test: tm_signal_stack
tags: git_version:f142f08
success: tm_signal_stack
ok 1..4 selftests: tm-signal-stack [PASS]
selftests: tm-vmxcopy
========================================
test: tm_vmxcopy
tags: git_version:f142f08
success: tm_vmxcopy
ok 1..5 selftests: tm-vmxcopy [PASS]
selftests: tm-fork
========================================
test: tm_fork
tags: git_version:f142f08
success: tm_fork
ok 1..6 selftests: tm-fork [PASS]
selftests: tm-tar
========================================
Starting, 10000 loops
test: tm_tar
tags: git_version:f142f08
success: tm_tar
ok 1..7 selftests: tm-tar [PASS]
selftests: tm-tmspr
========================================
test: tm_tmspr
tags: git_version:f142f08
success: tm_tmspr
ok 1..8 selftests: tm-tmspr [PASS]
selftests: tm-vmx-unavail
========================================
test: tm_vmx_unavail_test
tags: git_version:f142f08
success: tm_vmx_unavail_test
ok 1..9 selftests: tm-vmx-unavail [PASS]
selftests: tm-unavailable
========================================
test: tm_unavailable_test
tags: git_version:f142f08
Checking if FP/VEC registers are sane after a FP unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP ok VEC ok
If MSR.FP=1 MSR.VEC=0: FP ok VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC ok
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
Checking if FP/VEC registers are sane after a VEC unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP ok VEC ok
If MSR.FP=1 MSR.VEC=0: FP ok VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC ok
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
Checking if FP/VEC registers are sane after a VSX unavailable exception...
If MSR.FP=0 MSR.VEC=0: FP ok VEC ok
If MSR.FP=1 MSR.VEC=0: FP ok VEC ok
If MSR.FP=0 MSR.VEC=1: FP ok VEC ok
If MSR.FP=1 MSR.VEC=1: FP ok VEC ok
result: success
success: tm_unavailable_test
ok 1..10 selftests: tm-unavailable [PASS]
selftests: tm-trap
========================================
test: tm_trap_test
tags: git_version:f142f08
Little-Endian ma...

------- Comment From <email address hidden> 2018-05-10 11:57 EDT-------
Ok, let's consider this problem fixed for now, and we can open another bug for the different problem, which will require a different patch.

------- Comment From <email address hidden> 2018-05-15 14:03 EDT-------
This next problem was created as https://bugzilla.linux.ibm.com/show_bug.cgi?id=167739 and there is already a fix for it. Closing this problem, and tracking the other fix in bug#167739.