mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2021-03-05T19:40:03Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/10953D acceleration/OpenGL corrupts output on GeForce FX-52002021-03-05T19:40:03ZBugzilla Migration User3D acceleration/OpenGL corrupts output on GeForce FX-5200## Submitted by tho..@..lin.de
Assigned to **Nouveau Project**
**[Link to original bug (#93613)](https://bugs.freedesktop.org/show_bug.cgi?id=93613)**
## Description
etracer does render a useful display with the nouveau xorg drive...## Submitted by tho..@..lin.de
Assigned to **Nouveau Project**
**[Link to original bug (#93613)](https://bugs.freedesktop.org/show_bug.cgi?id=93613)**
## Description
etracer does render a useful display with the nouveau xorg driver. While the title and options screen renders successful, the main game remains at a solid blue screen, or at best, colored/shaded lines drawn from the top-left of the screen. The game is not playable.
The hardware is an old Geforce FX5200 card, in an old Pentium-4 system.
Version: 10.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1094Hack'n'Slash hangs with Nouveau driver2019-09-18T20:42:00ZBugzilla Migration UserHack'n'Slash hangs with Nouveau driver## Submitted by Steven Zakulec
Assigned to **Nouveau Project**
**[Link to original bug (#93563)](https://bugs.freedesktop.org/show_bug.cgi?id=93563)**
## Description
Created attachment 120767
Dmesg from boot that includes playing ...## Submitted by Steven Zakulec
Assigned to **Nouveau Project**
**[Link to original bug (#93563)](https://bugs.freedesktop.org/show_bug.cgi?id=93563)**
## Description
Created attachment 120767
Dmesg from boot that includes playing Hack'n'Slash
Hack'n'Slash- (http://store.steampowered.com/app/246070/?snr=1_7_15__13) freezes up & hangs very early in the game (once you get to the main map). This only happens with the Nouveau driver- if you install the proprietary NVidia driver (version doesn't seem to matter), the game works just fine.
Here's my system information:
HP Compaq 8510w laptop
Kubuntu 14.04
OpenGL renderer string: Gallium 0.4 on NV84
OpenGL version string: 3.0 Mesa 11.2.0-devel (git-b835255 2016-01-01 trusty-oibaf-ppa
Kernel: 3.13.0-49-generic
CPU: model name : Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz
Graphics card:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G84GLM [Quadro FX 570M] [10de:040c] (rev a1)
How to reproduce this:
Start a new game.
Finish the first room, and then go through the second room where you name your sprite.
Once you try to leave that room, you'll be taken to the world map.
If you have an existing save game, you need to rewind to BobCave (where Bob is the name of your sprite).
What happens:
The screen loads very slowly, the transition goes on for a very long time, and almost every keyboard & mouse press is swallowed up- if you're patient, you can eventually get the game menu to show up by pressing Esc enough times, and then going down to exit game. You can also just Alt-Tab out and kill the game.
You can't really continue playing because of these issues.
What should happen:
You leave the cave, and you get a quick transition to the world map (maybe 2-3 seconds), and then you can move freely around the screen without any lag or screen corruption.
I've attached my dmesg log which does have some Nouveau error messages from when I was playing.
**Attachment 120767**, "Dmesg from boot that includes playing Hack'n'Slash":
[dmesg-bug-report](/uploads/562ac4898abe6dfef22f6411c7af929a/dmesg-bug-report)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1093[NVA5] The Long Dark (game) is very slow because of "kernel rejected pushbuf"...2019-09-18T20:41:54ZBugzilla Migration User[NVA5] The Long Dark (game) is very slow because of "kernel rejected pushbuf" messages in log files## Submitted by Alexander Schlarb
Assigned to **Nouveau Project**
**[Link to original bug (#93254)](https://bugs.freedesktop.org/show_bug.cgi?id=93254)**
## Description
Created attachment 120358
First "kernel rejected pushbuf" err...## Submitted by Alexander Schlarb
Assigned to **Nouveau Project**
**[Link to original bug (#93254)](https://bugs.freedesktop.org/show_bug.cgi?id=93254)**
## Description
Created attachment 120358
First "kernel rejected pushbuf" error in log file
Kernel: Linux 4.3 (snapshot from 2015-11-04)
Mesa: 11.0.2
nouveau X11 driver: 1.0.11
Platform: Sony VPCF12S1E with NVidiaGT216M (GForce GT 330M)
System: Debian testing based
Starting the game works fine (although it is somewhat slower than with NVidia's driver), but once you launch the actual game Unity starts logging up to 1GB/min worth of "kernel rejected pushbuf" logs into the "~/.config/unity3d/Hinterland/The Long Dark/Player.log" log file. Making that file (and it's containing directory) read-only I could verify that the game runs at acceptable frame rates and without noticeable glitches most of the time. Sometimes however, some textures disappear and it hangs for several seconds before resuming.
Steps to reproduce:
1) Purchase and download "The Long Dark" from Steam[1]
2) Navigate to "~/.local/share/Steam/steamapps/common/TheLongDark" (on the console or a file browser)
3) Launch the "tld.x86_64" file[2]
4) Press any key to move past the disclaimer screen
5) Select "Sandbox" from the main menu[3]
6) Start a "New" game or "Continue" a previous survival trip
7) Wait for the actual game to load
8) Observe extreme slowness while the disk I/O is a 100%
"Step 8" does not happen with NVidia binary drivers and the game is quite playable.
See "Player.log.head" for first "kernel rejected pushbuf" error.
The corresponding `dmesg` message is:
nouveau 0000:01:00.0: tld.x86_64[28285]: nv50cal_space: -16
If you tell me what to do for debugging this, I'll definitely help as much as I can in fixing this issue!
(Including kernel patches, traces, etc.)
Notes:
1. I'm willing to donate a copy of the game to one established Nouveau contributor
2. The game cannot be launched from Steam when using recent versions of Open source drivers due to https://github.com/ValveSoftware/steam-runtime/issues/34
3. Due to the game being alpha right now the "Story"-mode has not been released yet – this shouldn't matter however
**Attachment 120358**, "First "kernel rejected pushbuf" error in log file":
[Player.log.head](/uploads/97aa6f31e170636d9431382e55bf7ae3/Player.log.head)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1092Warsow 2.0 crashes in nouveau_fence_trigger_work2020-02-08T19:27:56ZBugzilla Migration UserWarsow 2.0 crashes in nouveau_fence_trigger_work## Submitted by Marcin Ślusarz `@mslusarz`
Assigned to **Nouveau Project**
**[Link to original bug (#93197)](https://bugs.freedesktop.org/show_bug.cgi?id=93197)**
## Description
Warsow can be downloaded from: https://www.warsow.gg...## Submitted by Marcin Ślusarz `@mslusarz`
Assigned to **Nouveau Project**
**[Link to original bug (#93197)](https://bugs.freedesktop.org/show_bug.cgi?id=93197)**
## Description
Warsow can be downloaded from: https://www.warsow.gg/download
gdb session:
```
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe704a700 (LWP 12680)]
nouveau_fence_trigger_work (fence=fence@entry=0x7fffd0296850) at nouveau_fence.c:57
57 LIST_DEL(&work->list);
(gdb) bt
#0 nouveau_fence_trigger_work (fence=fence@entry=0x7fffd0296850) at nouveau_fence.c:57
#1 0x00007fffef9459be in nouveau_fence_update (screen=screen@entry=0xac1060, flushed=flushed@entry=false) at nouveau_fence.c:132
#2 0x00007fffef945c6e in nouveau_fence_wait (fence=0x7fffd0296850, debug=0x0) at nouveau_fence.c:223
#3 0x00007fffef68b0cb in st_finish (st=st@entry=0x17d6130) at state_tracker/st_cb_flush.c:101
#4 0x00007fffef68b110 in st_glFinish (ctx=<optimized out>) at state_tracker/st_cb_flush.c:136
#5 0x00007fffd72ef731 in ?? () from ./libs/libref_gl_x86_64.so
#6 0x0000000000405af6 in ?? ()
#7 0x0000000000405bc9 in ?? ()
#8 0x00007fffd72eb304 in ?? () from ./libs/libref_gl_x86_64.so
#9 0x00007ffff78bc6aa in start_thread (arg=0x7fffe704a700) at pthread_create.c:333
#10 0x00007ffff70e1eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
(gdb) print work
$1 = (struct nouveau_fence_work *) 0x7fffd815fc50
(gdb) print work->list
$2 = {prev = 0x0, next = 0x7fffd8121510}
(gdb) list
52 {
53 struct nouveau_fence_work *work, *tmp;
54
55 LIST_FOR_EACH_ENTRY_SAFE(work, tmp, &fence->work, list) {
56 work->func(work->data);
57 LIST_DEL(&work->list);
58 FREE(work);
59 }
60 }
61
(gdb) i threads
Id Target Id Frame
7 Thread 0x7fffe6048700 (LWP 12675) "warsow.x86_64" 0x00007ffff70d8743 in select () at ../sysdeps/unix/syscall-template.S:81
6 Thread 0x7fffe6849700 (LWP 12679) "warsow.x86_64" 0x00007ffff70d80b7 in ioctl () at ../sysdeps/unix/syscall-template.S:81
5 Thread 0x7fffd72a2700 (LWP 12683) "SDLAudioDev1" 0x00007ffff70d69a1 in __GI_ppoll (fds=0x7fffe003b060, nfds=2, timeout=<optimized out>, sigmask=0x0)
at ../sysdeps/unix/sysv/linux/ppoll.c:56
* 4 Thread 0x7fffe704a700 (LWP 12680) "warsow.x86_64" nouveau_fence_trigger_work (fence=fence@entry=0x7fffd0296850) at nouveau_fence.c:57
2 Thread 0x7fffe784b700 (LWP 12681) "warsow.x86_64" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:238
1 Thread 0x7ffff7fb9780 (LWP 12632) "warsow.x86_64" (Exiting) 0x00007fffd72e62b8 in ?? () from ./libs/libref_gl_x86_64.so
(gdb) print work
work work_count worklist_elem
(gdb) print work->func
$3 = (void (*)(void *)) 0x7fffef945d20 <nouveau_fence_unref_bo>
(gdb)
```
This is with Mesa-git from ~2 weeks ago:
OpenGL renderer string: Gallium 0.4 on NVE7
OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.1.0-devel (git-1a18457)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1091OpenScad has lousy performance2019-09-18T20:41:49ZBugzilla Migration UserOpenScad has lousy performance## Submitted by Roger Wolff
Assigned to **Nouveau Project**
**[Link to original bug (#92968)](https://bugs.freedesktop.org/show_bug.cgi?id=92968)**
## Description
OpenScad performance is WAY less than what I'm used to. This is wit...## Submitted by Roger Wolff
Assigned to **Nouveau Project**
**[Link to original bug (#92968)](https://bugs.freedesktop.org/show_bug.cgi?id=92968)**
## Description
OpenScad performance is WAY less than what I'm used to. This is with new hardware and a more recent ubuntu version.
Suggestion on the mailing list: disable vblank syncing. I was unable to do this. The environment variable setting that works for glxgears does not influence the behaviour of openscad. I was unable to achieve disabling the option in the X server.
Suggestions on the IRC channel led me to try installing an older version. I created an chrooted ubuntu 14.04 environment. The openscad in there provides reasonable performance.
I then recompiled the current git version of openscad in the chrooted 14.04 environment, and that too provides reasonable performance.
So: Without changing the X server (or its configuration) it is possible to achieve good performance. Also, the source of openscad is not the culprit, but the libraries linked to.
This does not mean that it is not an openscad bug: It could very well be that openscad requests a feature that was unimplemented on earlier libraries.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1090[NV1F celcius GeForce4 MX] Rendering artifacts, screen corruption, system reset.2022-10-30T22:13:47ZBugzilla Migration User[NV1F celcius GeForce4 MX] Rendering artifacts, screen corruption, system reset.## Submitted by Exidux
Assigned to **Nouveau Project**
**[Link to original bug (#92959)](https://bugs.freedesktop.org/show_bug.cgi?id=92959)**
## Description
Created attachment 119671
dmesg after booting.
The system displays rend...## Submitted by Exidux
Assigned to **Nouveau Project**
**[Link to original bug (#92959)](https://bugs.freedesktop.org/show_bug.cgi?id=92959)**
## Description
Created attachment 119671
dmesg after booting.
The system displays rendering artifacts.
The first ones to appear are thin lines flashing around on the lower half of the screen. Once a single (or multiple) program(s) is opened which use Opengl the screen will become partially distorted and usually (but not always) in the lower half area.
Typical glitches seem to be made up of fragments of what is shown on screen.
In most cases the computer needs a reboot to get back to a nearly clean desktop.
It gets triggered, or rather worsened by programs which use Opengl.
Vlc media player, while using the Xvideo output(XCB), will only suffer the anoying twitching glitch on the lower part of the screen, which also affects the desktop.
This happened twice and will not be tested again for the sake of my hardware ;
The system will reset without warning if running Opengl video, games, programs in full screen for prolonged times.
**Attachment 119671**, "dmesg after booting.":
[dmesg.txt](/uploads/c331a3b6630903684464d215d1b804b1/dmesg.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1089System hangs at visiting WebGL site2019-09-18T20:41:37ZBugzilla Migration UserSystem hangs at visiting WebGL site## Submitted by uxv
Assigned to **Nouveau Project**
**[Link to original bug (#92556)](https://bugs.freedesktop.org/show_bug.cgi?id=92556)**
## Description
Created attachment 119007
Two files: 'kmsg' and 'Xorg.0.log.old'
When I vi...## Submitted by uxv
Assigned to **Nouveau Project**
**[Link to original bug (#92556)](https://bugs.freedesktop.org/show_bug.cgi?id=92556)**
## Description
Created attachment 119007
Two files: 'kmsg' and 'Xorg.0.log.old'
When I visit any WebGL site, after it's done loading everything on screen freezes except mouse cursor. Keyboard not responding too, so only hard reset helps :)
Kernel messages and Xorg log are in attachment.
I have already posted a topic at https://bbs.archlinux.org/viewtopic.php?id=203765 There are some other kernel messages.
--
$ pacman -Qi mesa libdrm xf86-video-nouveau xorg-server firefox | egrep "Name|Version"
Name : mesa
Version : 11.0.3-1
Name : libdrm
Version : 2.4.65-1
Name : xf86-video-nouveau
Version : 1.0.11-3
Name : xorg-server
Version : 1.17.2-4
Name : firefox
Version : 41.0.2-1
--
Maybe it somewhat related to https://bugs.freedesktop.org/show_bug.cgi?id=89985
~~**Attachment 119007**~~, "Two files: 'kmsg' and 'Xorg.0.log.old'":
[webgl.tar.xz](/uploads/71f1eaf9325ddc2e4c89d4f933245943/webgl.tar.xz)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1088Virtualbox with 3D acceleration and with installed vbox-additions crashes2019-09-18T20:41:34ZBugzilla Migration UserVirtualbox with 3D acceleration and with installed vbox-additions crashes## Submitted by Tomasz Paweł Gajc
Assigned to **Nouveau Project**
**[Link to original bug (#92515)](https://bugs.freedesktop.org/show_bug.cgi?id=92515)**
## Description
I'm running this setup:
libdrm:
lib64drm_nouveau2-2.4.65-0....## Submitted by Tomasz Paweł Gajc
Assigned to **Nouveau Project**
**[Link to original bug (#92515)](https://bugs.freedesktop.org/show_bug.cgi?id=92515)**
## Description
I'm running this setup:
libdrm:
lib64drm_nouveau2-2.4.65-0.1-omv2014.0.x86_64
Mesa:
lib64gl1-10.5.9-0.1-omv2014.0.x86_64
kernel:
kernel-nrjQL-desktop-4.1.9-1omv-1-1-omv2014.0.x86_64
Vbox:
virtualbox-5.0.6-0.2-omv2014.0.x86_64
My vbox setup have enabled 3D acceleration support and have installed vbox-additions. This are needed for moder toolkit like Qt5 which heavily uses 3D acceleration.
Unfortunately my vbox crashes, or applications inside vbox does not work or segfaults.
I found these in my host journal:
paź 18 01:07:01 lazur kernel: ieee80211 phy0: rt61pci_txdone: Warning - TX status report missed for entry 25
paź 18 01:08:06 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:08:08 lazur kernel: PS2K: Selected scan set 2
paź 18 01:08:14 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:08:14 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:08:15 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:12:35 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[4504]] get 0x002002f2d0 put 0x002002f914 ib_get 0x000000d3 ib_put 0x000000d4 state 0x8000a204 (e... push 0x00406040
paź 18 01:12:35 lazur kernel: nouveau E[VBoxCrWinCmd[4504]] push 1 buffer not in list
paź 18 01:12:35 lazur kernel: nouveau E[VBoxCrWinCmd[4504]] push 1 buffer not in list
paź 18 01:12:35 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[4504]] get 0x00200455a4 put 0x0020045690 ib_get 0x00000208 ib_put 0x0000022b state 0x8000005c (e... push 0x00406040
paź 18 01:12:35 lazur kernel: ShCrOpenGL[4503]: segfault at 8a0 ip 00007fa8e55998fc sp 00007fa8e58717b0 error 4
paź 18 01:12:35 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR
paź 18 01:12:35 lazur kernel: INVALID_BITFIELD
paź 18 01:12:35 lazur kernel:
paź 18 01:12:35 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[4504]] subc 4 class 0x502d mthd 0x0200 data 0x00047454
paź 18 01:12:35 lazur kernel: in libdrm_nouveau.so.2.0.0[7fa8e5597000+6000]
paź 18 01:12:57 lazur kernel: vboxdrv: ffffffffc0764020 VMMR0.r0
paź 18 01:12:57 lazur kernel: vboxdrv: ffffffffc085d020 VBoxDDR0.r0
paź 18 01:12:57 lazur kernel: vboxdrv: ffffffffc007d020 VBoxDD2R0.r0
paź 18 01:12:59 lazur kernel: PS2K: Selected scan set 2
paź 18 01:13:13 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:13:13 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:13:14 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:15:27 lazur kernel: vboxdrv: ffffffffc087b020 VMMR0.r0
paź 18 01:15:27 lazur kernel: vboxdrv: ffffffffc0974020 VBoxDDR0.r0
paź 18 01:15:27 lazur kernel: vboxdrv: ffffffffc0098020 VBoxDD2R0.r0
paź 18 01:15:29 lazur kernel: PS2K: Selected scan set 2
paź 18 01:15:33 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:15:33 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:15:34 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:16:27 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x002018cacc put 0x002018cb34 ib_get 0x0000028d ib_put 0x000002ac state 0x80007b10 (e... push 0x00406040
paź 18 01:16:27 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x002018cb3c put 0x002018cbb0 ib_get 0x0000028f ib_put 0x000002ac state 0x80000024 (e... push 0x00406040
paź 18 01:16:27 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_BITFIELD
paź 18 01:16:27 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 3 class 0x8297 mthd 0x1b00 data 0x07800000
paź 18 01:16:27 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_OPERATION
paź 18 01:16:27 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 3 class 0x8297 mthd 0x1b0c data 0x07800000
paź 18 01:17:19 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x0020081ff4 put 0x0020082ae0 ib_get 0x0000020e ib_put 0x0000020f state 0x80008228 (e... push 0x00406040
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x021c data 0xffffffff
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_BITFIELD
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x0220 data 0xffffffff
paź 18 01:17:19 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x002009d600 put 0x002009ded4 ib_get 0x000003cb ib_put 0x000003cc state 0x80000000 (e... push 0x00406040
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x0838 data 0x03b60000
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x083c data 0x000c6a0c
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x0844 data 0x43ed8000
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x084c data 0x000c6a00
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 4 class 0x502d mthd 0x0854 data 0xc3ed8000
paź 18 01:17:19 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x00200a4528 put 0x00200a46c4 ib_get 0x0000003a ib_put 0x0000003b state 0x80006f05 (e... push 0x00406040
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_BITFIELD
paź 18 01:17:19 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 3 class 0x8297 mthd 0x0910 data 0x000472e8
paź 18 01:18:54 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[6947]] get 0x0020188d4c put 0x00201898f4 ib_get 0x00000203 ib_put 0x00000204 state 0x80000000 (e... push 0x00406040
paź 18 01:18:54 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_ENUM
paź 18 01:18:54 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 3 class 0x8297 mthd 0x191c data 0x41c851ec
paź 18 01:18:54 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_ENUM
paź 18 01:18:54 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[6947]] subc 3 class 0x8297 mthd 0x1920 data 0x42780000
paź 18 01:22:23 lazur kernel: vboxdrv: ffffffffc0992020 VMMR0.r0
paź 18 01:22:23 lazur kernel: vboxdrv: ffffffffc0a8b020 VBoxDDR0.r0
paź 18 01:22:23 lazur kernel: vboxdrv: ffffffffc0159020 VBoxDD2R0.r0
paź 18 01:22:24 lazur kernel: PS2K: Selected scan set 2
paź 18 01:22:36 lazur kernel: vboxdrv: ffffffffc0aa9020 VMMR0.r0
paź 18 01:22:36 lazur kernel: vboxdrv: ffffffffc0ba2020 VBoxDDR0.r0
paź 18 01:22:36 lazur kernel: vboxdrv: ffffffffc01fb020 VBoxDD2R0.r0
paź 18 01:22:37 lazur kernel: PS2K: Selected scan set 2
paź 18 01:22:41 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:22:41 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:22:42 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:24:49 lazur kernel: vboxdrv: ffffffffc0764020 VMMR0.r0
paź 18 01:24:49 lazur kernel: vboxdrv: ffffffffc085d020 VBoxDDR0.r0
paź 18 01:24:49 lazur kernel: vboxdrv: ffffffffc007d020 VBoxDD2R0.r0
paź 18 01:24:51 lazur kernel: PS2K: Selected scan set 2
paź 18 01:25:11 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:25:11 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:25:12 lazur kernel: HPET: Using timer above configured range: 3
paź 18 01:26:12 lazur kernel: nouveau E[VBoxCrWinCmd[7184]] multiple instances of buffer 30 on validation list
paź 18 01:26:12 lazur kernel: nouveau E[VBoxCrWinCmd[7184]] validate_init
paź 18 01:26:12 lazur kernel: nouveau E[VBoxCrWinCmd[7184]] validate: -22
paź 18 01:26:12 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[7184]] get 0x002003f5dc put 0x002003fd84 ib_get 0x0000019e ib_put 0x000001c5 state 0x80007220 (e... push 0x00406040
paź 18 01:26:12 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[7184]] get 0x0020e41344 put 0x0020e41370 ib_get 0x0000019f ib_put 0x000001c5 state 0x80000000 (e... push 0x00406040
paź 18 01:26:12 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[7184]] get 0x002003ffd4 put 0x002003ffd8 ib_get 0x000001a0 ib_put 0x000001c5 state 0x80007b10 (e... push 0x00406040
paź 18 01:26:12 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_VALUE
paź 18 01:26:12 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[7184]] subc 3 class 0x8297 mthd 0x1b04 data 0x000475ec
paź 18 01:26:12 lazur kernel: nouveau E[ PFIFO][0000:01:00.0] DMA_PUSHER - ch 5 [VBoxCrWinCmd[7184]] get 0x0020379744 put 0x002037974c ib_get 0x000001a1 ib_put 0x000001c5 state 0x80000000 (e... push 0x00406040
paź 18 01:26:12 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] DATA_ERROR INVALID_BITFIELD
paź 18 01:26:12 lazur kernel: nouveau E[ PGRAPH][0000:01:00.0] ch 5 [0x001f764000 VBoxCrWinCmd[7184]] subc 3 class 0x8297 mthd 0x1b0c data 0x000375f
Version: 10.6
### Depends on
* [Bug 92077](https://bugs.freedesktop.org/show_bug.cgi?id=92077)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1086Display errors in Qt applications after using Android Virtual Devices2019-09-18T20:41:19ZBugzilla Migration UserDisplay errors in Qt applications after using Android Virtual Devices## Submitted by Guido Winkelmann
Assigned to **Nouveau Project**
**[Link to original bug (#92287)](https://bugs.freedesktop.org/show_bug.cgi?id=92287)**
## Description
Created attachment 118670
Screenshot showing the problems
Aft...## Submitted by Guido Winkelmann
Assigned to **Nouveau Project**
**[Link to original bug (#92287)](https://bugs.freedesktop.org/show_bug.cgi?id=92287)**
## Description
Created attachment 118670
Screenshot showing the problems
After using an Android Virtual Machine (from Android Studio, https://developer.android.com/sdk/index.html) and stopping it, Qt/KDE application will show weird display errors. Pixmaps get drawn poorly aligned or with parts of them corrupted or just not at all, some windows are translucent when they should not be, drop down menus are not drawn fully (some items do not get drawn, although the space for them is still reserved) and have horizontal bars, either black or of various weird colors, through them. Most applications affected by this become unusable. I will attach a screenshot that shows the problem.
Only Qt/KDE applications seem to be affected by this, as far as I can tell. Only applications that are newly started after this will be affected, not applications that have been running before but have opened new windows. When these problems start to happen, only restarting the computer seems to fix them, simply restarting the X server is not enough.
On two occasions so far, the problems were even worse: The X display froze completely, except for mouse movements, and I could no longer switch the keyboards NumLuck LED on or off by pressing Numlock. I had to reset the machine with a SysRq sequence.
This problem is not always reproducible, but seems to happen more often when running two AVDs simultaneously and then quitting them. The AVDs need to be configured to "Use Host GPU". I have not found any other way to reproduce this.
My system:
Gentoo Linux on x86_64
X server: xorg-server 1.17.2-r1
Display driver: 1.0.11
Mesa: 11.0.2
Kernel version: 4.2.2
This also happened with earlier versions of the X server and Mesa. I upgraded those after this problem first started,
**Attachment 118670**, "Screenshot showing the problems":
![snapshot2](/uploads/2225ebc8f046b3e5b874e26907bf4f9d/snapshot2.png)
Version: 11.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1085WebGL Conformance conformance/textures/texture-size-limit.html -> system freeze2019-09-18T20:41:16ZBugzilla Migration UserWebGL Conformance conformance/textures/texture-size-limit.html -> system freeze## Submitted by Luke
Assigned to **Nouveau Project**
**[Link to original bug (#92136)](https://bugs.freedesktop.org/show_bug.cgi?id=92136)**
## Description
In Google Chrome, navigate to:
https://www.khronos.org/registry/webgl/con...## Submitted by Luke
Assigned to **Nouveau Project**
**[Link to original bug (#92136)](https://bugs.freedesktop.org/show_bug.cgi?id=92136)**
## Description
In Google Chrome, navigate to:
https://www.khronos.org/registry/webgl/conformance-suites/1.0.2/conformance/textures/texture-size-limit.html
On my on my GTX 650, this causes the desktop to lock-up with the Nouveau drivers, but passes with the Nvidia proprietary driver.
dmesg failure output:
[ 4183.336016] nouveau W[ DRM] skipped size 80010000
...
[ 4183.589907] nouveau W[ DRM] skipped size 80010000
[ 4183.740567] nouveau E[ PFIFO][0000:03:00.0] write fault at 0x002cfcb000 [PDE] from CE2/GR_CE on channel 0x007f61d000 [unknown]
Tested on Ubuntu 14.04 with default mesa and Ubuntu 15.10 with edgers(Mesa 11.0)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1084nouveau graphics freeze when using KDE Plasma 5; PGR engine fault2019-09-18T20:41:04ZBugzilla Migration Usernouveau graphics freeze when using KDE Plasma 5; PGR engine fault## Submitted by zoominee
Assigned to **Nouveau Project**
**[Link to original bug (#92077)](https://bugs.freedesktop.org/show_bug.cgi?id=92077)**
## Description
I upgraded KDE to Plasma-workspaces version 5. (Gentoo system)
Now, so...## Submitted by zoominee
Assigned to **Nouveau Project**
**[Link to original bug (#92077)](https://bugs.freedesktop.org/show_bug.cgi?id=92077)**
## Description
I upgraded KDE to Plasma-workspaces version 5. (Gentoo system)
Now, sometimes when my system has been idle for a while, it appears "unresponsive" when I come back (screen doesn't wake up on mouse, mouse pointer doesn't work if I switch off screen sleep, no reaction to any keys, etc.). The system doesn't crash, but the nouveau graphics output does, and I cannot reach a console using the keyboard, either.
I found the below output in /var/log/messages (a number of instances of observing the bug; ... indicates that I had to restart the system).
Versions used:
x11-drivers/xf86-video-nouveau-1.0.11
x11-base/xorg-server-1.16.4
media-libs/mesa-10.3.7-r1
x11-libs/libdrm-2.4.59
x11-base/xorg-drivers-1.16
Kernel: 4.0.5 (self-compiled)
I filed a bug against Plasma 5 but I'm not sure if it's their bug. See https://bugs.kde.org/show_bug.cgi?id=352605
I also have an apitrace record of plasmashell, replaying which (like a mini film) also freezes the nouveau. But it's a rather large file (1.4 GB) and contains private photos.
From /var/log/messages:
Sep 6 16:31:09 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] read fault at 0x0004042000 [PTE] from GR/GPC0/T1_1 on channel 0x0
03f7af000 [plasmashell[6790]]
Sep 6 16:31:09 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 10, recovering...
Sep 6 16:33:20 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] read fault at 0x0000023000 [PTE] from PBDMA0/HOST_CPU on channel
0x003fbe0000 [unknown]
[...]
Sep 7 23:30:25 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] write fault at 0x0003d49000 [PTE] from GR/GPC0/PROP_0 on channel
0x003f8ef000 [plasmashell[19341]]
Sep 7 23:30:25 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 8, recovering...
[...]
Sep 8 23:21:29 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] write fault at 0x0003e02000 [PTE] from GR/GPC0/PROP_0 on channel
0x003f8ef000 [plasmashell[4952]]
Sep 8 23:21:29 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 8, recovering...
[...]
Sep 10 02:00:03 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] read fault at 0x0001740000 [PTE] from GR/GPC0/T1_0 on channel 0x0
03f8ef000 [plasmashell[4709]]
Sep 10 02:00:03 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 8, recovering...
[...]
Sep 11 03:07:57 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] read fault at 0x0003508000 [PTE] from GR/GPC0/T1_0 on channel 0x0
03f84f000 [plasmashell[6720]]
Sep 11 03:07:57 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 9, recovering...
[...]
Sep 12 00:19:50 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] write fault at 0x0003ef5000 [PTE] from GR/GPC0/PROP_0 on channel
0x003facd000 [plasmashell[20804]]
Sep 12 00:19:50 localhost kernel: nouveau E[ PFIFO][0000:02:00.0] PGR engine fault on channel 5, recovering...
Version: 13.0
### Blocking
* [Bug 73373](https://bugs.freedesktop.org/show_bug.cgi?id=73373)
* [Bug 92438](https://bugs.freedesktop.org/show_bug.cgi?id=92438)
* [Bug 92515](https://bugs.freedesktop.org/show_bug.cgi?id=92515)
* [Bug 97537](https://bugs.freedesktop.org/show_bug.cgi?id=97537)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1083Artifacts in models rendering with GeForce 6150 (NV4x chipsets)2021-03-05T19:39:21ZBugzilla Migration UserArtifacts in models rendering with GeForce 6150 (NV4x chipsets)## Submitted by maurossi `@issor.oruam`
Assigned to **Nouveau Project**
**[Link to original bug (#91986)](https://bugs.freedesktop.org/show_bug.cgi?id=91986)**
## Description
Created attachment 118224
X-Wing model artifacts visibl...## Submitted by maurossi `@issor.oruam`
Assigned to **Nouveau Project**
**[Link to original bug (#91986)](https://bugs.freedesktop.org/show_bug.cgi?id=91986)**
## Description
Created attachment 118224
X-Wing model artifacts visible on with mesa 11.1git
X-Wing model and other models in FreeSpace2 with StarWars Original Trilogy mod shows rendering artifacts.
Filing a separate bug from https://bugs.freedesktop.org/show_bug.cgi?id=91551
as requested for NV4C chipset,
also because the artifacts are different.
Here I see big black poligons filling the screen, like vertexes of the model invading the whole screen.
NOTE: using mesa 10.6 the artifacts are not covering the entire GUI,
but I see some kind of vertex/surfaces problem, but the shaders maps are fine but the vertexes/surfaces are completely distorted.
Here is the link of the old trace that is able to produce the artifacs described in the different mesa versions. (X-Wing is the model visible before the Tie pilot)
http://www.mediafire.com/download/949r35rra31rpte/Tie_pilot_Nvidia_GT210_fs2_open_3.7.2.trace.7z
Attached pictures of the artifact for 11.1git and 10.6
Attached dmesg that show some nouveau errors, but most probably unrelated to the bug.
**Attachment 118224**, "X-Wing model artifacts visible on with mesa 11.1git":
![X-Wing_model_mesa_11_1_git](/uploads/ec8654621e186ffab5ea0fd8e055cfb5/X-Wing_model_mesa_11_1_git.jpg)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1082[nve7] Shadow Warrior: black gun2019-09-18T20:40:50ZBugzilla Migration User[nve7] Shadow Warrior: black gun## Submitted by Marcin Ślusarz `@mslusarz`
Assigned to **Nouveau Project**
**[Link to original bug (#91895)](https://bugs.freedesktop.org/show_bug.cgi?id=91895)**
## Description
Created attachment 118102
Shadow Warrior on Nouveau
...## Submitted by Marcin Ślusarz `@mslusarz`
Assigned to **Nouveau Project**
**[Link to original bug (#91895)](https://bugs.freedesktop.org/show_bug.cgi?id=91895)**
## Description
Created attachment 118102
Shadow Warrior on Nouveau
Screenshots comparing intel and nouveau attached.
Apitrace: http://people.freedesktop.org/~mslusarz/ShadowWarrior.bin.x86.trace.xz (174MB)
This is on mesa-git (3c6c4d4f298ec81fe57992790a68aaab2e573519) with the patch from bug#91890.
**Attachment 118102**, "Shadow Warrior on Nouveau":
![shadowwarrior-nouveau](/uploads/fb0be94f6af4dffe2d8da3d9ae687233/shadowwarrior-nouveau.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1081[NVE4] PGRAPH - grctx template channel unload timeout, failed to construct co...2019-09-18T20:40:31ZBugzilla Migration User[NVE4] PGRAPH - grctx template channel unload timeout, failed to construct context, init failed, -16## Submitted by Kyle De'Vir
Assigned to **Nouveau Project**
**[Link to original bug (#91722)](https://bugs.freedesktop.org/show_bug.cgi?id=91722)**
## Description
I have an Nvidia GeForce GTX 880M, which nouveau does not play with...## Submitted by Kyle De'Vir
Assigned to **Nouveau Project**
**[Link to original bug (#91722)](https://bugs.freedesktop.org/show_bug.cgi?id=91722)**
## Description
I have an Nvidia GeForce GTX 880M, which nouveau does not play with nicely. I have installed nouveau-fw, so the proprietary firmware is available.
When I boot my laptop, I get these errors:
nouveau E[ PGRAPH][0000:01:00.0] grctx template channel unload timeout
nouveau E[ PGRAPH][0000:01:00.0] failed to construct context
nouveau E[ PGRAPH][0000:01:00.0] init failed, -16
Operating system: Chakra OS (64-bit)
Relevant packages:
- linux-ck 4.1.6
- libdrm 2.4.64
- mesa 10.6.4
- mesa-vdpau 10.6.4
- opencl-mesa 10.6.4
- libva-mesa-driver 10.6.4
- xf86-video-nouveau 1.0.11
- nouveau-fw 340.32
I will also post my dmesg.log, Xorg.0.log and mmiotrace.log.xz.
Many thanks in advance. :)
Version: 10.6https://gitlab.freedesktop.org/mesa/mesa/-/issues/1080Assert in nouveau_pushbuf_data2023-10-07T10:11:57ZBugzilla Migration UserAssert in nouveau_pushbuf_data## Submitted by Allan Sandfeld Jensen
Assigned to **Nouveau Project**
**[Link to original bug (#91632)](https://bugs.freedesktop.org/show_bug.cgi?id=91632)**
## Description
I have been looking into why QtWebEngine crashes with the...## Submitted by Allan Sandfeld Jensen
Assigned to **Nouveau Project**
**[Link to original bug (#91632)](https://bugs.freedesktop.org/show_bug.cgi?id=91632)**
## Description
I have been looking into why QtWebEngine crashes with the nouveau driver, but the crashes appears asserts in the driver and not our code.
Any idea about what could trigger it:
```
#3 0x00007ffff0f032d2 in __GI___assert_fail (assertion=assertion@entry=0x7fffe1d77aa9 "kref",
file=file@entry=0x7fffe1d77a8a "../../nouveau/pushbuf.c", line=line@entry=726,
function=function@entry=0x7fffe1d77ad0 <__PRETTY_FUNCTION__.6213> "nouveau_pushbuf_data") at assert.c:101
#4 0x00007fffe1d76284 in nouveau_pushbuf_data (push=push@entry=0x598d40, bo=0x5ace30, offset=115624, length=20)
at ../../nouveau/pushbuf.c:726
#5 0x00007fffe1d761cb in nouveau_pushbuf_data (push=push@entry=0x598d40, bo=bo@entry=0x0, offset=offset@entry=0,
length=length@entry=0) at ../../nouveau/pushbuf.c:718
#6 0x00007fffe1d762ea in pushbuf_submit (push=push@entry=0x598d40, chan=<optimized out>, chan=<optimized out>)
at ../../nouveau/pushbuf.c:329
#7 0x00007fffe1d7656e in pushbuf_flush (push=push@entry=0x598d40) at ../../nouveau/pushbuf.c:404
#8 0x00007fffe1d77180 in nouveau_pushbuf_kick (push=0x598d40, chan=<optimized out>) at ../../nouveau/pushbuf.c:778
#9 0x00007fffe246d766 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
#10 0x00007fffe2182024 in ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so
<snip>
#15 0x00007ffff1cda345 in glXMakeCurrentReadSGI () from /usr/lib/x86_64-linux-gnu/libGL.so.1
```https://gitlab.freedesktop.org/mesa/mesa/-/issues/1079witcher 2 glitches a lot2019-09-18T20:40:20ZBugzilla Migration Userwitcher 2 glitches a lot## Submitted by Karol Herbst `@karolherbst`
Assigned to **Nouveau Project**
**[Link to original bug (#91310)](https://bugs.freedesktop.org/show_bug.cgi?id=91310)**
## Description
Created attachment 117061
screenshot showing the gl...## Submitted by Karol Herbst `@karolherbst`
Assigned to **Nouveau Project**
**[Link to original bug (#91310)](https://bugs.freedesktop.org/show_bug.cgi?id=91310)**
## Description
Created attachment 117061
screenshot showing the glitches
In the Load game menu and inside the game witcher 2 glitchers a lot.
sadly I can't create an apitrace, because the game crashes with MESA_EXTENSION_OVERRIDE=-GL_ARB_buffer_storage and setting vb_dirty = 1 and cb_dirty = 1 doesn't help (in nvc0_vbo.c:nvc0_draw_vbo)
It works with intel.
All settings set to minimum.
**Attachment 117061**, "screenshot showing the glitches":
![powermizer3](/uploads/839297f2fbc43afe4c820b6f0c1eecfc/powermizer3.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1078Axis Game Factory v3.0 (native) renders black ground2019-09-18T20:40:17ZBugzilla Migration UserAxis Game Factory v3.0 (native) renders black ground## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91306)](https://bugs.freedesktop.org/show_bug.cgi?id=91306)**
## Description
Created attachment 117057
screenshot, comparison (nouveau vs. n...## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91306)](https://bugs.freedesktop.org/show_bug.cgi?id=91306)**
## Description
Created attachment 117057
screenshot, comparison (nouveau vs. nvidia)
The application runs natively on Linux, I tested the demo version on Steam.
The demo contains some example sceneries, all of them have the same problem: terrain objects (rocks, vegetation) are rendered properly, but ground textures are black.
Disabling shader optimization doesn't help.
Ground looks OK with the llvmpipe driver/ Nvidia binary drivers.
Tested and reproduced in Mesa 10.1 and 10.4 as well.
Trace file:
https://drive.google.com/open?id=0B-tTbLKBl-tOQ25kNE80VjY3alk
VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) (prog-if 00 [VGA controller])
Mesa from git
Kernel 4.1.2
Fedora 22 32-bit
**Attachment 117057**, "screenshot, comparison (nouveau vs. nvidia)":
![AGF_screenshot](/uploads/dcdfe72dfc527d4f716f86170d959f0e/AGF_screenshot.png)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1077[NVA8] VDPAU only works when debug is on2019-09-18T20:40:14ZBugzilla Migration User[NVA8] VDPAU only works when debug is on## Submitted by zippy
Assigned to **Nouveau Project**
**[Link to original bug (#91229)](https://bugs.freedesktop.org/show_bug.cgi?id=91229)**
## Description
if i boot with 'nouveau.debug=debug', VDPAU works flawlessly for all supp...## Submitted by zippy
Assigned to **Nouveau Project**
**[Link to original bug (#91229)](https://bugs.freedesktop.org/show_bug.cgi?id=91229)**
## Description
if i boot with 'nouveau.debug=debug', VDPAU works flawlessly for all supported codecs. however, if i boot without it and try to play any video with VDPAU, my system slows down to a crawl. if i take too long to stop playback or to kill the offending program, i lose control of the system and i am forced to reboot.
i haven't experimented with other kernel parameters yet. any suggestions ?
GeForce 210
mesa 10.5.7
kernel 4.0.5
Version: 10.5https://gitlab.freedesktop.org/mesa/mesa/-/issues/1076Space Rangers 2 (in Wine) shows only black screen2019-09-18T20:40:11ZBugzilla Migration UserSpace Rangers 2 (in Wine) shows only black screen## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91171)](https://bugs.freedesktop.org/show_bug.cgi?id=91171)**
## Description
The game starts and runs fine except that the screen remains bl...## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91171)](https://bugs.freedesktop.org/show_bug.cgi?id=91171)**
## Description
The game starts and runs fine except that the screen remains black during the intro videos and in the menu, only audio can be heard.
This is with the default OpenGL renderer in Wine. When using the legacy GDI renderer the game displays properly.
From the http://wiki.winehq.org/UsefulRegistryKeys page:
"The "gdi" option mostly exists for legacy reasons. Aside from bugs in the GL
renderer, only change this if you have a setup without OpenGL. Installing a software GL implementation is the preferred solution in that case though."
The problem doesn't occur with the binary drivers.
When using the software renderer (LIBGL_ALWAYS_SOFTWARE=1) 2 out of the 4 intro videos and the menu is displayed properly.
Trace:
https://drive.google.com/open?id=0B-tTbLKBl-tOOGEwLXMtdmt2T1U
The trace consists of only a single frame which contains >100k calls.
Fedora 22 32-bit
VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) (prog-if 00 [VGA controller])
Mesa 10.6-branchpoint-773-g1de93f9
Kernel 4.0.6-300.fc22.i686+PAE
Xorg 1.17.2
libdrm-2.4.61-3.fc22.i686
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1075[NV50/Gallium] World of Zoo (in Wine) has rendering issues2021-03-05T23:00:00ZBugzilla Migration User[NV50/Gallium] World of Zoo (in Wine) has rendering issues## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91170)](https://bugs.freedesktop.org/show_bug.cgi?id=91170)**
## Description
When the game loads to the menu the screen is scrambled with fl...## Submitted by Béla Gyebrószki
Assigned to **Nouveau Project**
**[Link to original bug (#91170)](https://bugs.freedesktop.org/show_bug.cgi?id=91170)**
## Description
When the game loads to the menu the screen is scrambled with flashing polygons.
This doesn't occur with the binary drivers (340.76) or when starting the game with the software renderer.Disabling shader optimization doesn't resolve the problem.
Screenshot:
http://imgur.com/xro8Ixr
Trace file:
https://drive.google.com/open?id=0B-tTbLKBl-tOdTJxT1o0c2dZMmc
The problem is first visible in frame #152, when the second splash screen is displayed.
Demo version is available on Steam (needs Wine to run):
http://store.steampowered.com/app/43100/
Fedora 22 32-bit
Mesa 10.6-branchpoint-773-g1de93f9
Kernel 4.0.6-300.fc22.i686+PAE
Xorg 1.17.2
libdrm-2.4.61-3.fc22.i686
Version: git