This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
yakkety' to 'verification-done-yakkety'. If the problem still exists,
change the tag 'verification-needed-yakkety' to 'verification-failed-

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See for documentation how
to enable and use -proposed. Thank you!

** Tags added: verification-needed-yakkety

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  Kernel: Fix Transactional memory config typo

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Yakkety:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:

  Please include the following fix on 16.10.  This typo is causing some issue 
on TM.
  The patches that causes this problem is 
ec2a04841b785373a6379af66032201a2b90922b on yakkety-ubuntu repo.

  commit 39715bf972ed4fee18fe5409609a971fb16b1771
  Author: Valentin Rothberg <>
  Date:   Wed Oct 5 07:57:26 2016 +0200

      powerpc/process: Fix CONFIG_ALIVEC typo in restore_tm_state()
      It should be ALTIVEC, not ALIVEC.
      Cyril explains: If a thread performs a transaction with altivec and then
      gets preempted for whatever reason, this bug may cause the kernel to not
      re-enable altivec when that thread runs again. This will result in an
      altivec unavailable fault, when that fault happens inside a user
      transaction the kernel has no choice but to enable altivec and doom the
      The result is that transactions using altivec may get aborted more often
      than they should.
      The difficulty in catching this with a selftest is my deliberate use of
      the word may above. Optimisations to avoid FPU/altivec/VSX faults mean
      that the kernel will always leave them on for 255 switches. This code
      prevents the kernel turning it off if it got to the 256th switch (and
      userspace was transactional).
      Fixes: dc16b553c949 ("powerpc: Always restore FPU/VEC/VSX if hardware 
transactional memory in use")
      Reviewed-by: Cyril Bur <>
      Signed-off-by: Valentin Rothberg <>
      Signed-off-by: Michael Ellerman <>

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to