https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c1 --- Comment #1 from Richard Biener 2013-12-03 09:00:37 UTC --- *** Bug 853312 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=853312 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c3 --- Comment #3 from Michael Matz 2013-12-09 13:56:07 UTC --- (In reply to comment #2)

Unlocking a non-locked lock is never tolerated.

It is in the sense that the applications in question don't segfault and don't see other adverse effects. For application we (or anyone else) can change I agree that they should be fixed (like libusb). But we're talking about stuff that nobody is going to change anymore, and we do need a work around for those to keep them working. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c5 --- Comment #5 from Michael Matz 2013-12-09 15:49:36 UTC --- (In reply to comment #4)

Unlocking a non-locked lock has always had adverse effects.

But unfortunately only theoretical ones in some cases. For a user the (unchangeable) application "worked" before, with new glibc on Haswells it crashes right away. That is a problem which we can't define away by being right in the abstract. Rather we should provide a method to transform the crashing application back into a halfway (or barely, or sometimes, or whatever other definition of not quite, but better than crashing) working one. Patches to that effect (environment variable influence TSX unlock crashes) were even implemented by Andi but never upstreamed. OTOH it'd probably be better to just disable all the TSX stuff via a envvar disabling detection of TSX. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c7 --- Comment #7 from Michael Matz 2013-12-09 16:34:14 UTC --- That is correct. But that must not hinder us in providing a good quality of implementation also for broken apps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c9 --- Comment #9 from Andreas Schwab 2014-03-03 16:25:42 CET --- How does TSX relate to RTM/HLE? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c11 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |schwab@suse.com --- Comment #11 from Richard Biener 2014-06-26 09:14:29 UTC --- I belive this may have been addressed by Thu May 15 15:45:03 UTC 2014 - schwab@suse.de - add non-elision-enabled libpthread which looks like it needs LD_LIRBARY_PATH=/lib64/noelision:$LD_LIBRARY_PATH for affected broken programs. Maybe Andreas can clarify (and close this bug if fixed, eventually adding a bnc reference to .changes for the next update). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c13 --- Comment #13 from Holger Sickenberg 2014-06-26 11:29:33 CEST --- I can confirm that novell-groupwise-client-8.0.2HP4-102299.i586 is working with package http://download.opensuse.org/factory/repo/oss/suse/x86_64/glibc-32bit-2.19-9... and change in /opt/novell/groupwise/client/bin/groupwise export LD_LIBRARY_PATH=/opt/novell/groupwise/client/lib:/opt/novell/groupwise/client/java/lib/i386 to export LD_LIBRARY_PATH=/lib/noelision:/opt/novell/groupwise/client/lib:/opt/novell/groupwise/client/java/lib/i386 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=853311 https://bugzilla.novell.com/show_bug.cgi?id=853311#c15 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #15 from Andreas Schwab 2014-09-10 09:46:49 CEST --- Fixed by chip errata. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.