| 2016-03-30 23:38:54 |
Jason Gerard DeRose |
bug |
|
|
added bug |
| 2016-03-30 23:51:38 |
Jason Gerard DeRose |
description |
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This certainly effects hardware with NVIDIA 970m and 980m GPUs, and possibly others.
In the current state, it's not possible to install Xenial on such hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
|
| 2016-03-30 23:52:02 |
Jason Gerard DeRose |
bug task added |
|
system76 |
|
| 2016-03-30 23:54:56 |
Jason Gerard DeRose |
system76: status |
New |
Triaged |
|
| 2016-03-30 23:54:59 |
Jason Gerard DeRose |
system76: assignee |
|
Jason Gerard DeRose (jderose) |
|
| 2016-03-30 23:55:03 |
Jason Gerard DeRose |
system76: importance |
Undecided |
Critical |
|
| 2016-03-31 00:14:26 |
Jason Gerard DeRose |
description |
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
|
| 2016-04-08 22:09:53 |
Timo Aaltonen |
affects |
compiz (Ubuntu) |
mesa (Ubuntu) |
|
| 2016-04-14 07:51:44 |
Chih-Hsyuan Ho |
bug task added |
|
mesa |
|
| 2016-04-14 07:52:01 |
Chih-Hsyuan Ho |
affects |
mesa (Ubuntu) |
oem-priority |
|
| 2016-04-14 07:52:15 |
Chih-Hsyuan Ho |
bug |
|
|
added subscriber OEM Priority Team |
| 2016-04-14 10:41:16 |
Chen-Han Hsiao (Stanley) |
bug |
|
|
added subscriber Chen-Han Hsiao (Stanley) |
| 2016-04-19 22:54:15 |
Jason Gerard DeRose |
description |
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs.
The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved.
I have mesa test packages built against llvm 3.6 here:
https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages
I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well.
My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix.
Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug.
For concrete examples of System76 hardware effected by this:
1) All Skylake laptops with 970m, 980m, and 980gtx GPUs
2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort)
Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations.
In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg).
Also note that so far I've only tested amd64, haven't tested i386.
I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu.
Old description
===============
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
|
| 2016-04-20 02:15:09 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2016-04-20 04:37:58 |
Timo Aaltonen |
bug task deleted |
mesa |
|
|
| 2016-04-20 04:38:06 |
Timo Aaltonen |
bug task added |
|
mesa (Ubuntu) |
|
| 2016-04-20 04:38:17 |
Timo Aaltonen |
bug task added |
|
llvm-toolchain-3.8 (Ubuntu) |
|
| 2016-04-20 13:06:50 |
Timo Aaltonen |
llvm-toolchain-3.8 (Ubuntu): status |
New |
In Progress |
|
| 2016-04-20 13:06:50 |
Timo Aaltonen |
llvm-toolchain-3.8 (Ubuntu): assignee |
|
Timo Aaltonen (tjaalton) |
|
| 2016-04-20 15:30:29 |
Ian Santopietro |
attachment added |
|
cpuinfo-leox.txt https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640786/+files/cpuinfo-leox.txt |
|
| 2016-04-20 15:30:52 |
Ian Santopietro |
attachment added |
|
cpuinfo-silw.txt https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640787/+files/cpuinfo-silw.txt |
|
| 2016-04-21 14:05:06 |
Martin Pitt |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-04-21 14:05:06 |
Martin Pitt |
bug task added |
|
mesa (Ubuntu Xenial) |
|
| 2016-04-21 14:05:06 |
Martin Pitt |
bug task added |
|
llvm-toolchain-3.8 (Ubuntu Xenial) |
|
| 2016-04-21 14:06:35 |
Martin Pitt |
llvm-toolchain-3.8 (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-04-21 14:06:37 |
Martin Pitt |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-04-21 14:06:38 |
Martin Pitt |
bug |
|
|
added subscriber SRU Verification |
| 2016-04-21 14:06:47 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2016-04-21 19:07:07 |
Jason Gerard DeRose |
system76: status |
Triaged |
Fix Committed |
|
| 2016-04-21 19:08:35 |
Jason Gerard DeRose |
tags |
verification-needed |
verification-done |
|
| 2016-04-21 19:40:07 |
Jason Gerard DeRose |
description |
Currently it's impossible to install from xenial-desktop-amd64.iso on a wide range of hardware with Nvidia GPUs.
The problem is invalid opcode(s) when using llvmpipe (the software opengl fallback, used when using Unity with the Nouveau driver). The result is that compiz crashes over and over; Upstart will continue to restart compiz till it gives up. To confirm whether this bug is happening, switch to a VT and check dmesg, in which you'll see something like:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
A workable solution seems to be to re-build mesa against llvm-3.6-dev, libclang-3.6-dev (rather that 3.8). This would get us a working Xenial ISO for the effected hardware. Post 16.04 release, this could be revisited, and mesa in Xenial could possibly switch back to llvm 3.8 once this issue is resolved.
I have mesa test packages built against llvm 3.6 here:
https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages
I couldn't test the installation without a re-spun ISO, but I did confirm that after updating to the mesa packages in my PPA, I could again use Unity. So I'm pretty sure this will fix installing from the ISO as well.
My hunch is that llvm 3.8 is generating invalid code during its JIT compilation for llvmpipe, but it could also be the result of memory corruption. Either way, building mesa against llvm 3.6 seems to be quick the fix.
Note this is a regression from 14.04.4 and 15.10, both of which install fine on the hardware effected by this bug.
For concrete examples of System76 hardware effected by this:
1) All Skylake laptops with 970m, 980m, and 980gtx GPUs
2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs (although strangely, things seem to work with when you connect to a monitor over HDMI, but always fails when connecting to a monitor over DisplayPort)
Note that none of the above failed tested scenarios are using Optimus: all are using discrete GPU configurations.
In my testing thus far on the effected hardware, the install always fails if you choose "Try Ubuntu without installing". The install usually seems to work when you choose "Install Ubuntu", but even this 2nd scenario sometimes fails (and when it does, you'll see the same "trap invalid opcode" bits in dmesg).
Also note that so far I've only tested amd64, haven't tested i386.
I suspect there is some deeper weirdness here, but at this point System76 is just trying to make sure we have a Xenial ISO from which customers can re-install Ubuntu.
Old description
===============
Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware.
For example, from dmesg:
[ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0
[ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0
[ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0
This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well.
Although strangely, with some NVIDIA 900 series hardware we're not seeing this bug when using the nouveau driver. This will be investigated further.
In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs.
Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable:
(1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems.
(2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem.
I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me.
Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :)
Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support:
/usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log
That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). |
[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. |
|
| 2016-04-22 06:33:02 |
Mathew Hodson |
bug task added |
|
ubuntu-release-notes |
|
| 2016-04-22 06:33:13 |
Mathew Hodson |
ubuntu-release-notes: status |
New |
Fix Released |
|
| 2016-04-22 08:51:56 |
Ara Pulido |
oem-priority: status |
New |
Fix Committed |
|
| 2016-04-22 11:58:48 |
Launchpad Janitor |
llvm-toolchain-3.8 (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2016-04-23 04:46:29 |
Launchpad Janitor |
mesa (Ubuntu): status |
New |
Confirmed |
|
| 2016-04-23 04:46:29 |
Launchpad Janitor |
mesa (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2016-04-24 02:03:51 |
Srecko Toroman |
bug |
|
|
added subscriber Srecko Toroman |
| 2016-04-24 03:52:36 |
Mathew Hodson |
llvm-toolchain-3.8 (Ubuntu): importance |
Undecided |
Critical |
|
| 2016-04-24 03:52:38 |
Mathew Hodson |
llvm-toolchain-3.8 (Ubuntu Xenial): importance |
Undecided |
Critical |
|
| 2016-04-24 21:09:53 |
Launchpad Janitor |
llvm-toolchain-3.8 (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-04-24 21:10:00 |
Adam Conrad |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2016-04-24 22:20:58 |
Jason Gerard DeRose |
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. |
[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"
== 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 ISOs. It will be included on the 16.04.1 ISOs. |
|
| 2016-04-24 22:21:05 |
Jason Gerard DeRose |
system76: status |
Fix Committed |
Fix Released |
|
| 2016-04-25 15:17:28 |
Jason Gerard DeRose |
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"
== 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 ISOs. It will be included on the 16.04.1 ISOs. |
[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"
== In detail ==
The Ubuntu 16.04 desktop ISOs include 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 ISOs. It will be included on the 16.04.1 ISOs. |
|
| 2016-04-25 17:33:27 |
Jason Gerard DeRose |
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"
== In detail ==
The Ubuntu 16.04 desktop ISOs include 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 ISOs. It will be included on the 16.04.1 ISOs. |
[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: "Download updates while installing Ubuntu" doesn't currently seem to be working. If after installing 16.04 on effected Skylake hardware you find that Unity/Compiz is broken, switch to a VT with Control+Alt+F1, login, and then run:
sudo apt-get update
sudo apt-get dist-upgrade
You should see the `libllvm3.8` package get updated. After a reboot, Unity/Compiz should be working.
== In detail ==
The Ubuntu 16.04 desktop ISOs include 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 ISOs. It will be included on the 16.04.1 ISOs. |
|
| 2016-04-26 06:57:11 |
Abhinav Upadhyay |
bug |
|
|
added subscriber Abhinav Upadhyay |
| 2016-04-29 07:25:31 |
Yufei |
bug |
|
|
added subscriber Yufei |
| 2016-05-17 13:31:19 |
Ara Pulido |
oem-priority: status |
Fix Committed |
Fix Released |
|
| 2016-05-21 22:37:57 |
Andres |
bug |
|
|
added subscriber Andres |
| 2016-11-09 19:41:17 |
System76 |
bug |
|
|
added subscriber System76 |
| 2016-11-09 22:57:44 |
System76 |
mesa (Ubuntu Xenial): status |
Confirmed |
Invalid |
|
| 2016-11-09 22:57:51 |
System76 |
mesa (Ubuntu): status |
Confirmed |
Invalid |
|
| 2017-04-26 01:43:28 |
Mathew Hodson |
bug task deleted |
mesa (Ubuntu Xenial) |
|
|
| 2017-04-26 01:43:35 |
Mathew Hodson |
bug task deleted |
mesa (Ubuntu) |
|
|
