** No longer affects: mesa (Ubuntu Xenial)
** No longer affects: mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opcode when using llvmpipe
To manage not
** Changed in: mesa (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
On a whim, I just checked in on this with the 20160601 Xenial daily
amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and
everything works great:
http://cdimages.ubuntu.com/xenial/daily-live/pending/
So seems things are on track for this not being a problem in the 16.04.1
release.
--
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opcode when using llvmpipe
To manage notificati
Okay, seems that "Download updates while installing" has no effect with
the Ubiquity version on the 16.04 ISOs.
I filed a bug against Ubiquity for this, would appreciate if someone
could confirm my findings:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232
--
You received this bu
Jason, I checked the sha256 sum of the ISO. It is correct. I also tried
setting nomodeset in the live USB and then booting. It didn't hang then
but nothing really happened, it didn't start the installation. I could
see the screen and move the mouse around but no option to start the
installation.
I
Unfortunately, this broke my installation completely. Chroot-ing into
the broken installation and running the updates fixed my problem. Here's
the walk-through if anyone is still stuck:
https://toroman.wordpress.com/2016/04/26/getting-out-of-a-broken-
ubuntu-16-04-system-after-an-upgrade/
--
You
** Description changed:
[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
Hmm, I just tried this on Skylake hardware, and "Download updates while
installing" isn't doing the trick.
Could be that "Download updates while installing" is broken on the 16.04
ISOs, or this could be a result of the phased updates done by the Ubuntu
Software Updater and related components that
** Description changed:
[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
Abhinav,
Sounds like you're encountering a different bug, or perhaps your ISO
file is corrupted. Have you verified the checksum of your download?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
I am trying to boot from a 16.04 live USB and it is hanging up when I
say "Install Ubuntu" or "Try Ubuntu without installing". Will there be a
new ISO released with the fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
** Description changed:
[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
This bug was fixed in the package llvm-toolchain-3.8 - 1:3.8-2ubuntu3
---
llvm-toolchain-3.8 (1:3.8-2ubuntu3) xenial; urgency=medium
* rules: Allow LLVM tests to fail on i386, we know dropping AVX512 breaks
them.
llvm-toolchain-3.8 (1:3.8-2ubuntu2) xenial; urgency=medium
* d
HI!
Would this bug cause my system to crash when using an external monitor
via HDMI? I can attach and use the monitor no problem UNTIL I suspend
and/or detach and reattach the monitor, in which case the whole system
crashes i.e.) screen freezes, keyboard, touchpad and network are all
unresponsive
** Changed in: llvm-toolchain-3.8 (Ubuntu)
Importance: Undecided => Critical
** Changed in: llvm-toolchain-3.8 (Ubuntu Xenial)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Thank you Joakim!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opcode when using llvmpipe
To manage notifications about this bug go to:
https://bugs.launchpad.net/oe
Joel, I did this:
boot with nomodeset (press E after grub is booted and add nomodeset
after: quiet splash and press F10 (if I remember correctly) now change
to a terminal with CTRL + ALT + F2 or something.
wget
http://koti.kapsi.fi/~tjaalton/skl/build2/libllvm3.8_3.8-2ubuntu1.1_amd64.deb
sudo dp
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenia
Any chance on providing more instructions on how to resolve?
I thought I had installed the above deb successfully, but it didn't seem
to make a difference. Most likely I've not done something right.
Many thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Also just tried with the .deb from
http://koti.kapsi.fi/~tjaalton/skl/build2 worked perfectly.
To future users: add nomodeset and then use wget to get it and install
it that way. Look me a while to figure out why tty1-6 was not working ;)
--
You received this bug notification because you are a m
This bug was fixed in the package llvm-toolchain-3.8 - 1:3.8-2ubuntu3
---
llvm-toolchain-3.8 (1:3.8-2ubuntu3) xenial; urgency=medium
* rules: Allow LLVM tests to fail on i386, we know dropping AVX512 breaks
them.
llvm-toolchain-3.8 (1:3.8-2ubuntu2) xenial; urgency=medium
* d
** Changed in: oem-priority
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opcode when using llvmpipe
To manage notifications about
Hi, glad to see this has been solved. How long till I can find it in
updates? Can I add xenial-proposed during install?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid o
** 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** Description changed:
- Currently it's impossible to install from xenial-desktop-amd64.iso on a
- wide range of hardware with Nvidia GPUs.
+ [Description updated to reflect state of 16.04 release ISO]
- The problem is invalid opcode(s) when using llvmpipe (the software
- opengl fallback, used
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed
fixes this issue on Skylake hardware using llvmpipe.
Thanks!
** Changed in: system76
Status: Triaged => Fix Committed
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug n
Hello Jason, or anyone else affected,
Accepted llvm-toolchain-3.8 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-3.8/1:3.8-2ubuntu3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
After further investigating, it seems this bug doesn't effect Haswell-E
after all, sorry about the confusion.
Will continue to report back as we learn more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I can confirm that tjaalton's above test packages fix the problem on a
Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the
nouveau driver.
I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted,
and now I have working Unity again.
--
You received this bug no
this should be fixed with libllvm3.8 available on
http://koti.kapsi.fi/~tjaalton/skl/build2
which dropped AVX512 and it's subvariants from skylake
but the haswell thing is probably something else..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
Attaching CPU info from two affected Desktop systems.
** Attachment added: "cpuinfo-leox.txt"
https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640786/+files/cpuinfo-leox.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Second affected system
** Attachment added: "cpuinfo-silw.txt"
https://bugs.launchpad.net/oem-priority/+bug/1564156/+attachment/4640787/+files/cpuinfo-silw.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
just dropping AVX512 didn't fix skylake, but looking at current
lib/Target/X86/X86.td there are several features getting enabled which
are separated in 3.9 to apply only to server CPU's
** Changed in: llvm-toolchain-3.8 (Ubuntu)
Status: New => In Progress
** Changed in: llvm-toolchain-3.8
similar segfaults happen with mesa llvmpipe tests when built on skylake,
but not with llvm-3.9 snapshot. So the issue is with detecting skylake
features, I'll try disabling AVX512 from llvm if that works around this
issue.
It doesn't explain failure on HSW-E though, maybe it's trying to enable
ano
this happens with 11.1.x + llvm-3.8 too, so the bug should be in llvm as
any mesa bisect attempt hasn't helped
** No longer affects: mesa
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Also affects: llvm-toolchain-3.8 (Ubuntu)
Importance: Undecided
Status
** Also affects: mesa
Importance: Undecided
Status: New
** Package changed: mesa (Ubuntu) => oem-priority
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1564156
Title:
xenial: invalid opco
Oh, and another bit of information: our laptops all use embedded Display
Port for their connection to the internal screen, and in this case, this
bug always manifests.
So at least in our testing so far, both eDP and DP seem to be effected.
--
You received this bug notification because you are a
So there seems to be a curious pattern with this bug (which might
provide an important hint): on desktop systems with 970 GTX or 980 GTX
cards, this bug always seems to happen when connected to a monitor over
DisplayPort, but does *not* seem to happen when connected to a monitor
over HDMI.
We'll i
moving to mesa until it's better known, might be triggered by llvm 3.8
and related to bug #1553174
** Package changed: compiz (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/15
** Description changed:
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: c
** Description changed:
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: c
43 matches
Mail list logo
