[Nouveau] [Bug 99396] New: Crash in nouveau_dri.so when switching apps with alt-tab in Gnome
https://bugs.freedesktop.org/show_bug.cgi?id=99396 Bug ID: 99396 Summary: Crash in nouveau_dri.so when switching apps with alt-tab in Gnome Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau@lists.freedesktop.org Reporter: a...@cornell.edu QA Contact: nouveau@lists.freedesktop.org Originally filed as a bug against Gnome (https://bugzilla.gnome.org/show_bug.cgi?id=777183) but they directed me here. Intermittently, gnome-shell will crash with SIGSEGV when switching apps with alt-tab. See stack trace below. Generally when this occurs, I'm running Firefox and Chromium, each with several windows open, and gnome-terminal. I'm not certain, but it seems to only happen when I mouse over the app switcher. I'm running gnome-shell 3.22.2+18+gdf7727a-1 on Arch. Please let me know what other information I can gather! I'll update the bug if I can come up with a reproducible way to trigger the crash. Jan 12 12:37:20 mbp systemd-coredump[8769]: Process 8422 (gnome-shell) of user 1000 dumped core. Stack trace of thread 8422: #0 0x7f63b1771793 __memmove_avx_unaligned_erms (libc.so.6) #1 0x7f639e0baf40 n/a (nouveau_dri.so) #2 0x7f639e1cb008 n/a (nouveau_dri.so) #3 0x7f639e1c0355 n/a (nouveau_dri.so) #4 0x7f639e1c0537 n/a (nouveau_dri.so) #5 0x7f639e1cc3c4 n/a (nouveau_dri.so) #6 0x7f639df1b922 n/a (nouveau_dri.so) #7 0x7f639ddc6690 n/a (nouveau_dri.so) #8 0x7f639dd763b7 n/a (nouveau_dri.so) #9 0x7f639dd7bab5 n/a (nouveau_dri.so) #10 0x7f639dd7c900 n/a (nouveau_dri.so) #11 0x7f639dd005e7 n/a (nouveau_dri.so) #12 0x7f639dd013e0 n/a (nouveau_dri.so) #13 0x7f63af0e44ed n/a (libmutter-cogl.so) #14 0x7f63af0d5b14 n/a (libmutter-cogl.so) #15 0x7f63af10ae56 cogl_texture_allocate (libmutter-cogl.so) #16 0x7f63af12640b n/a (libmutter-cogl.so) #17 0x7f63af126909 cogl_texture_new_from_bitmap (libmutter-cogl.so) #18 0x7f63b277e143 n/a (libmutter-clutter-1.0.so) #19 0x7f63b275a85d clutter_actor_continue_paint (libmutter-clutter-1.0.so) #20 0x7f63b2760aab n/a (libmutter-clutter-1.0.so) #21 0x7f63b463daa0 n/a (libgnome-shell.so) #22 0x7f63b1f26ecf g_closure_invoke (libgobject-2.0.so.0) #23 0x7f63b1f3937d n/a (libgobject-2.0.so.0) #24 0x7f63b1f41bcc g_signal_emit_valist (libgobject-2.0.so.0) #25 0x7f63b1f41faf g_signal_emit (libgobject-2.0.so.0) #26 0x7f63b275a8a3 clutter_actor_continue_paint (libmutter-clutter-1.0.so) #27 0x7f63b2760aab n/a (libmutter-clutter-1.0.so) #28 0x7f63b4647f90 n/a (libgnome-shell.so) #29 0x7f63b1f26ecf g_closure_invoke (libgobject-2.0.so.0) #30 0x7f63b1f3937d n/a (libgobject-2.0.so.0) #31 0x7f63b1f41bcc g_signal_emit_valist (libgobject-2.0.so.0) #32 0x7f63b1f41faf g_signal_emit (libgobject-2.0.so.0) #33 0x7f63b275a8a3 clutter_actor_continue_paint (libmutter-clutter-1.0.so) #34 0x7f63b2760aab n/a (libmutter-clutter-1.0.so) #35 0x7f63b4656182 n/a (libgnome-shell.so) #36 0x7f63b1f26ecf g_closure_invoke (libgobject-2.0.so.0)
[Nouveau] [Bug 99396] Crash in nouveau_dri.so when switching apps with alt-tab in Gnome
https://bugs.freedesktop.org/show_bug.cgi?id=99396 --- Comment #1 from a...@cornell.edu --- I've managed to reproduce the crash fairly consistently by doing the following: 1. Open two Firefox windows on one virtual desktop 2. Open a gnome-terminal window on another desktop 3. Repeatedly alt-tab between Firefox and gnome-terminal. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GP106M+Intel Skylake, Kernel 4.10-rc3 : No display on HDMI or DP
On Thu, Jan 12, 2017 at 3:51 AM, Sylvain Fabre wrote: > xrand > > Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 > eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y > axis) 344mm x 194mm > 1920x1080 60.02*+ 47.99 > 1400x1050 59.98 > 1280x1024 60.02 > 1280x960 60.00 > 1024x768 60.0460.00 > 960x720 60.00 > 928x696 60.05 > 896x672 60.01 > 800x600 60.0060.3256.25 > 700x525 59.98 > 640x512 60.02 > 640x480 60.0059.94 > 512x384 60.00 > 400x300 60.3256.34 > 320x240 60.05 > HDMI-1 disconnected (normal left inverted right x axis y axis) > DP-1 disconnected (normal left inverted right x axis y axis) OK, so I think that these are not the HDMI/DP outputs connected to your secondary device. They are the ones connected to your primary device (might not be pinned out, or might only be available via an optional dock). Normally there'd be an extra -1- in the name of such outputs. But who knows with modesetting - perhaps it doesn't stick that in and sticks 100% to the kernel names. Have a look at https://nouveau.freedesktop.org/wiki/Optimus/ for some details on how to set up output offloading. The short version is that you want to do something like xrandr --setprovideroutputsource 1 0 If that doesn't help, grab the output of grep . /sys/class/drm/card*-*/status grep . /sys/class/drm/card*-*/modes preferably while something is plugged into one of your NVIDIA-attached connectors. When X first starts, it appears to get an EDID just fine for your secondary GPU's DP-1 output... Cheers, -ilia ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] New: [nouveau] garbled rending with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 Bug ID: 99400 Summary: [nouveau] garbled rending with glamor on G71 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau@lists.freedesktop.org Reporter: four...@xfce.org QA Contact: nouveau@lists.freedesktop.org Created attachment 128933 --> https://bugs.freedesktop.org/attachment.cgi?id=128933&action=edit Screenshot of the issue Description: While investigating rendering bugs on Xwayland with nouveau specifically ([1] and [2]) I realized that some gtk2 output (this Xwayland) is completely garbled. [1] https://bugzilla.redhat.com/show_bug.cgi?id=1411447 [2] https://bugzilla.gnome.org/show_bug.cgi?id=776255 How reproducible: Always Steps to reproduce: 1. Log in a Wayland session (either Weston or GNOME shell) on a Dell M1710 with a GeForce Go 7950 GTX 2. Run gtk-demo (the one from gtk2, i.e. not Wayland native but relying on Xwayland) 3. Start the "Assistant" demo (second starting from the top) Actual result: The window is black with random content Expected result: The rendering is correct Additional data: This issue does not occur when using "shm" and CPU rendering instead of glamor in Xwayland. I am not aware of any other hardware where glamor produces such garbled output, so I suspect an issue with nouveau, but if you reckon it's an issue with glamor instead, please flip this bug back to xserver/glamor I have seen other issue with black icons being reported with glamor and nouveau as well and these do not occur when using the CPU render in weston for example (https://bugzilla.redhat.com/show_bug.cgi?id=1411447#c12) In my case, hardware is VGA compatible controller: NVIDIA Corporation G71M [GeForce Go 7950 GTX] (rev a1) (prog-if 00 [VGA controller]) 01:00.0 0300: 10de:0297 (rev a1) (prog-if 00 [VGA controller]) Subsystem: 1028:019b -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rending with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #1 from Olivier Fourdan --- apitrace of Xwayland available here: https://people.freedesktop.org/~ofourdan/xwayland-apitrace-bug-99400.bz2 -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GP106M+Intel Skylake, Kernel 4.10-rc3 : No display on HDMI or DP
> > OK, so I think that these are not the HDMI/DP outputs connected to > your secondary device. They are the ones connected to your primary > device (might not be pinned out, or might only be available via an > optional dock). Normally there'd be an extra -1- in the name of such > outputs. But who knows with modesetting - perhaps it doesn't stick > that in and sticks 100% to the kernel names. > > Have a look at https://nouveau.freedesktop.org/wiki/Optimus/ for some > details on how to set up output offloading. The short version is that > you want to do something like > > xrandr --setprovideroutputsource 1 0 > > If that doesn't help, grab the output of > > grep . /sys/class/drm/card*-*/status > grep . /sys/class/drm/card*-*/modes > > preferably while something is plugged into one of your NVIDIA-attached > connectors. When X first starts, it appears to get an EDID just fine > for your secondary GPU's DP-1 output... > > Cheers, > > -ilia > Thanks Ilia; I already checked the wiki page, with no success so far. xrandr --setprovideroutputsource 1 0 seems to do nothing, either with a monitor connected to HDMI-1 or not. The second monitor is detected and available in the screen configuration tool of KDE, but it remains black, no window, nothing. With a monitor conected in HDMI-1, here are the results of the commands : sigmar@TALABHEIM:~> grep . /sys/class/drm/card*-*/status /sys/class/drm/card0-eDP-1/status:*connected* /sys/class/drm/card1-DP-1/status:*disconnected* /sys/class/drm/card1-HDMI-A-1/status:*connected* sigmar@TALABHEIM:~> grep . /sys/class/drm/card*-*/modes /sys/class/drm/card0-eDP-1/modes:*1920x1080* /sys/class/drm/card0-eDP-1/modes:*1920x1080* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080i* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080i* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080* /sys/class/drm/card1-HDMI-A-1/modes:*1920x1080i* /sys/class/drm/card1-HDMI-A-1/modes:*1600x1200* /sys/class/drm/card1-HDMI-A-1/modes:*1680x1050* /sys/class/drm/card1-HDMI-A-1/modes:*1280x1024* /sys/class/drm/card1-HDMI-A-1/modes:*1280x1024* /sys/class/drm/card1-HDMI-A-1/modes:*1440x900* /sys/class/drm/card1-HDMI-A-1/modes:*1280x960* /sys/class/drm/card1-HDMI-A-1/modes:*1366x768* /sys/class/drm/card1-HDMI-A-1/modes:*1152x864* /sys/class/drm/card1-HDMI-A-1/modes:*1280x720* /sys/class/drm/card1-HDMI-A-1/modes:*1280x720* /sys/class/drm/card1-HDMI-A-1/modes:*1280x720* /sys/class/drm/card1-HDMI-A-1/modes:*1024x768* /sys/class/drm/card1-HDMI-A-1/modes:*1024x768* /sys/class/drm/card1-HDMI-A-1/modes:*1024x768* /sys/class/drm/card1-HDMI-A-1/modes:*832x624* /sys/class/drm/card1-HDMI-A-1/modes:*800x600* /sys/class/drm/card1-HDMI-A-1/modes:*800x600* /sys/class/drm/card1-HDMI-A-1/modes:*800x600* /sys/class/drm/card1-HDMI-A-1/modes:*800x600* /sys/class/drm/card1-HDMI-A-1/modes:*720x576* /sys/class/drm/card1-HDMI-A-1/modes:*720x480* /sys/class/drm/card1-HDMI-A-1/modes:*720x480* /sys/class/drm/card1-HDMI-A-1/modes:*640x480* /sys/class/drm/card1-HDMI-A-1/modes:*640x480* /sys/class/drm/card1-HDMI-A-1/modes:*640x480* /sys/class/drm/card1-HDMI-A-1/modes:*640x480* /sys/class/drm/card1-HDMI-A-1/modes:*640x480* /sys/class/drm/card1-HDMI-A-1/modes:*720x400* Any hints really appreciated, Regards, Sylvain ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 Olivier Fourdan changed: What|Removed |Added Summary|[nouveau] garbled rending |[nouveau] garbled rendering |with glamor on G71 |with glamor on G71 -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #2 from Ilia Mirkin --- Not that it's of much consolation, but the nv30 GL driver sucks. There are a number of unhandled situations, and I wouldn't be overly surprised if glamor were to hit one or several of them. A "big hammer" approach to fixing some of the issues is running with NV30_SWTNL=1, although there's plenty more issues that this won't have an effect on. That usually fixes "bad geometry" issues, however the screenshot seems to suggest that perhaps incompatible color and depth buffers are being mixed - we print a warning about those in debug builds. I'll have a look at the apitrace later to see if can try reproducing on my NV34, although it's possible that won't work this time. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GP106M+Intel Skylake, Kernel 4.10-rc3 : No display on HDMI or DP
On Fri, Jan 13, 2017 at 10:11 AM, Sylvain Fabre wrote: > xrandr --setprovideroutputsource 1 0 seems to do nothing, either with a > monitor connected to HDMI-1 or not. The second monitor is detected and > available in the screen configuration tool of KDE, but it remains black, no > window, nothing. > > With a monitor conected in HDMI-1, here are the results of the commands : > > sigmar@TALABHEIM:~> grep . /sys/class/drm/card*-*/status > /sys/class/drm/card0-eDP-1/status:connected > /sys/class/drm/card1-DP-1/status:disconnected > /sys/class/drm/card1-HDMI-A-1/status:connected OK. So it sees the monitor, and detects its modes. Can you confirm that these are *not* listed in xrandr? In your original xrandr paste, the DP-1/HDMI-1 connectors were listed as disconnected. Perhaps you ran that xrandr command when the second monitor was not connected? Thanks, -ilia ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #3 from Olivier Fourdan --- (In reply to Ilia Mirkin from comment #2) > Not that it's of much consolation, but the nv30 GL driver sucks. There are a > number of unhandled situations, and I wouldn't be overly surprised if glamor > were to hit one or several of them. Could be a regression, I don't remember seeing those /before/ and the downstream bugs about black icons are recent as well. And there've been some glamor changes in the xserver as well, so it oculd be /something/ in glamor has changed and doesn't play well with the driver. > A "big hammer" approach to fixing some of the issues is running with > NV30_SWTNL=1, although there's plenty more issues that this won't have an > effect on. That usually fixes "bad geometry" issues, however the screenshot > seems to suggest that perhaps incompatible color and depth buffers are being > mixed Yes, that makes me think of that as well, could explain the black icons being reported downstream. > - we print a warning about those in debug builds. Good, so I'll rebuild with "--enable-debug" and see what I get. > I'll have a look at the apitrace later to see if can try reproducing on my > NV34, although it's possible that won't work this time. Thanks a bunch! -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GP106M+Intel Skylake, Kernel 4.10-rc3 : No display on HDMI or DP
Le vendredi 13 janvier 2017, 10:35:49 CET Ilia Mirkin a écrit : > > OK. So it sees the monitor, and detects its modes. Can you confirm > that these are *not* listed in xrandr? In your original xrandr paste, > the DP-1/HDMI-1 connectors were listed as disconnected. Perhaps you > ran that xrandr command when the second monitor was not connected? > > Thanks, > > -ilia > Sorry for the misunderstanding on my side : when a monitor is connected, xrandr shaow also the modes availables (example below). Note that from time to time, after connecting a monitor to DP-1 or HDMI-1, the "xrand" command is completely freezing my computer and i am obliged to perform a bruteforce ON/OFF with the power button. Example of xrandr with a a monitor connected to HDMI- 1: sigmar@TALABHEIM:/media/encfs/PIXKIT> xrandr ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #4 from Ilia Mirkin --- (In reply to Olivier Fourdan from comment #3) > (In reply to Ilia Mirkin from comment #2) > > Not that it's of much consolation, but the nv30 GL driver sucks. There are a > > number of unhandled situations, and I wouldn't be overly surprised if glamor > > were to hit one or several of them. > > Could be a regression, I don't remember seeing those /before/ and the > downstream bugs about black icons are recent as well. > > And there've been some glamor changes in the xserver as well, so it oculd be > /something/ in glamor has changed and doesn't play well with the driver. This may come as some surprise, but nv30 is not a hotbed of development activity. If you can figure out a change in mesa that broke it, that'd be very helpful. Separately, check dmesg - NVIDIA cards tend to yell loudly when we do something wrong. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #5 from Olivier Fourdan --- (In reply to Ilia Mirkin from comment #4) > This may come as some surprise, but nv30 is not a hotbed of development Understandable :) > activity. If you can figure out a change in mesa that broke it, that'd be > very helpful. Actually, I was thinking more about glamor here. > Separately, check dmesg - NVIDIA cards tend to yell loudly when we do > something wrong. I have tried a build with --enable-debug, but I see nothing wrong at all being reported neither in dmesg nor in journalctl. -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
Re: [Nouveau] GP106M+Intel Skylake, Kernel 4.10-rc3 : No display on HDMI or DP
Le vendredi 13 janvier 2017 16:11:59 CET, vous avez écrit : In addition, i noticed the following : xrand --output HDMI-1 --auto show the following messages in the dmesg : 24957.310638] nouveau :01:00.0: DRM: resuming kernel object tree... [24957.310873] nouveau :01:00.0: priv: HUB0: 00d054 0007 (18408216) [24957.369494] nouveau :01:00.0: DRM: resuming client object trees... [24957.369497] nouveau :01:00.0: DRM: resuming display... [24957.369558] nouveau :01:00.0: DRM: resuming console... ___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #6 from Ilia Mirkin --- (In reply to Olivier Fourdan from comment #1) > apitrace of Xwayland available here: > > https://people.freedesktop.org/~ofourdan/xwayland-apitrace-bug-99400.bz2 How did you get this trace? I can't seem to replay it - none of the context setup stuff is there. (And it seems to like doing glFlush *a lot*...) -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #7 from Olivier Fourdan --- (In reply to Ilia Mirkin from comment #6) > How did you get this trace? I can't seem to replay it - none of the context > setup stuff is there. (And it seems to like doing glFlush *a lot*...) Directly on Xwayland. apitrace trace /usr/bin/Xwayland "$@" -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 92077] nouveau graphics freeze when using KDE Plasma 5; PGR engine fault
https://bugs.freedesktop.org/show_bug.cgi?id=92077 --- Comment #30 from Andrey Mazo --- (In reply to Ilia Mirkin from comment #29) > Can someone see whether sticking > > QSG_RENDER_LOOP=basic > > into /etc/environment helps anything? I could try, but looks like it's used by default already: $ QT_LOGGING_RULES="qt.scenegraph.general=true" plasmawindowed org.kde.plasma.systemmonitor.net qt.scenegraph.general: QSG: basic render loop qt.scenegraph.general: texture atlas dimensions: 1024x512 qt.scenegraph.general: R/G/B/A Buffers:8 8 8 8 qt.scenegraph.general: Depth Buffer: 24 qt.scenegraph.general: Stencil Buffer: 8 qt.scenegraph.general: Samples:-1 qt.scenegraph.general: GL_VENDOR: nouveau qt.scenegraph.general: GL_RENDERER:Gallium 0.4 on NVD9 qt.scenegraph.general: GL_VERSION: 3.0 Mesa 12.0.1 ... I don't know for sure, which one was used when I reported the problem originally (comment 17) or when captured an apitrace (comment 23). But I would guess, that it was the same based on the following [1]: """ The non-threaded render loop is currently used by default ... Linux with Mesa drivers. """ [1] http://doc.qt.io/qt-5/qtquick-visualcanvas-scenegraph.html#non-threaded-render-loops-basic-and-windows -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
[Nouveau] [Bug 99400] [nouveau] garbled rendering with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 --- Comment #8 from Ilia Mirkin --- (In reply to Olivier Fourdan from comment #7) > (In reply to Ilia Mirkin from comment #6) > > How did you get this trace? I can't seem to replay it - none of the context > > setup stuff is there. (And it seems to like doing glFlush *a lot*...) > > Directly on Xwayland. > > apitrace trace /usr/bin/Xwayland "$@" OK, well, if I can't replay the trace then it's not of much use. I don't know anything about Wayland or XWayland or how they work, unfortunately. Perhaps you might have success in tracing Xvfb + glamor or Xnest + glamor or something? -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___ Nouveau mailing list Nouveau@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/nouveau
