GPU VM fault in Ubuntu17.10(mesa 17.2.8,kernel 4.15)

Hi all, We have gpu VM Fault problem sometimes with newest V4.15 kernel driver and mesa V17.2.8 My gpu is Radeon Pro WX7100 There is a lot of kernel log printed like this: Jan 31 13:35:44 ubuntu kernel: [120749.990185] amdgpu 000d:31:00.0: GPU fault detected: 146 0x0608d20c Jan 31 13:35:4

How to enable Radeon Pro Duo with mesa

Hi All , Does mesa support Radeon Pro Duo? I don't know how to configure xorg.conf to use two WX7100 card of DUO , and now I can only use the first card of DUO. Installed software packages: xserver-xorg xfce4 xinit Mesa version: 17.2.8 kernel version: 4.15 Pci information: 000d:31:00.0 PCI bri

re: How to enable Radeon Pro Duo with mesa

200 FPS DRI_PRIME=0 vblank_mode=0 glxgears ATTENTION: default value of option vblank_mode overridden by environment. 19846 frames in 5.0 seconds = 3969.058 FPS How to resolve this? > On Wed, Mar 14, 2018 at 5:41 AM, Lvzhihong (ReJohn) > wrote: > Hi All , > > Does mesa support

AMD WX7100 screen display problem on AArch64 architecture server.

Hi, We met a problem on ubuntu17.10 for arm server with amdgpu(AMD RADEON PRO WX7100), we use open source driver which are integrated in ubuntu17.10. And the architecture is AArch64-linux-gnu. we install : apt-get install xserver-xorg xinit xfce4 and mesa-utils glmar

Re: AMD WX7100 screen display problem on AArch64 architecture server.

>With ShadowPrimary enabled, all normal X11 drawing is performed by the CPU, >not the GPU. >Does enabling ShadowPrimary also make OpenGL applications look correct? >If not, it's most likely a Mesa or maybe LLVM issue. Enableing ShadowPrimary, some OpenGL applications looks better. But som

Re:AMD WX7100 screen display problem on AArch64 architecture server.

>With ShadowPrimary enabled, all normal X11 drawing is performed by the CPU, >not the GPU. >Does enabling ShadowPrimary also make OpenGL applications look correct? >If not, it's most likely a Mesa or maybe LLVM issue. >>Enableing ShadowPrimary, some OpenGL applications looks better. But

x11vnc display output problem while the physical monitor display is normal.

Hi, I use x11vnc for remote control, the environment is an arm server with AMDGPU which enabled by open source driver. we start x server by : startx , and start x11vnc by : export DISPLAY=:0 & x11vnc. From the beginning, the x11vnc output and the physical monitor output is the same and

Why the vram always with WC flag even if the architecture don't support WC memory

Hi All, I have a logical question when create buffer object in the amdgpu kernel driver code. My ARM64 architecture don't support WC memory , but in the driver , the VRAM BO still set WC flags. At file: drivers/gpu/drm/amd/amdgpu/amdgpu_object.c In function amdgpu_bo_do_create , it determine

Re: Why the vram always with WC flag even if the architecture don't support WC memory

> I think it's fine. Platforms without write-combining should fall back to > normal uncacheable mappings. This is fine for VRAM, because it can't be > cacheable. But for GTT, we want to use cacheable mappings if write- > combining isn't available, because uncacheable mappings would be much slower

Re: x11vnc display output problem while the physical monitor display is normal.

As we debug into the code, we found that the calls of glreadpixels function returns a large number of pixels which value are '0'. It means that when the problem appear, the call of glreadpixels function will get wrong pixels from framebuffer. But we still confused why and when the problem will