Bug#800574: Bug#807244: libegl1-nvidia: Programs crash due to elisian-unlock on skylake processor with nvidia driver 352.63-1 (experimental)
On 2015-12-08 22:30, Jelle Haandrikman wrote:
> Hi Andreas,
>
> On 2015-12-08 19:25, Andreas Beckmann wrote:
> >Hi Aurelien,
> >
> >... buggy software (#807244), which is only exposed by running on
> >hardware with working TSX-NI.
> >That could also explain the fact that the bug was introduced in 352+.
> >
> >Jelle, I didn't dig through the nvidia forums, but if this info isn't
> >mentioned there already, maybe you could post it:
> >
> >>According to the backtrace the problem is typical of a call to
> >>mutex_unlock() on a mutex which hasn't been locked with mutex_lock()
> >>before.
> >(or was already unlocked.)
> I'm not a member of any of any Nvidia forum. I'm more of an advanced
> Debian user, with a technical background as a tester. All the searches that
> I
> just did regarding mutex_unlock() and the driver point back to this post.
>
> You really are doing the best anaylysis I had found. Unfortunately it's also
> the only one I can find.
As often this can be also found on the archlinux bug tracking system:
https://bugs.archlinux.org/task/46064?project=1
There is even a link to an ugly patch showing that the issue has been
understood. Finally according to the last post in this bug entry it
seems that nvidia is about to release fix.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: