[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-11-25 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 19.2.4-1ubuntu1 --- mesa (19.2.4-1ubuntu1) focal; urgency=medium * Merge from Debian. * revert-set-full-thread-affinity.diff: Dropped, qemu is fixed now in eoan and up. (LP: #1815889) -- Timo Aaltonen Wed, 20 Nov 2019 20:17:00

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-10-28 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu Eoan) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-10-21 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu) Status: Triaged => In Progress ** Changed in: mesa (Ubuntu) Milestone: ubuntu-19.04 => None -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title:

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-10-21 Thread Timo Aaltonen
I believe this was fixed by qemu 4.0 in eoan. ** Changed in: qemu (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title:

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-05-07 Thread Sebastien Bacher
Reopening/Assigning to TImo for eoan since there is a patch which can we dropped once qemu is fixed ** Changed in: mesa (Ubuntu Eoan) Status: Fix Released => Triaged ** Changed in: mesa (Ubuntu Eoan) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-05-07 Thread Sebastien Bacher
** Changed in: mesa (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-04-24 Thread Thomas Huth
** Changed in: qemu Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-04-13 Thread Bug Watch Updater
** Changed in: mesa Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-04-03 Thread Christian Ehrhardt 
Thank you Daniel, we will most likely keep Disco as-is for now and merge this in 19.10 where then mesa can drop the revert. I tagged it for 19.10 to be revisited. ** Tags added: qemu-19.10 ** Also affects: mesa (Ubuntu Ee-series) Importance: Undecided Status: New ** Also affects:

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-04-02 Thread Daniel Berrange
FYI the QEMU change merged in the following pull request changed to return an EPERM errno for the thread affinity syscalls: commit 12f067cc14b90aef60b2b7d03e1df74cc50a0459 Merge: 84bdc58c06 035121d23a Author: Peter Maydell Date: Thu Mar 28 12:04:52 2019 + Merge remote-tracking branch

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-15 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 19.0.0-1ubuntu1 --- mesa (19.0.0-1ubuntu1) disco; urgency=medium * Merge from Debian. (LP: #1818516) * revert-set-full-thread-affinity.diff: Fix qemu crash. (LP: #1815889) -- Timo Aaltonen Thu, 14 Mar 2019 18:48:18 +0200 ** Changed

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Christian Ehrhardt 
The PPA was built against -proposed so I had to enable that to install all libs. That done the 19.0.0~rc6-1ubuntu0.1 with the set affinity change reverted works quite nicely. It would be great to get that into Ubuntu 19.04 until the involved upstreams agreed how to proceed with it and we can

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Timo Aaltonen
I don't have that issue on a chroot, so you should at least tell me why it would refuse to upgrade them all.. apt should show an error -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Christian Ehrhardt 
Hi Timo, I tried to test with the mesa from ppa:canonical-x/x-staging But there is a dependency issue in that PPA - I can't install all packages from there. It seems most of the X* packages will need a transition for the new mesa and those are not in this ppa right now. Installing all that I

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Timo Aaltonen
You can test 19.0~rc6 with this reverted on a ppa: ppa:canonical-x/x-staging should be built in 30min -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Christian Ehrhardt 
** Also affects: mesa (Ubuntu Disco) Importance: Medium Status: Confirmed ** Also affects: qemu (Ubuntu Disco) Importance: Undecided Status: Triaged ** No longer affects: qemu (Ubuntu Disco) ** Changed in: mesa (Ubuntu Disco) Status: Confirmed => Triaged ** Changed

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-03-04 Thread Timo Aaltonen
** Changed in: mesa (Ubuntu) Importance: Undecided => Medium ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title:

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-02-28 Thread Bug Watch Updater
Launchpad has imported 9 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=109695. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-02-28 Thread Will Cooke
Adding Timo who maintainers mesa. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() To manage

[Ubuntu-x-swat] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-02-28 Thread Christian Ehrhardt 
Thanks Daniel and MarcAndre for chiming in here. Atfer thinking more about it I agree to Daniel that actually mesa should honor and stick with its affinity assignment. For documentation purpose: the solution proposed on the ML is at