Re: R7-250X: Vulkan: Doom lockups.
After applying the patches from the bug report the lockup was immediate, black screen. Jun 23 15:50:48 agartha kernel: [ 199.021303] amdgpu :01:00.0: GPU fault detected: 146 0x0b22080c Jun 23 15:50:48 agartha kernel: [ 199.021308] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00100059 Jun 23 15:50:48 agartha kernel: [ 199.021310] amdgpu :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0200800C Jun 23 15:50:48 agartha kernel: [ 199.021313] amdgpu :01:00.0: VM fault (0x0c, vmid 1) at page 1048665, read from '' (0x) (8) Jun 23 15:53:33 agartha kernel: [ 363.707517] INFO: task Xorg:952 blocked for more than 120 seconds. Jun 23 15:53:33 agartha kernel: [ 363.707522] Not tainted 4.11.0-trunk-amd64 #1 Debian 4.11.3-1~exp1~cheako0~artful0 Jun 23 15:53:33 agartha kernel: [ 363.707524] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 23 15:53:33 agartha kernel: [ 363.707525] XorgD0 952950 0x0004 Jun 23 15:53:33 agartha kernel: [ 363.707527] Call Trace: Jun 23 15:53:33 agartha kernel: [ 363.707535] ? __schedule+0x3c2/0x8b0 Jun 23 15:53:33 agartha kernel: [ 363.707537] ? __kfifo_in+0x2d/0x40 Jun 23 15:53:33 agartha kernel: [ 363.707539] ? schedule+0x32/0x80 Jun 23 15:53:33 agartha kernel: [ 363.707574] ? amd_sched_entity_push_job+0xb9/0x100 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707576] ? remove_wait_queue+0x60/0x60 Jun 23 15:53:33 agartha kernel: [ 363.707593] ? amdgpu_job_submit+0x6e/0x90 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707608] ? amdgpu_vm_bo_split_mapping+0x510/0x6f0 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707629] ? amdgpu_gem_prime_export+0x50/0x50 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707644] ? amdgpu_vm_bo_update+0x148/0x340 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707657] ? amdgpu_gem_va_ioctl+0x3c9/0x400 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707659] ? __check_object_size+0xfb/0x196 Jun 23 15:53:33 agartha kernel: [ 363.707677] ? drm_ioctl+0x1ef/0x440 [drm] Jun 23 15:53:33 agartha kernel: [ 363.707684] ? drm_ioctl+0x1ef/0x440 [drm] Jun 23 15:53:33 agartha kernel: [ 363.707697] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707699] ? ep_scan_ready_list.constprop.13+0x24f/0x260 Jun 23 15:53:33 agartha kernel: [ 363.707701] ? __hrtimer_init+0xc0/0xc0 Jun 23 15:53:33 agartha kernel: [ 363.707702] ? timerqueue_add+0x54/0xa0 Jun 23 15:53:33 agartha kernel: [ 363.707713] ? amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Jun 23 15:53:33 agartha kernel: [ 363.707714] ? do_vfs_ioctl+0x9f/0x600 Jun 23 15:53:33 agartha kernel: [ 363.707716] ? __sys_recvmsg+0x4e/0x90 Jun 23 15:53:33 agartha kernel: [ 363.707717] ? __sys_recvmsg+0x7d/0x90 Jun 23 15:53:33 agartha kernel: [ 363.707718] ? SyS_ioctl+0x74/0x80 Jun 23 15:53:33 agartha kernel: [ 363.707720] ? system_call_fast_compare_end+0xc/0x9b Jun 23 15:55:33 agartha kernel: [ 484.547113] INFO: task Xorg:952 blocked for more than 120 seconds. Jun 23 15:55:33 agartha kernel: [ 484.547119] Not tainted 4.11.0-trunk-amd64 #1 Debian 4.11.3-1~exp1~cheako0~artful0 Jun 23 15:55:33 agartha kernel: [ 484.547120] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jun 23 15:55:33 agartha kernel: [ 484.547122] XorgD0 952950 0x0004 Jun 23 15:55:33 agartha kernel: [ 484.547124] Call Trace: Jun 23 15:55:33 agartha kernel: [ 484.547132] ? __schedule+0x3c2/0x8b0 Jun 23 15:55:33 agartha kernel: [ 484.547134] ? __kfifo_in+0x2d/0x40 Jun 23 15:55:33 agartha kernel: [ 484.547136] ? schedule+0x32/0x80 Jun 23 15:55:33 agartha kernel: [ 484.547177] ? amd_sched_entity_push_job+0xb9/0x100 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547179] ? remove_wait_queue+0x60/0x60 Jun 23 15:55:33 agartha kernel: [ 484.547197] ? amdgpu_job_submit+0x6e/0x90 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547212] ? amdgpu_vm_bo_split_mapping+0x510/0x6f0 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547227] ? amdgpu_gem_prime_export+0x50/0x50 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547241] ? amdgpu_vm_bo_update+0x148/0x340 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547255] ? amdgpu_gem_va_ioctl+0x3c9/0x400 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547257] ? __check_object_size+0xfb/0x196 Jun 23 15:55:33 agartha kernel: [ 484.547273] ? drm_ioctl+0x1ef/0x440 [drm] Jun 23 15:55:33 agartha kernel: [ 484.547279] ? drm_ioctl+0x1ef/0x440 [drm] Jun 23 15:55:33 agartha kernel: [ 484.547293] ? amdgpu_gem_metadata_ioctl+0x1c0/0x1c0 [amdgpu] Jun 23 15:55:33 agartha kernel: [ 484.547295] ? ep_scan_ready_list.constprop.13+0x24f/0x260 Jun 23 15:55:33 agartha kernel: [ 484.547297] ? __hrtimer_init+0xc0/0xc0 Jun 23 15:55:33 agartha kernel: [ 484.547298] ? timerqueue_add+0x54/0xa0 Jun 23 15:55:33 agartha kernel: [ 484.547309] ? amdgpu_drm_ioctl+0x49/0x80 [amdgpu] Jun 23 15:55:33 agartha kernel: [
Re: R7-250X: Vulkan: Doom lockups.
On Fri, Jun 16, 2017 at 1:02 AM, Emil Velikov <emil.l.veli...@gmail.com> wrote: > Hi Mike, > > On 16 June 2017 at 05:48, Mike Mestnik <che...@mikemestnik.net> wrote: >> I can tell by the 2 color(green and violet) rendering that this driver >> is experimental. Attached is kern.log from some testing I've done. >> > You might be interested in the following bug report. It's the first > hit on google under "radv doom green" ;-) > > https://bugs.freedesktop.org/show_bug.cgi?id=99467 > > -Emil That's great, but I was more reporting the lockups. Like the DRM should be catching something it's not. ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
R7-250X: Vulkan: Doom lockups.
I can tell by the 2 color(green and violet) rendering that this driver is experimental. Attached is kern.log from some testing I've done. Jun 15 22:14:47 agartha kernel: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-trunk-amd64 root=UUID=05127f71-6704-4c13-9401-48496c61e0fe ro rootflags=subvol=root-amd64-i386 quiet rootflags=subvolid=261 Jun 15 22:14:47 agartha kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' Jun 15 22:14:47 agartha kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' Jun 15 22:14:47 agartha kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' Jun 15 22:14:47 agartha kernel: [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 Jun 15 22:14:47 agartha kernel: [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. Jun 15 22:14:47 agartha kernel: [0.00] e820: BIOS-provided physical RAM map: Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0x-0x0009] usable Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0x0010-0xdcf9bfff] usable Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdcf9c000-0xdcfcbfff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdcfcc000-0xdcfdbfff] ACPI data Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdcfdc000-0xdd654fff] ACPI NVS Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdd655000-0xde3e2fff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xde3e3000-0xde43efff] type 20 Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xde43f000-0xde43] usable Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xde44-0xde645fff] ACPI NVS Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xde646000-0xdea82fff] usable Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdea83000-0xdeff3fff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xdeff4000-0xdeff] usable Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xfeb8-0xfec01fff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xfec1-0xfec10fff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xfed0-0xfed00fff] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xfed8-0xfed8] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0xff00-0x] reserved Jun 15 22:14:47 agartha kernel: [0.00] BIOS-e820: [mem 0x0001-0x00041eff] usable Jun 15 22:14:47 agartha kernel: [0.00] NX (Execute Disable) protection: active Jun 15 22:14:47 agartha kernel: [0.00] efi: EFI v32.31 by American Megatrends Jun 15 22:14:47 agartha kernel: [0.00] efi: ACPI=0xdcfd3000 ACPI 2.0=0xdcfd3000 SMBIOS=0xf04c0 MPS=0xfd490 Jun 15 22:14:47 agartha kernel: [0.00] SMBIOS 2.7 present. Jun 15 22:14:47 agartha kernel: [0.00] DMI: System manufacturer System Product Name/A88X-PRO, BIOS 1902 03/27/2015 Jun 15 22:14:47 agartha kernel: [0.00] e820: update [mem 0x-0x0fff] usable ==> reserved Jun 15 22:14:47 agartha kernel: [0.00] e820: remove [mem 0x000a-0x000f] usable Jun 15 22:14:47 agartha kernel: [0.00] e820: last_pfn = 0x41f000 max_arch_pfn = 0x4 Jun 15 22:14:47 agartha kernel: [0.00] MTRR default type: uncachable Jun 15 22:14:47 agartha kernel: [0.00] MTRR fixed ranges enabled: Jun 15 22:14:47 agartha kernel: [0.00] 0-9 write-back Jun 15 22:14:47 agartha kernel: [0.00] A-B write-through Jun 15 22:14:47 agartha kernel: [0.00] C-C write-protect Jun 15 22:14:47 agartha kernel: [0.00] D-D uncachable Jun 15 22:14:47 agartha kernel: [0.00] E-F write-protect Jun 15 22:14:47 agartha kernel: [0.00] MTRR variable ranges enabled: Jun 15 22:14:47 agartha kernel: [0.00] 0 base mask 8000 write-back Jun 15 22:14:47 agartha kernel: [0.00] 1 base 8000 mask C000 write-back Jun 15 22:14:47 agartha kernel: [0.00] 2 base C000 mask E000 write-back Jun 15 22:14:47 agartha kernel: [0.00] 3 disabled Jun 15 22:14:47 agartha kernel: [0.00] 4 disabled Jun 15 22:14:47 agartha kernel: [0.00] 5 disabled Jun
radeon: ring 0 stalled for more than 10480msec
May 18 21:38:55 arcadia kernel: [0.00] Linux version 4.0.0-1-amd64 (debian-kernel at lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-16) ) #1 SMP Debian 4.0.2-1 (2015-05-11) May 18 21:38:55 arcadia kernel: [3.467818] [drm] radeon/VERDE_mc2.bin: 31500 bytes May 19 00:06:08 arcadia kernel: [ 6226.594929] radeon :01:00.0: ring 0 stalled for more than 10480msec May 19 00:06:08 arcadia kernel: [ 6226.594938] radeon :01:00.0: GPU lockup (current fence id 0x0003dc60 last fence id 0x0003dc7c on ring 0) May 19 00:06:09 arcadia kernel: [ 6227.126990] radeon :01:00.0: Saved 1185 dwords of commands on ring 0. May 19 00:06:09 arcadia kernel: [ 6227.127068] radeon :01:00.0: GPU softreset: 0x004D May 19 00:06:09 arcadia kernel: [ 6227.127072] radeon :01:00.0: GRBM_STATUS = 0xA25E7028 May 19 00:06:09 arcadia kernel: [ 6227.127076] radeon :01:00.0: GRBM_STATUS_SE0 = 0x0F86 May 19 00:06:09 arcadia kernel: [ 6227.127080] radeon :01:00.0: GRBM_STATUS_SE1 = 0x0006 May 19 00:06:09 arcadia kernel: [ 6227.127083] radeon :01:00.0: SRBM_STATUS = 0x200400C0 May 19 00:06:09 arcadia kernel: [ 6227.127141] radeon :01:00.0: SRBM_STATUS2 = 0x May 19 00:06:09 arcadia kernel: [ 6227.127144] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x May 19 00:06:09 arcadia kernel: [ 6227.127147] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010800 May 19 00:06:09 arcadia kernel: [ 6227.127150] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x00408006 May 19 00:06:09 arcadia kernel: [ 6227.127154] radeon :01:00.0: R_008680_CP_STAT = 0x84038647 May 19 00:06:09 arcadia kernel: [ 6227.127157] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44483146 May 19 00:06:09 arcadia kernel: [ 6227.127160] radeon :01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 May 19 00:06:09 arcadia kernel: [ 6227.127163] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x May 19 00:06:09 arcadia kernel: [ 6227.127167] radeon :01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x May 19 00:06:09 arcadia kernel: [ 6227.637461] radeon :01:00.0: GRBM_SOFT_RESET=0xDDFF May 19 00:06:09 arcadia kernel: [ 6227.637520] radeon :01:00.0: SRBM_SOFT_RESET=0x00100100 May 19 00:06:09 arcadia kernel: [ 6227.638671] radeon :01:00.0: GRBM_STATUS = 0x80007028 May 19 00:06:09 arcadia kernel: [ 6227.638675] radeon :01:00.0: GRBM_STATUS_SE0 = 0x0206 May 19 00:06:09 arcadia kernel: [ 6227.638679] radeon :01:00.0: GRBM_STATUS_SE1 = 0x0006 May 19 00:06:09 arcadia kernel: [ 6227.638682] radeon :01:00.0: SRBM_STATUS = 0x200400C0 May 19 00:06:09 arcadia kernel: [ 6227.638740] radeon :01:00.0: SRBM_STATUS2 = 0x May 19 00:06:09 arcadia kernel: [ 6227.638744] radeon :01:00.0: R_008674_CP_STALLED_STAT1 = 0x May 19 00:06:09 arcadia kernel: [ 6227.638747] radeon :01:00.0: R_008678_CP_STALLED_STAT2 = 0x May 19 00:06:09 arcadia kernel: [ 6227.638750] radeon :01:00.0: R_00867C_CP_BUSY_STAT = 0x May 19 00:06:09 arcadia kernel: [ 6227.638753] radeon :01:00.0: R_008680_CP_STAT = 0x May 19 00:06:09 arcadia kernel: [ 6227.638756] radeon :01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 May 19 00:06:09 arcadia kernel: [ 6227.638759] radeon :01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 May 19 00:06:09 arcadia kernel: [ 6227.638890] radeon :01:00.0: GPU reset succeeded, trying to resume May 19 00:06:09 arcadia kernel: [ 6227.670575] [drm] probing gen 2 caps for device 1022:1425 = 733d03/e May 19 00:06:09 arcadia kernel: [ 6227.670580] [drm] PCIE gen 3 link speeds already enabled May 19 00:06:09 arcadia kernel: [ 6227.673508] [drm] PCIE GART of 1024M enabled (table at 0x00277000). May 19 00:06:09 arcadia kernel: [ 6227.673631] radeon :01:00.0: WB enabled May 19 00:06:09 arcadia kernel: [ 6227.673634] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x88040a4ffc00 May 19 00:06:09 arcadia kernel: [ 6227.673636] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0x88040a4ffc04 May 19 00:06:09 arcadia kernel: [ 6227.673638] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x88040a4ffc08 May 19 00:06:09 arcadia kernel: [ 6227.673639] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x88040a4ffc0c May 19 00:06:09 arcadia kernel: [ 6227.673641] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0x88040a4ffc10 May 19 00:06:09 arcadia kernel: [ 6227.674040] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0xc90005f35a18 May 19 00:06:09 arcadia kernel: [ 6227.841114] [drm] ring
stereoscopic: 3D over standard 1080p using remote to switch into 3D mode.
Hello, I've successfully done a few tests using Chrome and WebGL to render two images side by side and having the TV compose the images into stereoscopic 3D. I don't know why there was a notion that one needed to send special HDMI commands. Well perhaps to reach full 1080p these commands might be necessary, although it looks like most TVs can figure out what to do if they are given the right modeline and I feel that these special HDMI commands may simply be cosmetic after reading 2010_03_04_3DExtraction_HDMI_Spec1.4a.pdf and only necessary if you want to do something out of the ordinary. Currently the display hardware is vary far ahead of the software and frankly it's unavailable for novices like myself. While my tests were conclusive using different shapes altogether in each eye, I was unable to line things up to my satisfaction to produce anything usable. I just got really board with this project because of my skill level. One area I find interesting is that we will once again have a half frame, as the technology of my set uses shutter glasses it would seem appropriate to render things in a fashion much like what's done for interlaced content. In that an object moving horizontally would be drawn in 2 places for each eye so that the position of the object is consistent for when the user sees it. I'm looking into upgrading to a 4K set, now that they are affordable... I plan to sit right up next to it and use it like any other monitor, so I'm not concerned about that oddly irrelevant debates that those resolutions are not usable. It's like a web developer refusing to accept anything greater then 800x600, ppl should just move past there preconceptions an opinions... That said the TVs I'm looking at use another technology that uses even and odd rows for each eye, so the previously mentioned half frames are out and we bring in a concept similar to sub-pixel ordering which while not offering any great challenges or rewards it may produce a loss in quality if not handled correctly. It's clear that to fully support these technologies a great deal of work would be needed. Leaving one vary big question worth asking... What's important and what course of action are ppl thinking? Currently Gnome has a UI for tweaking font rendering. How, if at all, should stereoscopic hardware be configured? Especially with regard to technology type and perhaps future displays capable of multiple technologies? There are also glassless stereoscopic technologies as possibilities. I'm most concerned with what ppl are waiting for, I've moved from a CTR to this rig because I didn't think till now that there were any displays that were fast enough for me. That and I noticed that I rarely used the interlaced modes to deinterlace content made for TV. Now with 4K I can finally have big size and high resolution, it'll be nice to have two 55" displays side by side.
stereoscopic: 3D over standard 1080p using remote to switch into 3D mode.
Hello, I've successfully done a few tests using Chrome and WebGL to render two images side by side and having the TV compose the images into stereoscopic 3D. I don't know why there was a notion that one needed to send special HDMI commands. Well perhaps to reach full 1080p these commands might be necessary, although it looks like most TVs can figure out what to do if they are given the right modeline and I feel that these special HDMI commands may simply be cosmetic after reading 2010_03_04_3DExtraction_HDMI_Spec1.4a.pdf and only necessary if you want to do something out of the ordinary. Currently the display hardware is vary far ahead of the software and frankly it's unavailable for novices like myself. While my tests were conclusive using different shapes altogether in each eye, I was unable to line things up to my satisfaction to produce anything usable. I just got really board with this project because of my skill level. One area I find interesting is that we will once again have a half frame, as the technology of my set uses shutter glasses it would seem appropriate to render things in a fashion much like what's done for interlaced content. In that an object moving horizontally would be drawn in 2 places for each eye so that the position of the object is consistent for when the user sees it. I'm looking into upgrading to a 4K set, now that they are affordable... I plan to sit right up next to it and use it like any other monitor, so I'm not concerned about that oddly irrelevant debates that those resolutions are not usable. It's like a web developer refusing to accept anything greater then 800x600, ppl should just move past there preconceptions an opinions... That said the TVs I'm looking at use another technology that uses even and odd rows for each eye, so the previously mentioned half frames are out and we bring in a concept similar to sub-pixel ordering which while not offering any great challenges or rewards it may produce a loss in quality if not handled correctly. It's clear that to fully support these technologies a great deal of work would be needed. Leaving one vary big question worth asking... What's important and what course of action are ppl thinking? Currently Gnome has a UI for tweaking font rendering. How, if at all, should stereoscopic hardware be configured? Especially with regard to technology type and perhaps future displays capable of multiple technologies? There are also glassless stereoscopic technologies as possibilities. I'm most concerned with what ppl are waiting for, I've moved from a CTR to this rig because I didn't think till now that there were any displays that were fast enough for me. That and I noticed that I rarely used the interlaced modes to deinterlace content made for TV. Now with 4K I can finally have big size and high resolution, it'll be nice to have two 55 displays side by side. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
In Diablo III when the ground is covered in water, it's all messed-up.
I found a rendering error in Diablo III, in a well there ground is covered in water and it's all red and flickers. http://c566453.r53.cf2.rackcdn.com/DiabloIII-well-wine-preloader.trace.xz 3.5G, 234665296 Bytes compressed ~234M. EE r600_shader.c:1605 r600_shader_from_tgsi - GPR limit exceeded - shader requires 181 registers EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed ! Rendered 621 frames in 80.724 secs, average of 7.69288 fps
In Diablo III when the ground is covered in water, it's all messed-up.
I found a rendering error in Diablo III, in a well there ground is covered in water and it's all red and flickers. http://c566453.r53.cf2.rackcdn.com/DiabloIII-well-wine-preloader.trace.xz 3.5G, 234665296 Bytes compressed ~234M. EE r600_shader.c:1605 r600_shader_from_tgsi - GPR limit exceeded - shader requires 181 registers EE r600_shader.c:140 r600_pipe_shader_create - translation from TGSI failed ! Rendered 621 frames in 80.724 secs, average of 7.69288 fps ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Diablo III Beta: Testing platform available, even for (wine and non-beta testers) users like me.
PM me and I get get you setup with access to my private Battle.Net test platform for the purpose of working on wine or Video Drivers. I can supply the crack to join third party servers built to run on wine and *?illegally? the Diablo III Beta download(er) Diablo-III-Beta-enUS-Setup.exe. * I'd prefer if you could find the downloader on your own, note that the pre-release download is not adequate. I can be found via email or on IRC as cheako. On 04/26/12 09:19, Mike Mestnik wrote: > My system specs are here http://pastebin.com/35NwE0G1 > dmsg http://pastebin.com/CDhuT4bU > http://c566453.r53.cf2.rackcdn.com/DIIILoackupLowFPS.trace.xz > > This trace shows unbearable slowness and a GPU lockup at a specific map > location, "*GPU lockup CP detected." > *http://appdb.winehq.org/objectManager.php?sClass=version=25588 >
Diablo III Beta: Testing platform available, even for (wine and non-beta testers) users like me.
PM me and I get get you setup with access to my private Battle.Net test platform for the purpose of working on wine or Video Drivers. I can supply the crack to join third party servers built to run on wine and *?illegally? the Diablo III Beta download(er) Diablo-III-Beta-enUS-Setup.exe. * I'd prefer if you could find the downloader on your own, note that the pre-release download is not adequate. I can be found via email or on IRC as cheako. On 04/26/12 09:19, Mike Mestnik wrote: My system specs are here http://pastebin.com/35NwE0G1 dmsg http://pastebin.com/CDhuT4bU http://c566453.r53.cf2.rackcdn.com/DIIILoackupLowFPS.trace.xz This trace shows unbearable slowness and a GPU lockup at a specific map location, *GPU lockup CP detected. *http://appdb.winehq.org/objectManager.php?sClass=versioniId=25588 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
RV670: wine: Diablo III Beta: GPU Lockup and slow framerate(9FPS avg.) 400MB compressed trace available.
My system specs are here http://pastebin.com/35NwE0G1 dmsg http://pastebin.com/CDhuT4bU http://c566453.r53.cf2.rackcdn.com/DIIILoackupLowFPS.trace.xz This trace shows unbearable slowness and a GPU lockup at a specific map location, "*GPU lockup CP detected." *http://appdb.winehq.org/objectManager.php?sClass=version=25588
RV670: wine: Diablo III Beta: GPU Lockup and slow framerate(9FPS avg.) 400MB compressed trace available.
My system specs are here http://pastebin.com/35NwE0G1 dmsg http://pastebin.com/CDhuT4bU http://c566453.r53.cf2.rackcdn.com/DIIILoackupLowFPS.trace.xz This trace shows unbearable slowness and a GPU lockup at a specific map location, *GPU lockup CP detected. *http://appdb.winehq.org/objectManager.php?sClass=versioniId=25588 ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
