group.of.nepali.translators team mailing list archive
-
group.of.nepali.translators team
-
Mailing list archive
-
Message #02073
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opcode when using llvmpipe
Status in OEM Priority Project:
New
Status in System76:
Fix Committed
Status in Release Notes for Ubuntu:
Fix Released
Status in llvm-toolchain-3.8 package in Ubuntu:
Fix Committed
Status in mesa package in Ubuntu:
New
Status in llvm-toolchain-3.8 source package in Xenial:
Fix Committed
Status in mesa source package in Xenial:
New
Bug description:
[Description updated to reflect state of 16.04 release ISO]
== In summary ==
If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or
possibly other GPUs that likewise require use of the llvmpipe opengl
software fallback), a work-around is needed to install Ubuntu 16.04
desktop.
To work-around this, you'll need to:
1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try
Ubuntu without installing")
2) Check "Download updates while installing Ubuntu"
** Note the above work-around wont work till
llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens.
== In detail ==
The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1,
which has a bug that results in invalid JIT code generation when using
the mesa llvmpipe opengl software fallback on Skylake CPUs.
When you encounter this bug, Unity/Compiz will fail to start, and
you'll see something like this in dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode
ip:7efc940030d4 sp:7ffccd914ea0 error:0
libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make
it onto the 16.04 release ISO. It will be included on the 16.04.1 ISO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions