Attachment 127759 Details for Bug 98492 – GALLIUM_DDEBUG-2

GALLIUM_DDEBUG-2

X-Plane-x86_64_256_00000000 (text/plain), 1.54 KB, created by Amarildo on 2016-11-04 14:05:04 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Amarildo

Created: 2016-11-04 14:05:04 UTC

Size: 1.54 KB

patch

obsolete

>Command: /home/amarildo/.local/share/Steam/steamapps/common/X-Plane 10/X-Plane-x86_64 --force_run 
>Driver vendor: X.Org
>Device vendor: AMD
>Device name: AMD PITCAIRN (DRM 3.9.0 / 4.7.0-1-ARCH-g841c4eb-dirty, LLVM 4.0.0)
>
>Draw call sequence # = 411703
>HW reached sequence # = 411702
>Elapsed time = 2000 ms
>
>clear:
>  buffers: 1
>  color: {f = {1.000000, 1.000000, 1.000000, 1.000000}, ui = {1065353216, 1065353216, 1065353216, 1065353216}
>  depth: 1.000000
>  stencil: 0x0
>
>
>*****************************************************************************
>Driver-specific state:
>
>
>Memory-mapped registers:
>        [1;33mGRBM_STATUS[0m <- ME0PIPE0_CMDFIFO_AVAIL = 8
>                       SRBM_RQ_PENDING = 1
>                       ME0PIPE0_CF_RQ_PENDING = 0
>                       ME0PIPE0_PF_RQ_PENDING = 0
>                       GDS_DMA_RQ_PENDING = 0
>                       DB_CLEAN = 1
>                       CB_CLEAN = 1
>                       TA_BUSY = 0
>                       GDS_BUSY = 0
>                       WD_BUSY_NO_DMA = 0
>                       VGT_BUSY = 0
>                       IA_BUSY_NO_DMA = 0
>                       IA_BUSY = 0
>                       SX_BUSY = 0
>                       WD_BUSY = 0
>                       SPI_BUSY = 0
>                       BCI_BUSY = 0
>                       SC_BUSY = 0
>                       PA_BUSY = 0
>                       DB_BUSY = 0
>                       CP_COHERENCY_BUSY = 0
>                       CP_BUSY = 0
>                       CB_BUSY = 0
>                       GUI_ACTIVE = 0
>
>
>Last 60 lines of dmesg:
>

Actions: View

Attachments on bug 98492: 127609 | 127758 | 127759

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.