https://bugs.freedesktop.org/show_bug.cgi?id=101262
Bug ID: 101262 Summary: Mesa reports no Video Memory Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: noonetinone@gmail.com QA Contact: dri-devel@lists.freedesktop.org
When trying to run Dying Light. It seg faults. I compiled Mesa-git well past the patches written by Brooks. Plus, I am using the overrides. In common/Dying Light/DW/out/logs/ there are some logs to examine.
I see this:
{21:54:20.616} INFO: [INFO] > [OpenGL] Video memory detected: 0 [MB]! {21:54:20.620} INFO: [INFO] > Caught signal 11 (Segmentation fault). {21:54:20.622} INFO: [INFO] > /lib64/libc.so.6(+0x336e0) [0x7f2472ceb6e0] {21:54:20.622} INFO: [INFO] | /lib64/libpthread.so.0(pthread_join+0x1e) [0x7f247a2d06de] {21:54:20.622} INFO: [INFO] | /usr/lib64/dri/radeonsi_dri.so(+0x303b90) [0x7f24674fbb90] {21:54:20.622} INFO: [INFO] | /usr/lib64/dri/radeonsi_dri.so(+0x303be8) [0x7f24674fbbe8]
I have 4 gig's on my card. All other native linux games run fine.
https://bugs.freedesktop.org/show_bug.cgi?id=101262
Anthony Jagers noonetinone@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #1 from Anthony Jagers noonetinone@gmail.com --- I have new information.
My current OS is Linux from Scratch. I tried Dying Light in Ubuntu and it works. The log still show no video memory. So, that is not the problem.
The only thing different in Ubuntu's logs is the reported pciids for the video card. Right after the seg fault in the logs my target OS give the line:
GPU's vendor id: 1 [0x0001]; GPU's device id: 2 [0x0002]. instead of [0x1002:0x67ef].
Those are incorrectly filled. But nvidia closed drivers reports the same thing. So that isn't the problem.
______________________________________
At the steam console with mesa debugging turned on I get some interesting lines.
Steam: An X Error occurred X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 40 (X_TranslateCoords) Resource id in failed request: 0x1000fce Serial number of failed request: 25757 xerror_handler: X failed, continuing . . . Mesa: User error: GL_INVALID_OPERATION in unsupported function called (unsupported extension or deprecated function?) Mesa: 4 similar GL_INVALID_OPERATION errors Mesa: User error: GL_INVALID_ENUM in glEnable(GL_TEXTURE_2D) Mesa: User error: GL_INVALID_ENUM in glDisable(GL_TEXTURE_2D)
https://bugs.freedesktop.org/show_bug.cgi?id=101262
Anthony Jagers noonetinone@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Mesa reports no Video |Need help in running Dying |Memory |Light
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #2 from Anthony Jagers noonetinone@gmail.com --- My guess is I need help in tracing this. How would you trace a steam game?
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #3 from Emil Velikov emil.l.velikov@gmail.com --- (In reply to Anthony Jagers from comment #2)
My guess is I need help in tracing this. How would you trace a steam game?
See https://wiki.archlinux.org/index.php/Steam/Troubleshooting#Debugging_Steam
No idea which extension the game uses, so it may be that Mesa does not implement it.
IIRC only GLX_MESA_query_renderer is done - see the output of glxinfo. You'll get something like
Extended renderer info (GLX_MESA_query_renderer): Vendor: Intel Open Source Technology Center (0x8086) Device: Mesa DRI Intel(R) HD Graphics 5500 (Broadwell GT2) (0x1616) Version: 17.0.7 Accelerated: yes Video memory: 3072MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 3.0 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #4 from Anthony Jagers noonetinone@gmail.com --- Whatever the problem is, it is clearly not a mesa bug. It seems only lesser used distros are having problems. Gentoo and LFS are the ones.
I'm closing this.
https://bugs.freedesktop.org/show_bug.cgi?id=101262
Anthony Jagers noonetinone@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Priority|medium |lowest Resolution|--- |NOTOURBUG Severity|normal |trivial Status|NEEDINFO |RESOLVED
--- Comment #5 from Anthony Jagers noonetinone@gmail.com --- Closed
https://bugs.freedesktop.org/show_bug.cgi?id=101262
--- Comment #6 from Mariusz Ceier mceier+freedesktop@gmail.com --- That bug is due to missing /usr/bin/lspci. Dying Light tries to execve /usr/bin/lspci in a fork and when it fails it calls exit function instead of _exit.
exit calls exit handler registered by mesa which causes the segmentation fault and 'hangup' of Dying Light. I have reported this bug to the developers on 10th May 2018.
Additional info that some people might find useful:
a) Dying Light requires haptic support in SDL, otherwise it shows uninformative dialog and exits.
b) Dying Light requires OpenGL 4.4 (according to devs) and uses glew to detect OpenGL version which parses GL version string. Since mesa returns OpenGL version 3.0~3.1 for GL contexts created by glew, override variables have to be used to run Dying Light, e.g.:
MESA_GL_VERSION_OVERRIDE=4.4 MESA_GLSL_VERSION_OVERRIDE=440 %command%
in launch options in steam.
Sorry for commenting inside "resolved" bug.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org