mesa issueshttps://gitlab.freedesktop.org/mesa/mesa/-/issues2022-12-20T23:50:59Zhttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1163Xorg stops responding when running DRI_PRIME=1 glxgears2022-12-20T23:50:59ZBugzilla Migration UserXorg stops responding when running DRI_PRIME=1 glxgears## Submitted by Sam Morris
Assigned to **Nouveau Project**
**[Link to original bug (#107735)](https://bugs.freedesktop.org/show_bug.cgi?id=107735)**
## Description
Created attachment 141338
kernel messages
If I run 'DRI_PRIME=1 g...## Submitted by Sam Morris
Assigned to **Nouveau Project**
**[Link to original bug (#107735)](https://bugs.freedesktop.org/show_bug.cgi?id=107735)**
## Description
Created attachment 141338
kernel messages
If I run 'DRI_PRIME=1 glxgears', glxgears appears and runs normally for < 1 second. However then the screen freezes and pressing Esc to close glxgears (and other keyboard/mouse input) does not work.
Neither the kernel nor Xorg log anything when this happens.
If I run 'DRI_PRIME=1 timeout 5 glxgears', after 5 seconds SIGTERM is sent to the process, it exits and Xorg stops being frozen.
The really weird thing is that if I leave an instance of glxgears (using the integrated graphics) running at the same time, then glxgears using the discrete GPU does not cause Xorg to freeze up at all!
This is on a Lenovo P50 with the following setup:
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2)
I'm using debian unstable.
Mesa version: 18.1.6
nouveau version: 1.0.15
Kernel: Linux version 4.17.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-28)) #1 SMP Debian 4.17.17-1 (2018-08-18)
I've seen this with earlier kernels too.
**Attachment 141338**, "kernel messages":
[dmesg](/uploads/b1dd0fec2e20352a4b78b37993725729/dmesg)
Version: 18.1https://gitlab.freedesktop.org/mesa/mesa/-/issues/1161regression in thermal management of Quadro FX 15002021-03-05T23:10:19ZBugzilla Migration Userregression in thermal management of Quadro FX 1500## Submitted by Thomas Blume
Assigned to **Nouveau Project**
**[Link to original bug (#107447)](https://bugs.freedesktop.org/show_bug.cgi?id=107447)**
## Description
Created attachment 140926
dmesg kernel 4.4
On my machine with a...## Submitted by Thomas Blume
Assigned to **Nouveau Project**
**[Link to original bug (#107447)](https://bugs.freedesktop.org/show_bug.cgi?id=107447)**
## Description
Created attachment 140926
dmesg kernel 4.4
On my machine with an:
```
Model: "nVidia Quadro FX 1500"
Vendor: pci 0x10de "nVidia Corporation"
Device: pci 0x029e "Quadro FX 1500"
SubVendor: pci 0x10de "nVidia Corporation"
SubDevice: pci 0x032c
Revision: 0xa1
Driver: "nouveau"
Driver Modules: "drm"
```
graphics card, the gpu fan start running at high load.
The issue started after installing openSUSE Leap15 with kernel version 4.12.
The same issue is visible using kernel version 4.17.
It was working fine on older openSUSE versions, up to kernel version 4.4.
Installing kernel version 4.4 on Leap 15 makes the issue go away.
The nouveau driver debug logs show when booting with kernel 4.12:
```
grep therm /mnt/dmesg-4_12.txt
[ 5.985658] nouveau 0000:01:00.0: therm: FAN control: PWM
[ 5.985667] nouveau 0000:01:00.0: therm: parsing the fan table failed
[ 5.985680] nouveau 0000:01:00.0: therm: fan management: automatic
[ 5.985687] nouveau 0000:01:00.0: therm: FAN target request: 90%
[ 5.985692] nouveau 0000:01:00.0: therm: FAN target: 90
[ 5.985697] nouveau 0000:01:00.0: therm: FAN update: 23
[ 5.985707] nouveau 0000:01:00.0: therm: internal sensor: yes
[ 6.005559] nouveau 0000:01:00.0: therm: programmed thresholds [ 90(3), 95(3), 130(2), 135(5) ]
[ 6.485750] nouveau 0000:01:00.0: therm: FAN update: 26
[ 6.985841] nouveau 0000:01:00.0: therm: FAN update: 29
[ 7.485929] nouveau 0000:01:00.0: therm: FAN update: 32
[ 7.986009] nouveau 0000:01:00.0: therm: FAN update: 35
[ 8.486100] nouveau 0000:01:00.0: therm: FAN update: 38
[ 8.986193] nouveau 0000:01:00.0: therm: FAN update: 41
[ 9.486270] nouveau 0000:01:00.0: therm: FAN update: 44
[ 9.987905] nouveau 0000:01:00.0: therm: FAN update: 47
[ 10.489188] nouveau 0000:01:00.0: therm: FAN update: 50
[ 10.990485] nouveau 0000:01:00.0: therm: FAN update: 53
[ 11.491779] nouveau 0000:01:00.0: therm: FAN update: 56
[ 11.993032] nouveau 0000:01:00.0: therm: FAN update: 59
[ 12.494276] nouveau 0000:01:00.0: therm: FAN update: 62
[ 12.995621] nouveau 0000:01:00.0: therm: FAN update: 65
[ 13.497070] nouveau 0000:01:00.0: therm: FAN update: 68
[ 13.998516] nouveau 0000:01:00.0: therm: FAN update: 71
[ 14.500055] nouveau 0000:01:00.0: therm: FAN update: 74
[ 15.001850] nouveau 0000:01:00.0: therm: FAN update: 77
[ 15.505237] nouveau 0000:01:00.0: therm: FAN update: 80
[ 16.006924] nouveau 0000:01:00.0: therm: FAN update: 83
[ 16.508429] nouveau 0000:01:00.0: therm: FAN update: 86
[ 17.009946] nouveau 0000:01:00.0: therm: FAN update: 89
[ 17.511480] nouveau 0000:01:00.0: therm: FAN update: 90
```
with kernel 4.4 it only shows:
```
grep therm /mnt/dmesg-4_4.txt
[ 7.547113] nouveau 0000:01:00.0: therm: FAN control: PWM
[ 7.547117] nouveau 0000:01:00.0: therm: parsing the fan table failed
[ 7.547121] nouveau 0000:01:00.0: therm: fan management: automatic
[ 7.547124] nouveau 0000:01:00.0: therm: internal sensor: yes
[ 7.566971] nouveau 0000:01:00.0: therm: programmed thresholds [ 90(3), 95(3), 130(2), 135(5) ]
```
Attaching dmesg with noveau debug logs for kernel 4.4. and kernel 4.12.
**Attachment 140926**, "dmesg kernel 4.4":
[dmesg-4_4.txt](/uploads/bb15a88916384d941a254b3d51e515be/dmesg-4_4.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1152Freeze when playing videos in WebKit2023-03-30T09:44:10ZBugzilla Migration UserFreeze when playing videos in WebKit## Submitted by Link Dupont
Assigned to **Nouveau Project**
**[Link to original bug (#105525)](https://bugs.freedesktop.org/show_bug.cgi?id=105525)**
## Description
Created attachment 138134
Epiphany/WebKit logs
My Wayland deskto...## Submitted by Link Dupont
Assigned to **Nouveau Project**
**[Link to original bug (#105525)](https://bugs.freedesktop.org/show_bug.cgi?id=105525)**
## Description
Created attachment 138134
Epiphany/WebKit logs
My Wayland desktop session freezes when I load a web video (for example, YouTube) in a WebKitProcess Epiphany.
== Steps to Reproduce ==
1. Log into a Wayland session
2. Launch Epiphany
3. Load a youtube.com video
== Expected Results ==
The video plays.
== Actual Results ==
The desktop freezes until I remotely connect to the computer over SSH and kill the WebKitProcess process rendering the content.
== Notes ==
This can be avoided by running epiphany with WEBKIT_DISABLE_COMPOSITING_MODE=1 set, which leads me to believe it is a nouveau bug (rather than a WebKit bug). I've attached logs with Epiphany output. These two lines are particularly concerning:
> Mar 15 07:20:03 bant org.gnome.Epiphany.desktop[14459]: WebKitWebProcess: pushbuf.c:727: nouveau_pushbuf_data: Assertion `kref' failed.
> Mar 15 07:20:16 bant org.gnome.Epiphany.desktop[14459]: nouveau: kernel rejected pushbuf: Device or resource busy
=== mesa version ===
mesa-dri-drivers.i686 17.3.6-1.fc27 @updates
mesa-dri-drivers.x86_64 17.3.6-1.fc27 @updates
mesa-filesystem.i686 17.3.6-1.fc27 @updates
mesa-filesystem.x86_64 17.3.6-1.fc27 @updates
mesa-libEGL.x86_64 17.3.6-1.fc27 @updates
mesa-libGL.x86_64 17.3.6-1.fc27 @updates
mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora
mesa-libOpenCL.x86_64 17.3.6-1.fc27 @updates
mesa-libgbm.x86_64 17.3.6-1.fc27 @updates
mesa-libglapi.i686 17.3.6-1.fc27 @updates
mesa-libglapi.x86_64 17.3.6-1.fc27 @updates
mesa-libwayland-egl.x86_64 17.3.6-1.fc27 @updates
mesa-libwayland-egl-devel.x86_64 17.3.6-1.fc27 @updates
mesa-libxatracker.x86_64 17.3.6-1.fc27 @updates
=== NVIDIA card ===
$ lspci | grep NV
01:00.0 VGA compatible controller: NVIDIA Corporation GK104M [GeForce GTX 775M Mac Edition] (rev a1)
**Attachment 138134**, "Epiphany/WebKit logs":
[epiphany_nouveau.log](/uploads/d7d2ca4f62a14265c5d6b382c3581f58/epiphany_nouveau.log)
Version: 17.3https://gitlab.freedesktop.org/mesa/mesa/-/issues/1146[G96, 9500 GT] Removing nouveau module results in BUG: unable to handle kerne...2021-03-05T23:05:07ZBugzilla Migration User[G96, 9500 GT] Removing nouveau module results in BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8## Submitted by Vedran Miletić
Assigned to **Nouveau Project**
**[Link to original bug (#104609)](https://bugs.freedesktop.org/show_bug.cgi?id=104609)**
## Description
Created attachment 136693
dmesg
Description of problem:
Remov...## Submitted by Vedran Miletić
Assigned to **Nouveau Project**
**[Link to original bug (#104609)](https://bugs.freedesktop.org/show_bug.cgi?id=104609)**
## Description
Created attachment 136693
dmesg
Description of problem:
Removing nouveau module using modprobe -r results in BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
Version-Release number of selected component (if applicable):
Linux 4.14.0-3-amd64 (Debian 4.14.12-2)
How reproducible:
Didn't try.
Steps to Reproduce:
1. sudo modprobe -r nouveau
2.
3.
Actual results:
```
[466017.592089] BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
[466017.592089] IP: nouveau_fbcon_fini+0xb8/0x120 [nouveau]
[466017.592089] PGD 0 P4D 0
[466017.592089] Oops: 0000 [#1] SMP NOPTI
[466017.592089] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs dm_mod cfg80211 rfkill snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iptable_filter fuse tun powernow_k8 amd64_edac_mod edac_mce_amd nouveau(-) kvm_amd kvm irqbypass mxm_wmi wmi video ppdev ttm drm_kms_helper evdev drm snd_hda_codec_realtek snd_hda_codec_generic i2c_algo_bit snd_hda_intel serio_raw snd_hda_codec pcspkr snd_hda_core k8temp snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_timer sg snd soundcore parport_pc shpchp parport asus_atk0110 button binfmt_misc sunrpc loop ecryptfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 fscrypto ecb crypto_simd cryptd glue_helper aes_x86_64 uas usb_storage hid_generic usbhid hid btrfs zstd_decompress zstd_compress xxhash sr_mod cdrom
[466017.592089] raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor sd_mod raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod ata_generic psmouse r8169 via_rhine mii uhci_hcd ehci_pci ehci_hcd i2c_viapro sata_via pata_via usbcore libata usb_common scsi_mod floppy
[466017.592089] CPU: 1 PID: 26532 Comm: modprobe Not tainted 4.14.0-3-amd64 #1 Debian 4.14.12-2
[466017.592089] Hardware name: stem manufacturer System Product Name/M2VTVM-VM890, BIOS 1201 03/17/2008
[466017.592089] task: ffff89b926dfc100 task.stack: ffffaae4c324c000
[466017.592089] RIP: 0010:nouveau_fbcon_fini+0xb8/0x120 [nouveau]
[466017.592089] RSP: 0018:ffffaae4c324fdb8 EFLAGS: 00010282
[466017.592089] RAX: 0000000000000000 RBX: ffff89b97b7ff800 RCX: fffff31601e3815f
[466017.592089] RDX: 000000000000003b RSI: ffff89b97c3c3680 RDI: 0000000000000282
[466017.592089] RBP: ffff89b97b062000 R08: 0000000000000002 R09: ffff89b976db8540
[466017.592089] R10: ffffaae4c324fdb8 R11: 0000000000000001 R12: 0000000000000000
[466017.592089] R13: ffffffffc0d52770 R14: ffff89b97cab4100 R15: ffffffffc0d527e8
[466017.592089] FS: 00007fc9e0352540(0000) GS:ffff89b97fd00000(0000) knlGS:0000000000000000
[466017.592089] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[466017.592089] CR2: 00000000000000b8 CR3: 0000000029b5e000 CR4: 00000000000006e0
[466017.592089] Call Trace:
[466017.592089] nouveau_drm_unload+0x37/0xd0 [nouveau]
[466017.592089] drm_dev_unregister+0x3c/0xe0 [drm]
[466017.592089] drm_put_dev+0x2e/0x60 [drm]
[466017.592089] nouveau_drm_device_remove+0x44/0x70 [nouveau]
[466017.592089] pci_device_remove+0x36/0xb0
[466017.592089] device_release_driver_internal+0x157/0x210
[466017.592089] driver_detach+0x39/0x70
[466017.592089] bus_remove_driver+0x51/0xd0
[466017.592089] pci_unregister_driver+0x2a/0xa0
[466017.592089] nouveau_drm_exit+0x15/0x1c5 [nouveau]
[466017.592089] SyS_delete_module+0x18c/0x290
[466017.592089] system_call_fast_compare_end+0xc/0x6f
[466017.592089] RIP: 0033:0x7fc9dfefcad7
[466017.592089] RSP: 002b:00007ffea4c86a38 EFLAGS: 00000206
[466017.592089] Code: e8 6e 59 f4 ff 48 8d bb 10 01 00 00 e8 62 59 f4 ff 48 8b 9d a0 09 00 00 4c 8b 23 48 89 df e8 30 eb d2 ff 48 89 df e8 58 f2 d2 ff `<49>` 8b bc 24 b8 00 00 00 48 85 ff 74 31 49 8d b4 24 c0 00 00 00
[466017.592089] RIP: nouveau_fbcon_fini+0xb8/0x120 [nouveau] RSP: ffffaae4c324fdb8
[466017.592089] CR2: 00000000000000b8
[466017.596375] ---[ end trace e8cb85440e5df03c ]---
```
Expected results:
No error.
Additional info:
02:00.0 VGA compatible controller [0300]: NVIDIA Corporation G96 [GeForce 9500 GT] [10de:0640] (rev a1)
**Attachment 136693**, "dmesg":
[file_104609.txt](/uploads/dc9970bc45209090b22579abc466326d/file_104609.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/11443D renering results in a distorted frame.2021-03-05T18:35:23ZBugzilla Migration User3D renering results in a distorted frame.## Submitted by Ilya
Assigned to **Nouveau Project**
**[Link to original bug (#103764)](https://bugs.freedesktop.org/show_bug.cgi?id=103764)**
## Description
Starting glxgears results in one static distorted frame. But the program...## Submitted by Ilya
Assigned to **Nouveau Project**
**[Link to original bug (#103764)](https://bugs.freedesktop.org/show_bug.cgi?id=103764)**
## Description
Starting glxgears results in one static distorted frame. But the programs continues to run and outputs in the console, that the frames are drawn. No error reports occure.
Hardware:
01:00.0 VGA compatible controller: NVIDIA Corporation G72M [Quadro NVS 110M/GeForce Go 7300] (rev a1)
Version: 17.0https://gitlab.freedesktop.org/mesa/mesa/-/issues/1143[GM107] reboot/suspend/lspci hang with nouveau2019-09-21T17:43:12ZBugzilla Migration User[GM107] reboot/suspend/lspci hang with nouveau## Submitted by Laurentiu Nicola
Assigned to **Nouveau Project**
**[Link to original bug (#103409)](https://bugs.freedesktop.org/show_bug.cgi?id=103409)**
## Description
Created attachment 134998
dmesg log
I have an ASUS ROG lapt...## Submitted by Laurentiu Nicola
Assigned to **Nouveau Project**
**[Link to original bug (#103409)](https://bugs.freedesktop.org/show_bug.cgi?id=103409)**
## Description
Created attachment 134998
dmesg log
I have an ASUS ROG laptop (GL752V) with dual graphics. I've just installed Linux and GNOME seems to pick the Intel card by default, but the nouveau module still gets loaded.
The issue is that I can't power off, reboot or suspend the laptop. On reboot and power off it hangs with a "watchdog0 did not stop" message on the console. I also noticed that simply running lspci hangs in uninterruptible sleep.
Blacklisting the nouveau driver fixes all these issues.
**Attachment 134998**, "dmesg log":
[dmesg.txt](/uploads/b032d89e7b531d283641beb44ceca67d/dmesg.txt)
Version: 17.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1141Nouveau fails when booting with a screen connected to displayport since 13a86...2021-03-05T20:02:47ZBugzilla Migration UserNouveau fails when booting with a screen connected to displayport since 13a86519202c5d119d83640d6f781f3181205d2c## Submitted by Chris Glass
Assigned to **Nouveau Project**
**[Link to original bug (#103351)](https://bugs.freedesktop.org/show_bug.cgi?id=103351)**
## Description
As discovered when testing the latest release of Ubuntu with (mai...## Submitted by Chris Glass
Assigned to **Nouveau Project**
**[Link to original bug (#103351)](https://bugs.freedesktop.org/show_bug.cgi?id=103351)**
## Description
As discovered when testing the latest release of Ubuntu with (mainline) trees, commit 13a86519202c5d119d83640d6f781f3181205d2c seems to introduce a regression when booting with a screen attached to displayport (the system otherwise boots fine with the same kernel using an HDMI output).
An original bug was filed with the Ubuntu bug tracker and contains information about bissection: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619
A (set of) dmesg outputs can be found here: https://pastebin.ubuntu.com/25767385/
4.14-rc5 still exhibits this behavior on the tested system.
Please don't hesitate to reach out to me should you need more information - one affected system happens to be my main workstation.https://gitlab.freedesktop.org/mesa/mesa/-/issues/1128[NV4C] System crashes reliably with glxinfo2021-03-05T20:00:59ZBugzilla Migration User[NV4C] System crashes reliably with glxinfo## Submitted by Dave Odell
Assigned to **Nouveau Project**
**[Link to original bug (#99968)](https://bugs.freedesktop.org/show_bug.cgi?id=99968)**
## Description
Created attachment 129920
Example display corruption
+++ This bug w...## Submitted by Dave Odell
Assigned to **Nouveau Project**
**[Link to original bug (#99968)](https://bugs.freedesktop.org/show_bug.cgi?id=99968)**
## Description
Created attachment 129920
Example display corruption
+++ This bug was initially created as a clone of Bug #91992 +++
Hardware is NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) on an old Dell Inspiron 531. Integrated graphics.
The system boots OK (with high-resolution console) into X11. I can log in to a Lubuntu desktop (2D, no OpenGL, AFAIK). Then, from a terminal window I run:
$ while true; do nice -n19 glxinfo > /dev/null; done
Then I drag the window around for a few seconds. Then the entire system crashes: total system lockup, followed by display corruption a second or two later. (I've attached a photograph, because I can't take a normal screen shot.) No Ctrl-Alt-F1, no magic SysRq, no ping response.
Other OpenGL apps (i.e. glxgears) can run...sometimes. Other times, they crash the same way. It seems to happen on GL init.
Ubuntu 16.10 (with Lubuntu Desktop)
Linux kernel 4.10.0 (freshly compiled)
libdrm 2.4.70-1 (from distro)
Mesa 12.0.3-1ubuntu2 (from distro)
xf86-video-nouveau 1:1.0.12-2 (from distro)
This seems a lot like [bug 91992](https://bugs.freedesktop.org/show_bug.cgi?id=91992), but I've got my video memory cranked up to 256 MB in the BIOS settings, and it still happens.
**Attachment 129920**, "Example display corruption":
![IMG_20170225_180139765](/uploads/a741d63bf1e10e263dc8be89348a7cb0/IMG_20170225_180139765.jpg)
Version: 12.0
### Depends on
* [Bug 91992](https://bugs.freedesktop.org/show_bug.cgi?id=91992)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1126XVMC on nv43 class card broken with recent mesa + kernel.2021-03-05T19:50:02ZBugzilla Migration UserXVMC on nv43 class card broken with recent mesa + kernel.## Submitted by Andrew Randrianasulu
Assigned to **Nouveau Project**
**[Link to original bug (#99584)](https://bugs.freedesktop.org/show_bug.cgi?id=99584)**
## Description
Hello again.
Not sure if anyone will look into this, but ...## Submitted by Andrew Randrianasulu
Assigned to **Nouveau Project**
**[Link to original bug (#99584)](https://bugs.freedesktop.org/show_bug.cgi?id=99584)**
## Description
Hello again.
Not sure if anyone will look into this, but I run into bug where xvmc state tracker/nouveau failed for me in multiple ways, depending on exact kernel/mesa combination.
With kernel 4.2.0 new mesa (Mesa 17.1.0-devel git-12dcad1) compiled agains recent libdrm (d4b8344363b4e0f0e831e5722b6df5cc0bb08df8
Author: Chad Versace <chadversary@chromium.org>
Date: Fri Jan 27 12:18:00 2017 -0800
Bump version for 2.4.75 release)
produces pink window.
With more mdoern kernel (4.10-rc5). whole device creation failed.
Test commandline:
/home/guest/src/mesa/src/gallium/state_trackers/xvmc/tests/xvmc_bench
result:
Acceleration level: IDCT
Creation failed: No such device (-19)
xvmc_bench: tests/xvmc_bench.c:238: main: Assertion `XvMCCreateContext(display, port_num, surface_type_id, config.input_width, config.input_height, 0x00000001, &context) == 0' failed.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1125openmw - Segfault with the nouveau ddx + DRI32022-11-23T21:43:37ZBugzilla Migration Useropenmw - Segfault with the nouveau ddx + DRI3## Submitted by orb..@..lev.dk
Assigned to **Nouveau Project**
**[Link to original bug (#99464)](https://bugs.freedesktop.org/show_bug.cgi?id=99464)**
## Description
Created attachment 129055
Apitrace.
When starting openmw which ...## Submitted by orb..@..lev.dk
Assigned to **Nouveau Project**
**[Link to original bug (#99464)](https://bugs.freedesktop.org/show_bug.cgi?id=99464)**
## Description
Created attachment 129055
Apitrace.
When starting openmw which is the free engine re-implementation of the game morrowind it will segfault. This may be a mesa core bug, but it will only happen with the nouveau DDX + DRI3. It will not crash with modesetting + DRI3, DRI2 or the llvmpipe.
Here is a backtrace.
http://pastebin.com/HMdv4iWb
Apitrace log.
http://pastebin.com/FzZVyGqW
Here is a workaround as reported to the the mesa mailing list by Tobias Klausmann. It successfully hides the crash, but potentially breaking the hardware cursor used by openmw which works correctly with DRI2, modesetting or the llvmpipe. It also was not intended as a real fix.
"OpenMW tries to upload a new surface (mouse pointer) which fails in the now
guarded update_framebuffer_size() as the surface is NULL.
This is not inteded as a real "fix", as it would just hide the immediate crash.
So if somebody could take a look at this...
Reported-by: <ovariegata@yahoo.com>
Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann@mni.thm.de>
---
src/mesa/state_tracker/st_atom_framebuffer.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/src/mesa/state_tracker/st_atom_framebuffer.c b/src/mesa/state_tracker/st_atom_framebuffer.c
index ea41d9d..3ee4ea5 100644
--- a/src/mesa/state_tracker/st_atom_framebuffer.c
+++ b/src/mesa/state_tracker/st_atom_framebuffer.c
@@ -177,8 +177,10 @@ update_framebuffer_state( struct st_context *st )
/* rendering to a GL texture, may have to update surface */
st_update_renderbuffer_surface(st, strb);
}
- pipe_surface_reference(&framebuffer->zsbuf, strb->surface);
- update_framebuffer_size(framebuffer, strb->surface);
+ if (strb->surface) {
+ pipe_surface_reference(&framebuffer->zsbuf, strb->surface);
+ update_framebuffer_size(framebuffer, strb->surface);
+ }
}
else {
strb = st_renderbuffer(fb->Attachment[BUFFER_STENCIL].Renderbuffer);
--
2.9.2"
**Attachment 129055**, "Apitrace.":
[openmw_nouveau_dri3.trace.xz](/uploads/66f7c6188bfa51bcccf2889a9e7d25f6/openmw_nouveau_dri3.trace.xz)
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1124[nouveau] garbled rendering with glamor on G712019-09-19T14:39:30ZBugzilla Migration User[nouveau] garbled rendering with glamor on G71## Submitted by Olivier Fourdan `@ofourdan`
Assigned to **Nouveau Project**
**[Link to original bug (#99400)](https://bugs.freedesktop.org/show_bug.cgi?id=99400)**
## Description
Created attachment 128933
Screenshot of the issue
...## Submitted by Olivier Fourdan `@ofourdan`
Assigned to **Nouveau Project**
**[Link to original bug (#99400)](https://bugs.freedesktop.org/show_bug.cgi?id=99400)**
## Description
Created attachment 128933
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
**Attachment 128933**, "Screenshot of the issue":
![glamor-nouveau-g71](/uploads/713cff550faa5940b9bd1d58497fcacc/glamor-nouveau-g71.png)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1106Missrendering of Reflections in Talos Principle2019-09-19T11:24:43ZBugzilla Migration UserMissrendering of Reflections in Talos Principle## Submitted by Karol Herbst `@karolherbst`
Assigned to **Nouveau Project**
**[Link to original bug (#96443)](https://bugs.freedesktop.org/show_bug.cgi?id=96443)**
## Description
With the Performance settings "cpu settings > mirro...## Submitted by Karol Herbst `@karolherbst`
Assigned to **Nouveau Project**
**[Link to original bug (#96443)](https://bugs.freedesktop.org/show_bug.cgi?id=96443)**
## Description
With the Performance settings "cpu settings > mirror reflections" enabled, the sky reflection on the water is broken.
Traces are useless here, because the issue is somehow consistent on other drivers as well, but don't show there if the game runs on them.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1103lockup on kde startup2022-12-20T23:39:17ZBugzilla Migration Userlockup on kde startup## Submitted by Martin Bednar
Assigned to **Nouveau Project**
**[Link to original bug (#95351)](https://bugs.freedesktop.org/show_bug.cgi?id=95351)**
## Description
Created attachment 123619
complete dmesg when hung
lspci:
01:00....## Submitted by Martin Bednar
Assigned to **Nouveau Project**
**[Link to original bug (#95351)](https://bugs.freedesktop.org/show_bug.cgi?id=95351)**
## Description
Created attachment 123619
complete dmesg when hung
lspci:
01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [NVS 300] (rev a2)
On plasma5 (5.6) session startup, the entire GUI freezes (except cursor, that still moves). Always before plasma initializes.
reproducible every time.
~~**Attachment 123619**~~, "complete dmesg when hung":
[dmesg.nouveau](/uploads/70b2642f488c5aa3be7fa2d11c8b66d3/dmesg.nouveau)
Version: 11.2https://gitlab.freedesktop.org/mesa/mesa/-/issues/1099[NV30/NV40] nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref` failed.2021-03-05T19:41:43ZBugzilla Migration User[NV30/NV40] nouveau/pushbuf.c:238: pushbuf_krel: Assertion `bkref` failed.## Submitted by Severin Pappadeux
Assigned to **Nouveau Project**
**[Link to original bug (#94727)](https://bugs.freedesktop.org/show_bug.cgi?id=94727)**
## Description
Linux, Lubuntu 16.04 beta2, x64 on Intel CPU, NVIDIA Quadro 1...## Submitted by Severin Pappadeux
Assigned to **Nouveau Project**
**[Link to original bug (#94727)](https://bugs.freedesktop.org/show_bug.cgi?id=94727)**
## Description
Linux, Lubuntu 16.04 beta2, x64 on Intel CPU, NVIDIA Quadro 1500M
Multithreaded OpenGL application (C++, Geant4 toolkit, 3D visualisation)
Failed to start with the message in Subj. Application is working in VMware, same Linux version, on top of Windows 10https://gitlab.freedesktop.org/mesa/mesa/-/issues/1087Segfault in pushbuf_kref on nv50 when rendering from multiple threads2023-07-31T13:24:36ZBugzilla Migration UserSegfault in pushbuf_kref on nv50 when rendering from multiple threads## Submitted by Gabriele Svelto
Assigned to **Nouveau Project**
**[Link to original bug (#92438)](https://bugs.freedesktop.org/show_bug.cgi?id=92438)**
## Description
Created attachment 118838
kernel log
I've encountered an easil...## Submitted by Gabriele Svelto
Assigned to **Nouveau Project**
**[Link to original bug (#92438)](https://bugs.freedesktop.org/show_bug.cgi?id=92438)**
## Description
Created attachment 118838
kernel log
I've encountered an easily reproducible segfault using the Firefox OS emulator while I was hacking the said operating. The Firefox OS emulator [1] is a fork of the Android emulator which is in turn a fork of qemu. In both cases the graphics part is untouched so it might be possible to reproduce the same issue in qemu even though I didn't have the time to try it.
Here's my full STR:
1) Build the Firefox OS emulator using the emulator-x86-kk target device ( git clone https://github.com/mozilla-b2g/B2G.git ; cd B2G ; ./config.sh emulator-x86-kk ; ./build.sh )
2) Launch it from the tree using the run-emulator.sh script
3) Once Firefox OS has started quickly click on any application and keep clicking on buttons / input boxes / etc... The segfault will normally happen in a matter of seconds
I've reproduced the bug both on Fedora 22 and Gentoo so it doesn't look like distro-specific, these are the versions number taken from my Gentoo installation:
xf86-video-nouveau 1.0.11
libdrm 2.4.59
mesa 10.3.7
xorg-server 1.16.4
kernel 4.0.5
I've captured a stack trace of the segfault with gdb:
```
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xc3dfeb40 (LWP 9387)]
0xf689a323 in pushbuf_kref () from /usr/lib32/libdrm_nouveau.so.2
(gdb) bt
#0 0xf689a323 in pushbuf_kref () from /usr/lib32/libdrm_nouveau.so.2
#1 0xf689ab9f in pushbuf_validate () from /usr/lib32/libdrm_nouveau.so.2
#2 0xf6ce47e8 in nv50_state_validate () from /usr/lib32/dri/nouveau_dri.so
#3 0xf6cf0a49 in nv50_draw_vbo () from /usr/lib32/dri/nouveau_dri.so
#4 0xf6b3846d in cso_draw_vbo () from /usr/lib32/dri/nouveau_dri.so
#5 0xf6a5f29e in st_draw_vbo () from /usr/lib32/dri/nouveau_dri.so
#6 0xf6a30cd3 in vbo_draw_arrays () from /usr/lib32/dri/nouveau_dri.so
#7 0xf6a30f37 in vbo_exec_DrawArrays () from /usr/lib32/dri/nouveau_dri.so
#8 0xf72ca52b in glDrawArrays (mode=4, first=0, count=6) at sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:576
#9 0xf74b9965 in gl2_decoder_context_t::decode (this=0xc3dfdfd4, buf=0xc47ff008, len=5452, stream=0xc6400768)
at out/host/linux-x86/obj/STATIC_LIBRARIES/libGLESv2_dec_intermediates/gl2_dec.cpp:565
#10 0xf74b662c in RenderThread::Main (this=0xc6400788) at sdk/emulator/opengl/host/libs/libOpenglRender/RenderThread.cpp:128
#11 0xf74cdc3d in osUtils::Thread::thread_main (p_arg=0xc6400788) at sdk/emulator/opengl/shared/OpenglOsUtils/osThreadUnix.cpp:83
#12 0xf7f9711f in start_thread () from /lib32/libpthread.so.0
#13 0xf7d5f79e in clone () from /lib32/libc.so.6
```
I'm attaching the kernel log and the X log. Those may be "polluted" by other stuff as my machine has been running for some time since I've hit the bug. I'll try to provide cleaner ones right after I hit the bug. If more detailed information is needed (e.g. a backtrace with finer-grained debug information, etc...) I can provide it given some time to gather it.
[1] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Using_the_B2G_emulators
~~**Attachment 118838**~~, "kernel log":
[dmesg.log](/uploads/6ff7cd88b70339b3882b96553a6be15d/dmesg.log)
Version: 11.0
### Depends on
* [Bug 92077](https://bugs.freedesktop.org/show_bug.cgi?id=92077)
### See also
* https://launchpad.net/bugs/1553328https://gitlab.freedesktop.org/mesa/mesa/-/issues/104719.2.0_rc1 fails lp_test_arit, u_format_test, PIPE_FORMAT_DXT5_RGBA (unorm8)2021-07-16T20:19:52ZBugzilla Migration User19.2.0_rc1 fails lp_test_arit, u_format_test, PIPE_FORMAT_DXT5_RGBA (unorm8)## Submitted by erh..@..ox.org
Assigned to **mes..@..op.org**
**[Link to original bug (#111549)](https://bugs.freedesktop.org/show_bug.cgi?id=111549)**
## Description
Created attachment 145252
Gentoo build.log.xz (19.2.0_rc1, x86)...## Submitted by erh..@..ox.org
Assigned to **mes..@..op.org**
**[Link to original bug (#111549)](https://bugs.freedesktop.org/show_bug.cgi?id=111549)**
## Description
Created attachment 145252
Gentoo build.log.xz (19.2.0_rc1, x86)
# inxi -b
System: Host: hakla04 Kernel: 5.2.11-gentoo i686 bits: 32 Console: tty 1 Distro: Gentoo Base System release 2.6
Machine: Type: Desktop System: Shuttle product: SN41V20 v: N/A serial: N/A
Mobo: Shuttle model: FN41V20 serial: N/A BIOS: Phoenix v: 6.00 PG date: 10/29/2004
CPU: Single Core: AMD Athlon XP 2600+ type: UP speed: 2080 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV350 [Radeon 9550/9600/X1050 Series] driver: radeon v: kernel
Display: tty server: X.org 1.20.5 driver: ati,radeon unloaded: modesetting tty: 132x24
Message: Advanced graphics data unavailable in console for root.
Network: Device-1: NVIDIA nForce2 Ethernet driver: forcedeth
Device-2: Qualcomm Atheros AR5212/5213/2414 Wireless Network Adapter driver: ath5k
Drives: Local Storage: total: 279.48 GiB used: 6.73 GiB (2.4%)
Info: Processes: 112 Uptime: 5h 44m Memory: 1.96 GiB used: 192.0 MiB (9.6%) Init: systemd Shell: bash inxi: 3.0.34
# lscpu
Architecture: i686
CPU op-mode(s): 32-bit
Byte Order: Little Endian
Address sizes: 34 bits physical, 32 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Vendor ID: AuthenticAMD
CPU family: 6
Model: 8
Model name: AMD Athlon(tm) XP 2600+
Stepping: 1
CPU MHz: 2079.583
BogoMIPS: 4160.46
L1d cache: 64K
L1i cache: 64K
L2 cache: 256K
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow cpuid 3dnowprefetch vmmcall
[...]
Testing PIPE_FORMAT_DXT5_RGBA (unorm8) ...
round.v1(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL
round.v1(0.5): ref = 0, out = 1, precision = -inf bits, FAIL
round.v4(-0.5): ref = -0, out = -1, precision = -inf bits, FAIL
round.v4(0.5): ref = 0, out = 1, precision = -inf bits, FAIL
[...]
Testing util_format_dxt1_rgb_unpack_rgba_8unorm ...
FAILED: {0x99, 0xb0, 0x8e, 0xff}, {0x5d, 0x62, 0x89, 0xff}, {0x99, 0xb0, 0x8e, 0xff}, {0x99, 0xb0, 0x8e, 0xff}, {0xd6, 0xff, 0x94, 0xff}, {0x5d, 0x62, 0x89, 0xff}, {0x99, 0xb0, 0x8e, 0xff}, {0xd6, 0xff, 0x94, 0xff}, {0x5d, 0x62, 0x89, 0xff}, {0x5d, 0x62, 0x89, 0xff}, {0x99, 0xb0, 0x8e, 0xff}, {0x21, 0x14, 0x84, 0xff}, {0x5d, 0x62, 0x89, 0xff}, {0x21, 0x14, 0x84, 0xff}, {0x21, 0x14, 0x84, 0xff}, {0x99, 0xb0, 0x8e, 0xff} obtained
{0x98, 0xaf, 0x8e, 0xff}, {0x5c, 0x62, 0x88, 0xff}, {0x98, 0xaf, 0x8e, 0xff}, {0x98, 0xaf, 0x8e, 0xff}, {0xd6, 0xff, 0x94, 0xff}, {0x5c, 0x62, 0x88, 0xff}, {0x98, 0xaf, 0x8e, 0xff}, {0xd6, 0xff, 0x94, 0xff}, {0x5c, 0x62, 0x88, 0xff}, {0x5c, 0x62, 0x88, 0xff}, {0x98, 0xaf, 0x8e, 0xff}, {0x21, 0x13, 0x84, 0xff}, {0x5c, 0x62, 0x88, 0xff}, {0x21, 0x13, 0x84, 0xff}, {0x21, 0x13, 0x84, 0xff}, {0x98, 0xaf, 0x8e, 0xff} expected
Testing util_format_dxt1_rgba_unpack_rgba_8unorm ...
FAILED: {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xaa, 0x90, 0xff}, {0x4e, 0xaa, 0x90, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xaa, 0x90, 0xff}, {0x29, 0xff, 0xff, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xaa, 0x90, 0xff}, {0x73, 0x55, 0x21, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xaa, 0x90, 0xff}, {0x4e, 0xaa, 0x90, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xaa, 0x90, 0xff} obtained
{0x00, 0x00, 0x00, 0x00}, {0x4e, 0xa9, 0x8f, 0xff}, {0x4e, 0xa9, 0x8f, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xa9, 0x8f, 0xff}, {0x29, 0xff, 0xff, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xa9, 0x8f, 0xff}, {0x73, 0x54, 0x21, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xa9, 0x8f, 0xff}, {0x4e, 0xa9, 0x8f, 0xff}, {0x00, 0x00, 0x00, 0x00}, {0x00, 0x00, 0x00, 0x00}, {0x4e, 0xa9, 0x8f, 0xff} expected
Testing util_format_dxt3_rgba_unpack_rgba_8unorm ...
FAILED: {0x6d, 0xc6, 0x96, 0x77}, {0x6d, 0xc6, 0x96, 0xee}, {0x6d, 0xc6, 0x96, 0xaa}, {0x8c, 0xff, 0xb5, 0x44}, {0x6d, 0xc6, 0x96, 0xff}, {0x6d, 0xc6, 0x96, 0x88}, {0x31, 0x55, 0x5a, 0x66}, {0x6d, 0xc6, 0x96, 0x99}, {0x31, 0x55, 0x5a, 0xbb}, {0x31, 0x55, 0x5a, 0x55}, {0x31, 0x55, 0x5a, 0x11}, {0x6d, 0xc6, 0x96, 0xcc}, {0x6d, 0xc6, 0x96, 0xcc}, {0x6d, 0xc6, 0x96, 0x11}, {0x31, 0x55, 0x5a, 0x44}, {0x31, 0x55, 0x5a, 0x88} obtained
{0x6c, 0xc6, 0x96, 0x77}, {0x6c, 0xc6, 0x96, 0xee}, {0x6c, 0xc6, 0x96, 0xa9}, {0x8c, 0xff, 0xb5, 0x43}, {0x6c, 0xc6, 0x96, 0xff}, {0x6c, 0xc6, 0x96, 0x87}, {0x31, 0x54, 0x5a, 0x66}, {0x6c, 0xc6, 0x96, 0x98}, {0x31, 0x54, 0x5a, 0xba}, {0x31, 0x54, 0x5a, 0x54}, {0x31, 0x54, 0x5a, 0x10}, {0x6c, 0xc6, 0x96, 0xcc}, {0x6c, 0xc6, 0x96, 0xcc}, {0x6c, 0xc6, 0x96, 0x10}, {0x31, 0x54, 0x5a, 0x43}, {0x31, 0x54, 0x5a, 0x87} expected
Testing util_format_dxt5_rgba_unpack_rgba_8unorm ...
FAILED: {0x6d, 0xc6, 0x96, 0x74}, {0x6d, 0xc6, 0x96, 0xf8}, {0x6d, 0xc6, 0x96, 0xb6}, {0x8c, 0xff, 0xb5, 0x53}, {0x6d, 0xc6, 0x96, 0xf8}, {0x6d, 0xc6, 0x96, 0x95}, {0x31, 0x55, 0x5a, 0x53}, {0x6d, 0xc6, 0x96, 0x95}, {0x31, 0x55, 0x5a, 0xb6}, {0x31, 0x55, 0x5a, 0x53}, {0x31, 0x55, 0x5a, 0x11}, {0x6d, 0xc6, 0x96, 0xd7}, {0x6d, 0xc6, 0x96, 0xb6}, {0x6d, 0xc6, 0x96, 0x11}, {0x31, 0x55, 0x5a, 0x32}, {0x31, 0x55, 0x5a, 0x95} obtained
{0x6c, 0xc6, 0x96, 0x73}, {0x6c, 0xc6, 0x96, 0xf7}, {0x6c, 0xc6, 0x96, 0xb6}, {0x8c, 0xff, 0xb5, 0x53}, {0x6c, 0xc6, 0x96, 0xf7}, {0x6c, 0xc6, 0x96, 0x95}, {0x31, 0x54, 0x5a, 0x53}, {0x6c, 0xc6, 0x96, 0x95}, {0x31, 0x54, 0x5a, 0xb6}, {0x31, 0x54, 0x5a, 0x53}, {0x31, 0x54, 0x5a, 0x10}, {0x6c, 0xc6, 0x96, 0xd7}, {0x6c, 0xc6, 0x96, 0xb6}, {0x6c, 0xc6, 0x96, 0x10}, {0x31, 0x54, 0x5a, 0x31}, {0x31, 0x54, 0x5a, 0x95} expected
[...]
49/61 mesa:llvmpipe / lp_test_arit FAIL 2.15 s (exit status 1)
56/61 mesa:gallium / u_format_test FAIL 0.29 s (exit status 1)
Ok: 59
Expected Fail: 0
Fail: 2
Unexpected Pass: 0
Skipped: 0
Timeout: 0
**Attachment 145252**, "Gentoo build.log.xz (19.2.0_rc1, x86)":
[mesa-19.2.0_rc1_20190903-120559.log.xz](/uploads/477b3d3456ac3d2571bcafd0e900bac1/mesa-19.2.0_rc1_20190903-120559.log.xz)
Version: 19.2
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=110612
* https://bugs.freedesktop.org/show_bug.cgi?id=109615
* https://bugs.freedesktop.org/show_bug.cgi?id=106644https://gitlab.freedesktop.org/mesa/mesa/-/issues/1044Random crash on amdgpu due to temperature missrepoorting2022-01-07T11:00:35ZBugzilla Migration UserRandom crash on amdgpu due to temperature missrepoorting## Submitted by Michel
Assigned to **mes..@..op.org**
**[Link to original bug (#111080)](https://bugs.freedesktop.org/show_bug.cgi?id=111080)**
## Description
Created attachment 144716
amdgpu_pm_info information from start of game...## Submitted by Michel
Assigned to **mes..@..op.org**
**[Link to original bug (#111080)](https://bugs.freedesktop.org/show_bug.cgi?id=111080)**
## Description
Created attachment 144716
amdgpu_pm_info information from start of game to crash
Hi,
I have been experiencing some random crash in dota 2 for the past 2 years.
Changed everything in the computer 6900k -> threadripper, corsaire memory -> gskill, radeon frontier -> radeon vega 7. Ubuntu 16.04 ->16.10 -> 17.04 -> 17.10 ->18.04 ->18.10 ->19.04. This is with all the mesa version in between currently on
"OpenGL renderer string: AMD Radeon VII (VEGA20, DRM 3.32.0, 5.2.0-rc7+, LLVM 9.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel - padoka PPA
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
"
All experience the same random crash.
I finally got on lead on the problem seeing the GPU reporting unrealistic values, ex: MHZ jump to 10 000 range. Around the time of the crash temperature in the logs goes from 62c to 500c within two seconds back to 62c. This I suspect would cause the GPU to apply its protection and freeze and if it was true, also violate some law of physics.
Most other tool I use to test the grapgic card, example Uningine, reports correct values within the supported range defined for the cards which are
"
#OD_VDDC_CURVE:
#0: 808Mhz 704mV
#1: 1304Mhz 777mV
#2: 1801Mhz 1054mV
#OD_RANGE:
#SCLK: 808Mhz 2200Mhz
#MCLK: 351Mhz 1200Mhz
"
Attached is an example generated with
"watch -t -n1 'cat /sys/kernel/debug/dri/1/amdgpu_pm_info|grep -A 9 "GFX Clocks" | tee -a /home/mitch/tmp/gpulog.txt'"
Example grep Temp
"
GPU Temperature: 70 C
GPU Temperature: 511 C
GPU Temperature: 69 C
"
grep \(SLCK
"
1924 MHz (SCLK)
5422 MHz (SCLK)
1999 MHz (SCLK)
"
I realize the issue might be somewhere else than the mesa driver but would like to know where this could be and if anybody else seen this kind of behaviour
Thank you very much for any help
**Attachment 144716**, "amdgpu_pm_info information from start of game to crash":
[gpulog_crash3.txt](/uploads/27151cd52a66257345ea7f21b13a563d/gpulog_crash3.txt)https://gitlab.freedesktop.org/mesa/mesa/-/issues/1043PBO unpacking is not accelerated2021-07-27T16:20:55ZBugzilla Migration UserPBO unpacking is not accelerated## Submitted by Whatcookie
Assigned to **mes..@..op.org**
**[Link to original bug (#111043)](https://bugs.freedesktop.org/show_bug.cgi?id=111043)**
## Description
While investigating performance bottlenecks with RPCS3 while using ...## Submitted by Whatcookie
Assigned to **mes..@..op.org**
**[Link to original bug (#111043)](https://bugs.freedesktop.org/show_bug.cgi?id=111043)**
## Description
While investigating performance bottlenecks with RPCS3 while using Radeonsi, I came across a scene which was only getting 1FPS, while spending 99% of the CPU time in the driver. Further investigation led to the discovery that using the GL_STREAM_COPY flag instead of GL_STATIC_COPY led to performance increasing to 11fps.
This prompted us to look into Mesa's code for an explanation, since the operation here should be moving data between GPU memory to GPU memory, and shouldn't be faster with GL_STREAM_COPY.
We came across this https://gitlab.freedesktop.org/mesa/mesa/commit/a338dc01866ce50bf7555ee8dc08491c7f63b585 which provided an explanation for why GL_STREAM_COPY was faster.
Anyways, point is we need PBO unpacking acceleration for this to be any faster. Even when using the GL_STREAM_COPY flag about 90% of the time spent in the graphics thread is spent in a single function in the driver.
Thanks.
Version: githttps://gitlab.freedesktop.org/mesa/mesa/-/issues/1041u_format_test fails on i6862021-07-16T20:19:37ZBugzilla Migration Useru_format_test fails on i686## Submitted by Marius Bakke
Assigned to **mes..@..op.org**
**[Link to original bug (#110612)](https://bugs.freedesktop.org/show_bug.cgi?id=110612)**
## Description
Created attachment 144165
Meson test log
When building Mesa 19.0...## Submitted by Marius Bakke
Assigned to **mes..@..op.org**
**[Link to original bug (#110612)](https://bugs.freedesktop.org/show_bug.cgi?id=110612)**
## Description
Created attachment 144165
Meson test log
When building Mesa 19.0.3 for i686-linux, these tests fail (from u_format_test):
Testing util_format_dxt1_rgb_unpack_rgba_8unorm ...
Testing util_format_dxt1_rgba_unpack_rgba_8unorm ...
Testing util_format_dxt3_rgba_unpack_rgba_8unorm ...
Testing util_format_dxt5_rgba_unpack_rgba_8unorm ...
Meson test log with output attached.
**Attachment 144165**, "Meson test log":
[testlog.txt](/uploads/245de1aaff860b8e37664e61d3d5ec2e/testlog.txt)
Version: 19.0
### See also
* https://bugs.freedesktop.org/show_bug.cgi?id=111549https://gitlab.freedesktop.org/mesa/mesa/-/issues/1040src/compiler/nir/nir.h : warning: type of ‘nir_get_io_offset_src’ does not ma...2020-01-24T09:35:17ZBugzilla Migration Usersrc/compiler/nir/nir.h : warning: type of ‘nir_get_io_offset_src’ does not match original declaration [-Wlto- type-mismatch]## Submitted by Fabio Pedretti
Assigned to **mes..@..op.org**
**[Link to original bug (#110611)](https://bugs.freedesktop.org/show_bug.cgi?id=110611)**
## Description
When building with LTO enabled there are 38 -Wlto-type-mismatch...## Submitted by Fabio Pedretti
Assigned to **mes..@..op.org**
**[Link to original bug (#110611)](https://bugs.freedesktop.org/show_bug.cgi?id=110611)**
## Description
When building with LTO enabled there are 38 -Wlto-type-mismatch warnings, all in src/compiler/nir/nir.h , examples:
../src/compiler/nir/nir.h:3150:10: warning: type of ‘nir_get_io_offset_src’ does not match original declaration [-Wlto-
type-mismatch]
../src/compiler/nir/nir.h:2490:22: warning: type of ‘nir_intrinsic_instr_create’ does not match original declaration [-
Wlto-type-mismatch]
Full log here:
https://launchpadlibrarian.net/422180941/buildlog_ubuntu-eoan-amd64.mesa_19.1~git1905040730.918994~oibaf~e_BUILDING.txt.gz
Version: git