[Nouveau] [Bug 104728] New: [possible regression] VMD crashes on startup on GT 640 / GK107 / NVE7

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Jan 22 12:46:33 UTC 2018 

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

            Bug ID: 104728
           Summary: [possible regression] VMD crashes on startup on GT 640
                    / GK107 / NVE7
           Product: Mesa
           Version: 17.2
          Hardware: All
                OS: All
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/DRI/nouveau
          Assignee: nouveau at lists.freedesktop.org
          Reporter: vedran at miletic.net
        QA Contact: nouveau at lists.freedesktop.org

Created attachment 136893
  --> https://bugs.freedesktop.org/attachment.cgi?id=136893&action=edit
Apitrace

I'm using

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GK107 [GeForce GT
640] [10de:0fc1] (rev a1)

OpenGL vendor string: nouveau
OpenGL renderer string: NVE7
OpenGL core profile version string: 4.3 (Core Profile) Mesa 17.2.4
OpenGL core profile shading language version string: 4.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

on Fedora 27 with kernel 4.14.13 and Mesa 17.2.4 (I also tried what follows
with 17.3.0rc3 pulled from rawhide, made no change). When running VMD 1.9.3
[1], I get:

apitrace: loaded into /usr/bin/apitrace
apitrace: unloaded from /usr/bin/apitrace
apitrace: loaded into /usr/bin/tcsh
apitrace: loaded into /usr/bin/id
apitrace: unloaded from /usr/bin/id
apitrace: loaded into /usr/bin/id
apitrace: unloaded from /usr/bin/id
apitrace: loaded into /usr/bin/uname
apitrace: unloaded from /usr/bin/uname
apitrace: loaded into /usr/bin/uname
apitrace: unloaded from /usr/bin/uname
apitrace: loaded into /usr/bin/uname
apitrace: unloaded from /usr/bin/uname
apitrace: loaded into /usr/bin/uname
apitrace: unloaded from /usr/bin/uname
apitrace: loaded into /usr/bin/uname
apitrace: unloaded from /usr/bin/uname
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: /lib64/libGL.so.1: no version
information available (required by
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64)
apitrace: loaded into /sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64
apitrace: tracing to /home/miletivn/vmd_LINUXAMD64.trace
apitrace: attempting to read configuration file:
/home/miletivn/.config/apitrace/gltrace.conf
apitrace: warning: caught signal 11
apitrace: flushing trace due to an exception
/usr/bin/../lib64/apitrace/wrappers/glxtrace.so+0x222f6c
/lib64/libpthread.so.0+0x12a7f
/lib64/libX11.so.6: XGetICValues+0x72
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tk_HandleEvent+0x1ea
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x75f2dd
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d6f63
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclEvalObjEx+0x1a2
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7fad60
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_FSEvalFileEx+0x150
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x79fa99
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_EvalObjv+0x47
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclEvalObjEx+0x315
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7fad60
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclObjInterpProcCore+0x3f6
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclObjInterpProcCore+0x3f6
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ec34
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_FSEvalFileEx+0x150
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x79fa99
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8084b0
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_PkgRequireProc+0x8
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8091fa
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8084b0
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_PkgRequireProc+0x8
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8092a9
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d6f63
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclEvalObjEx+0x1a2
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7fad60
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_FSEvalFileEx+0x150
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x79fa99
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ffcc
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8084b0
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_PkgRequireProc+0x8
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x8092a9
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclObjInterpProcCore+0x3f6
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclObjInterpProcCore+0x3f6
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x78ed86
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d1045
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0x7d6f63
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: TclEvalObjEx+0x1a2
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_RecordAndEvalObj+0x1ab
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: Tcl_RecordAndEval+0x44
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64:
_ZN13TclTextInterp10evalStringEPKc+0xf
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64:
_ZN6UIText14act_on_commandEiP7Command+0x5f
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64:
_ZN12CommandQueue10runcommandEP7Command+0xb8
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: _Z14VMDreadStartupP6VMDApp+0x27c
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64: main+0xdc
/lib64/libc.so.6: __libc_start_main+0xe9
/sw/mbm/app/vmd/1.9.3/lib/vmd/vmd_LINUXAMD64+0xe7378
apitrace: info: taking default action for signal 11
Segmentation fault (core dumped)

Apitrace of the run is attached. This doesn't happen with the proprietary
driver, and I can't confirm it's a regression, but there appear to be reports
of VMD working on nouveau (albeit slowly).

[1] http://www.ks.uiuc.edu/Research/vmd/

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/nouveau/attachments/20180122/acc0fb30/attachment.html>

More information about the Nouveau mailing list