dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101881] [regression] 32bit steam games segfault when launched with DRI_PRIME=1
Date: Sat, 29 Jul 2017 14:17:38 +0000	[thread overview]
Message-ID: <bug-101881-502-WlJnof0dP7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101881-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1483 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101881

--- Comment #5 from Rafael Ristovski <rafael.ristovski@gmail.com> ---
I can confirm a very similar issue on my SI Cape Verde (HD8850M GCN1.0) using
the amdgpu driver with mesa. It happens even if I compile mesa's `xdemos` with
-m32 in which case most of the binaries produce a segfault pointing to
drmGetVersion().

Can you confirm the same thing on your end?
Steps to reproduce:

1) Compile xdemos with -m32
2) Load `glthreads` in gdb
3) Switch DRI on inside gdb via 'set environment DRI_prime=1'
4) After you run the program ('r'), and it segfaults, try and see what 'bt'
produces.

For me its the following:

#0  0xf7a9c001 in ?? () from /lib32/libc.so.6
#1  0xf7a9bceb in strdup () from /lib32/libc.so.6
#2  0xf7735c55 in drmGetVersion () from /usr/lib32/libdrm.so.2
#3  0xf71a1acc in amdgpu_winsys_create () from /usr/lib32/dri/radeonsi_dri.so
#4  0xf69152d8 in ?? () from /usr/lib32/dri/radeonsi_dri.so
#5  0xf6de8238 in ?? () from /usr/lib32/dri/radeonsi_dri.so
#6  0xf6de2eb3 in ?? () from /usr/lib32/dri/radeonsi_dri.so
#7  0xf7e0f0c5 in ?? () from /usr/lib32/libGL.so.1
#8  0xf7de040c in ?? () from /usr/lib32/libGL.so.1
#9  0xf7dde789 in glXChooseVisual () from /usr/lib32/libGL.so.1
#10 0x0804a483 in create_window ()
#11 0x0804abe9 in main ()

Note 64bit binaries work flawlessly.
Using gcc 8 alpha here.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2319 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-07-29 16:46 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-23  0:00 [Bug 101881] [regression] 32bit steam games segfault when launched with DRI_PRIME=1 bugzilla-daemon
2017-07-23  0:07 ` bugzilla-daemon
2017-07-23 10:59 ` bugzilla-daemon
2017-07-23 13:08 ` bugzilla-daemon
2017-07-23 22:58 ` bugzilla-daemon
2017-07-29 14:17 ` bugzilla-daemon [this message]
2017-07-29 14:21 ` bugzilla-daemon
2017-07-31  1:55 ` bugzilla-daemon
2017-07-31  7:28 ` bugzilla-daemon
2017-07-31  7:39 ` bugzilla-daemon
2017-07-31  8:13 ` bugzilla-daemon
2017-08-04  6:57 ` bugzilla-daemon
2017-08-04  7:02 ` bugzilla-daemon
2017-08-04  7:20 ` bugzilla-daemon
2017-08-04  7:53 ` bugzilla-daemon
2017-08-08  1:04 ` bugzilla-daemon
2017-08-08  8:42 ` bugzilla-daemon
2017-08-08  9:49 ` bugzilla-daemon
2017-08-08 12:37 ` bugzilla-daemon
2017-08-08 15:08 ` bugzilla-daemon
2017-08-09  7:01 ` bugzilla-daemon
2017-08-09  9:13 ` bugzilla-daemon
2017-08-09 15:48 ` bugzilla-daemon
2017-12-13  1:46 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101881-502-WlJnof0dP7@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox