dri-devel March 2015

dri-devel@lists.freedesktop.org

196 participants
1117 discussions

[Bug 81620] New: radeon: fence wait failed (-35) after hybrid suspend on 3.15
by bugzilla-daemon＠freedesktop.org 30 May '18

30 May '18

https://bugs.freedesktop.org/show_bug.cgi?id=81620 Priority: medium Bug ID: 81620 Assignee: dri-devel(a)lists.freedesktop.org Summary: radeon: fence wait failed (-35) after hybrid suspend on 3.15 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: iive(a)yahoo.com Hardware: x86 (IA32) Status: NEW Version: unspecified Component: DRM/Radeon Product: DRI Created attachment 103217 --> https://bugs.freedesktop.org/attachment.cgi?id=103217&action=edit dmesg of suspend/resume session with radeon.ko dpm debug turned on My hardware is Radeon HD5670 (Redwood). To reproduce the problem boot vanilla 3.15.x kernel. Run in KMS mode (no Xorg server needed). Then suspend to ram-and-disk with the following command: `echo suspend > /sys/power/disk; echo disk > /sys/power/state` Resume from the power button. In `dmesg` you can find: [ 83.997399] [drm] ring test on 5 succeeded in 1 usecs [ 83.997403] [drm] UVD initialized successfully. [ 83.997450] [drm] ib test on ring 0 succeeded in 0 usecs [ 83.997494] [drm] ib test on ring 3 succeeded in 1 usecs [ 94.137259] radeon 0000:01:00.0: ring 5 stalled for more than 10000msec [ 94.137263] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000004 last fence id 0x0000000000000002 on ring 5) [ 94.137265] [drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35). [ 94.137268] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35). At this point if Xorg server is started any attempt to vdpau hardware decoding would fail. If the computer is left working, without reboot, at some point timeout would trigger and GPU restart might be attempted, usually hanging the system. (I took the following log from older GPU restart, probably successful). [ 0.000000] Linux version 3.15.2 (root) (gcc version 4.8.3 (GCC) ) #2 SMP [12398.387691] radeon 0000:01:00.0: ring 5 stalled for more than 242796msec [12398.387699] radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000005 last fence id 0x0000000000000004 on ring 5) [12398.425151] radeon 0000:01:00.0: Saved 23 dwords of commands on ring 0. [12398.425167] radeon 0000:01:00.0: GPU softreset: 0x00000009 [12398.425169] radeon 0000:01:00.0: GRBM_STATUS = 0xF5703828 [12398.425171] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0xFC000007 [12398.425173] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [12398.425175] radeon 0000:01:00.0: SRBM_STATUS = 0x200800C0 [12398.425177] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [12398.425179] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [12398.425181] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x40000000 [12398.425183] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00008004 [12398.425185] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80228647 [12398.425187] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [12398.441572] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x00007F6B [12398.441626] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00000100 [12398.442782] radeon 0000:01:00.0: GRBM_STATUS = 0x00003828 [12398.442783] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000007 [12398.442785] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000007 [12398.442787] radeon 0000:01:00.0: SRBM_STATUS = 0x200800C0 [12398.442789] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [12398.442791] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [12398.442793] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [12398.442795] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [12398.442796] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [12398.442798] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [12398.442813] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [12398.512161] [drm] enabling PCIE gen 2 link speeds, disable with radeon.pcie_gen2=0 [12398.516583] [drm] PCIE GART of 1024M enabled (table at 0x000000000025D000). The bug vanishes if only suspend to ram or suspend to disk is used. I tried to do a bisect, but a number of rc kernels seem to hang on me, long before radeon module is loaded. At this point bisect I suspected that the new async suspend/resume code might be at fault, as I was seeing video card been turned off (aka monitor going off) and then turning on a moment before shutting down completely. So I found the commits of the async suspend (from an article) and reverted them. Reverting 200421a80f6e0a9e39d698944cc35cba103eb6ce, 3c31b52f96f7b559d950b16113c0f68c72a1985e seems to avoid the above effect about monitor turning off, on, then off again. But it does not fix the bug. Reverting 7cd0602d7836c0056fe9bdab014d5ac5ec5cb291, 92858c476ec4e99cf0425f05dee109b6a55eb6f8 and 9e5e7910df824ba02aedd2b5d2ca556426ea6d0b, 76569faa62c46382e080c3e190c66e19515aae1c, de377b3972729f00ee236ae4a97393e282ffe391, 28b6fd6e37792b16a56d324841bdb20ab78e4522, a59ffb2062df3a5c346dbed931fa1e587fd0f0f3 doesn't affect the bug either, so I assume that this bug is not related to suspend/resume async changes. If you cannot reproduce the problem, please advice me what commits to revert. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 72785] New: bfgminer --scrypt on 7xxx+
by bugzilla-daemon＠freedesktop.org 30 May '18

30 May '18

https://bugs.freedesktop.org/show_bug.cgi?id=72785 Priority: medium Bug ID: 72785 Assignee: dri-devel(a)lists.freedesktop.org Summary: bfgminer --scrypt on 7xxx+ Severity: normal Classification: Unclassified OS: All Reporter: haagch.christoph(a)googlemail.com Hardware: All Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa bfgminer --benchmark without scrypt seems to be working fine now. But I think many people would rather compute scrypt right now on their 7xxx+ GPUs, just considering the recent rumors that the radeon 7950 is getting sold out because of litecoin miners. With mesa/llvm it doesn't work yet. llvm 3.5 197392, mesa and stuff are very recent git builds. The kernel is https://github.com/luke-jr/bfgminer/blob/bfgminer/scrypt130511.cl bfgminer is started with bfgminer -v1 --scrypt -S opencl:auto --url=<pool> --userpass=<user:worker:pass> The error is: Initialising kernel scrypt130511.cl without bitalign, 1 vectors and worksize 256 [...] LLVM ERROR: Cannot select: 0x7f0b7cbd40a0: ch = br_cc 0x7f0b7cd32bb0, 0x7f0b7cc28c20, 0x7f0b7cd32fb0, 0x7f0b7cc2bc30, 0x7f0b7cc2ad30 [ORD=19251] [ID=4253] 0x7f0b7cd32fb0: i1,ch = llvm.SI.loop 0x7f0b7cc2c030:1, 0x7f0b7cd333b0, 0x7f0b7cc2c030 [ORD=19250] [ID=4250] 0x7f0b7cd333b0: i64 = TargetConstant<3431> [ID=132] 0x7f0b7cc2c030: i64,ch = llvm.SI.if.break 0x7f0b7cf2f3e0, 0x7f0b7cc2b530, 0x7f0b7cc2c530, 0x7f0b7cd339b0 [ORD=19249] [ID=4249] 0x7f0b7cc2b530: i64 = TargetConstant<3428> [ID=129] 0x7f0b7cc2c530: i1 = setcc 0x7f0b7cc7dd60, 0x7f0b7cc80760, 0x7f0b7cd337b0 [ORD=19248] [ID=212] 0x7f0b7cc7dd60: i64 = add 0x7f0b7cc81560, 0x7f0b7cc81360 [ORD=13153] [ID=187] 0x7f0b7cc81560: i64,ch = CopyFromReg 0x7f0b7c0535d8, 0x7f0b7cc81660 [ORD=13147] [ID=149] 0x7f0b7cc81660: i64 = Register %vreg53 [ID=1] 0x7f0b7cc81360: i64 = Constant<1> [ID=2] 0x7f0b7cc80760: i64 = Constant<4> [ID=4] 0x7f0b7cd339b0: i64,ch = CopyFromReg 0x7f0b7c0535d8, 0x7f0b7cd342b0 [ORD=19249] [ID=185] 0x7f0b7cd342b0: i64 = Register %vreg52 [ID=130] 0x7f0b7cc2bc30: i1 = Constant<-1> [ID=133] In function: search -- You are receiving this mail because: You are the assignee for the bug.

1 43

[Bug 48424] New: Fix warnings/errors reported by clang's scan-build tool
by bugzilla-daemon＠freedesktop.org 12 Apr '18

12 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=48424 Bug #: 48424 Summary: Fix warnings/errors reported by clang's scan-build tool Classification: Unclassified Product: Mesa Version: git Platform: x86 (IA32) URL: https://gitorious.org/jobermayr/scan-build-mesa OS/Version: All Status: NEW Severity: normal Priority: medium Component: Mesa core AssignedTo: mesa-dev(a)lists.freedesktop.org ReportedBy: johannesobermayr(a)gmx.de CC: dri-devel(a)lists.freedesktop.org, nouveau(a)lists.freedesktop.org https://gitorious.org/jobermayr/scan-build-mesa ~ 8 MB to download, 680 MB on disk. Please report false positives here. I will forward them. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 70910] New: [radeonsi&r600g] wrong colors on radeonsi screen in some places when radeonsi and r600g gpus are installed
by bugzilla-daemon＠freedesktop.org 10 Apr '18

10 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=70910 Priority: medium Bug ID: 70910 Assignee: dri-devel(a)lists.freedesktop.org Summary: [radeonsi&r600g] wrong colors on radeonsi screen in some places when radeonsi and r600g gpus are installed Severity: minor Classification: Unclassified OS: All Reporter: ptpzz(a)yandex.ru Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/radeonsi Product: Mesa Created attachment 88176 --> https://bugs.freedesktop.org/attachment.cgi?id=88176&action=edit screenshot Looks like in some cases there is RGB <-> BGR mismatch, so that red icons become blue, etc. On the attached screenshot xchat icon on the xfce panel is rendered normally - red/yellow, but the same icon on a tooltip below is blue. Similar issues can be seen in some other places - e.g. window decorations, icons on buttons in dialog windows, but in many other cases the colors are correct - e.g. with glxgears. AFAICS there is no such problem on r600g screen. Also, without r600g card there is no such problem on radeonsi screen as well, it happens only when two cards are installed. r600g uses EXA in my config, but IIRC it was the same when both drivers use glamor. -- You are receiving this mail because: You are the assignee for the bug.

1 10

[Bug 66940] New: Mobility Radeon HD 5650 doesn't resume from suspend on kernel 3.11 (linus and drm_next)
by bugzilla-daemon＠freedesktop.org 10 Apr '18

10 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=66940 Priority: medium Bug ID: 66940 Assignee: dri-devel(a)lists.freedesktop.org Summary: Mobility Radeon HD 5650 doesn't resume from suspend on kernel 3.11 (linus and drm_next) Severity: normal Classification: Unclassified OS: All Reporter: mail(a)3v1n0.net Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 82459 --> https://bugs.freedesktop.org/attachment.cgi?id=82459&action=edit dmesg I've tried running linux 3.11 from both linus and drm_next branches, but when using the radeon drivers it's impossible to resume from suspension. It's quite sure that the problem is in radeon module, because unloading it (and switching to my intel card with vgaswitcheroo) works fine. Also, enabling the pm_trace sys-node it highlights that the radeon device caused the freeze: from dmesg: [ 1.286810] Magic number: 0:660:725 [ 1.286815] hash matches /home/marco/Dev/debs/linux/drivers/base/power/main.c:575 [ 1.286829] block loop5: hash matches [ 1.286867] pci 0000:01:00.0: hash matches ^ This is the PCI id of my radeon card cat /sys/power/pm_trace_dev_match: block radeon This is a regression, since linux 3.10 works well. -- You are receiving this mail because: You are the assignee for the bug.

1 16

[Bug 89685] Cripling Dota 2 freeze with Morphling at hero selection or loadout
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89685 Bug ID: 89685 Summary: Cripling Dota 2 freeze with Morphling at hero selection or loadout Product: Mesa Version: 10.5 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: wittyman37(a)yahoo.com QA Contact: dri-devel(a)lists.freedesktop.org So I am having a very bizare issue as recently. I noticed yesterday that I cannot play Morphling! If I select him during the hero selection or even try to view him in the loadout screen, my system completely freezes with no option but to do a hard reset. I cannot alt-tab, minimize to desktop, switch to any TTY and REISUB does not work. This ONLY happens with the hero morphling and seems to be an issue with graphics because it seems to happen when I am about to see his model loaded. I even deleted the one item I had for him. I verified the game files; no good. I deleted all local content and downloaded the game again...no good. This is either an issue with my graphics drivers and morphling or a Dota 2 and Linux issue. My wife is using Windows 8.1 and does not have this problem. I am running an AMD R9 270X with linux 3.19.2 and mesa 10.5.1 where everything else works wonderfully! -- You are receiving this mail because: You are the assignee for the bug.

1 28

[Bug 84232] New: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=84232 Priority: medium Bug ID: 84232 Assignee: dri-devel(a)lists.freedesktop.org Summary: PHINode containing itself causes segfault in LLVM when compiling Blender OpenCL kernel with R600 backend Severity: normal Classification: Unclassified OS: All Reporter: vitalif(a)yourcmc.ru Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Created attachment 106717 --> https://bugs.freedesktop.org/attachment.cgi?id=106717&action=edit Blender output with R600_DEBUG=compute,fs,vs,gs,ps,cs I'm trying to run Blender using Mesa OpenCL implementation on a radeonsi card. First the kernel didn't want to compile, but that was caused by a bug in it (they were using . instead of -> in 1 place), and after fixing this bug I've got the kernel to compile... ...But after that, LLVM started to crash during translation of IR into shader code with R600 backend. I've done some investigation and figured out that the crash is caused by a PHINode containing itself. SIAnnotateControlFlow::handleLoopCondition() can't handle such situation - it recurses into itself, calls Phi->eraseFromParent() inside the inner execution, returns into outer one, gets zeroed out object and crashes when trying to do something with its members... for example when trying to erase it again. I've tried to understand the semantics of such PHINodes from reading the code and got a suspicion that the rest of LLVM code just ignores PHINodes equal to their parent, so I've tried to fix the bug by making handleLoopCondition() skip IncomingValues equal to the Phi itself, but the bug didn't go away! Surprisingly, PHINode may not just contain itself directly, but it also may contain itself inside another PHINode, i.e. Phi->getIncomingValue(0)->getIncomingValue(0) == Phi, which results in the same problem with SIAnnotateControlFlow... I'll attach Blender output with R600_DEBUG = trace everything and a stack trace of the crash. The bug reproduced with llvm 3.5 and snapshot of 3.6; blender is 2.71; Mesa is from OIBAF's repository. sudo -E CYCLES_OPENCL_TEST=1 R600_DEBUG=compute,fs,vs,gs,ps,cs blender cup\ of\ coffee\ 5.blend &> kernel-llvm.log -- You are receiving this mail because: You are the assignee for the bug.

1 20

[Bug 89659] GPU Hangs with dota2
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89659 Bug ID: 89659 Summary: GPU Hangs with dota2 Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: kontakt(a)ib-guder.de Created attachment 114442 --> https://bugs.freedesktop.org/attachment.cgi?id=114442&action=edit dmesg after a crash Hello, I get reproducible GPU hangs often within one minute spectating a game in dota2. Other OpenGL applications runs without hangs. The screen stays black, the keyboard doesn't work after a crash. Networking via ssh works. Archlinux 64bit Mesa: 10.5.1 Linux: 3.18.6 and 3.14.53 Thank you and best wishes Tom Guder -- You are receiving this mail because: You are the assignee for the bug.

1 4

[Bug 89059] Dota crashes constantly before 10min mark
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=89059 Bug ID: 89059 Summary: Dota crashes constantly before 10min mark Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel(a)lists.freedesktop.org Reporter: jarkko_korpi(a)hotmail.com QA Contact: dri-devel(a)lists.freedesktop.org I got oibaf ppa. They started to use LLVM 3.6 compiler around that time I started to have unstable dota. I cant finnish any dota 2 games. The computer hangs before 10min mark while in dota. But I have played around 2hour episode of game of thrones from tell tale. So this sounds only dota 2 issue for me. I could see console a message something like this: "Still active bo inside vm" The computer freezes, most of the times I could only force boot. Gpu r9 290 3.19.0-031900rc7 OpenGL renderer string: Gallium 0.4 on AMD HAWAII OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.0-devel (git-08a06b6 2015-02-10 trusty-oibaf-ppa) -- You are receiving this mail because: You are the assignee for the bug.

1 12

[Bug 79895] New: Google Hangout crashes radeon
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=79895 Priority: medium Bug ID: 79895 Assignee: dri-devel(a)lists.freedesktop.org Summary: Google Hangout crashes radeon Severity: normal Classification: Unclassified OS: All Reporter: darkbasic(a)linuxsystems.it Hardware: Other Status: NEW Version: XOrg CVS Component: DRM/Radeon Product: DRI Kernel 3.15.0-rc8 + PTE patches [380782.919272] Watchdog[21745]: segfault at 0 ip 00007f405eb822b8 sp 00007f404b8b9850 error 6 in chrome[7f405afc6000+5807000] [380783.427655] radeon 0000:01:00.0: ring 0 stalled for more than 11720msec [380783.427659] radeon 0000:01:00.0: GPU lockup (waiting for 0x00000000006e62e5 last fence id 0x00000000006e62e4 on ring 0) [380783.427662] radeon 0000:01:00.0: failed to get a new IB (-35) [380783.852997] radeon 0000:01:00.0: Saved 240 dwords of commands on ring 0. [380783.853042] radeon 0000:01:00.0: GPU softreset: 0x0000006C [380783.853043] radeon 0000:01:00.0: GRBM_STATUS = 0xA0003028 [380783.853044] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380783.853045] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380783.853046] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380783.853080] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380783.853082] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380783.853083] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00010000 [380783.853084] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000002 [380783.853085] radeon 0000:01:00.0: R_008680_CP_STAT = 0x80010243 [380783.853086] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44483106 [380783.853087] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C84246 [380783.853089] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00000000 [380783.853090] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x00000000 [380784.261939] radeon 0000:01:00.0: GRBM_SOFT_RESET=0x0000DDFF [380784.261993] radeon 0000:01:00.0: SRBM_SOFT_RESET=0x00100140 [380784.263140] radeon 0000:01:00.0: GRBM_STATUS = 0x00003028 [380784.263141] radeon 0000:01:00.0: GRBM_STATUS_SE0 = 0x00000006 [380784.263142] radeon 0000:01:00.0: GRBM_STATUS_SE1 = 0x00000006 [380784.263143] radeon 0000:01:00.0: SRBM_STATUS = 0x200000C0 [380784.263177] radeon 0000:01:00.0: SRBM_STATUS2 = 0x00000000 [380784.263178] radeon 0000:01:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [380784.263180] radeon 0000:01:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [380784.263181] radeon 0000:01:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [380784.263182] radeon 0000:01:00.0: R_008680_CP_STAT = 0x00000000 [380784.263183] radeon 0000:01:00.0: R_00D034_DMA_STATUS_REG = 0x44C83D57 [380784.263184] radeon 0000:01:00.0: R_00D834_DMA_STATUS_REG = 0x44C83D57 [380784.263261] radeon 0000:01:00.0: GPU reset succeeded, trying to resume [380784.301675] [drm] probing gen 2 caps for device 8086:151 = 261ad03/e [380784.301678] [drm] PCIE gen 3 link speeds already enabled [380784.303658] [drm] PCIE GART of 1024M enabled (table at 0x0000000000276000). [380784.303740] radeon 0000:01:00.0: WB enabled [380784.303742] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x00000000c0000c00 and cpu addr 0xffff880417946c00 [380784.303743] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x00000000c0000c04 and cpu addr 0xffff880417946c04 [380784.303744] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x00000000c0000c08 and cpu addr 0xffff880417946c08 [380784.303745] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x00000000c0000c0c and cpu addr 0xffff880417946c0c [380784.303746] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x00000000c0000c10 and cpu addr 0xffff880417946c10 [380784.304140] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffc90006135a18 [380784.625264] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0xCAFEDEAD) [380784.625268] [drm:si_resume] *ERROR* si startup failed on resume [380784.625304] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed [380784.625374] switching from power state: [380784.625376] ui class: none [380784.625377] internal class: boot [380784.625378] caps: [380784.625379] uvd vclk: 0 dclk: 0 [380784.625380] power level 0 sclk: 50000 mclk: 15000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625381] status: c b [380784.625382] switching to power state: [380784.625383] ui class: performance [380784.625384] internal class: none [380784.625385] caps: [380784.625386] uvd vclk: 0 dclk: 0 [380784.625387] power level 0 sclk: 30000 mclk: 15000 vddc: 850 vddci: 875 pcie gen: 3 [380784.625388] power level 1 sclk: 50100 mclk: 125000 vddc: 950 vddci: 875 pcie gen: 3 [380784.625390] power level 2 sclk: 81000 mclk: 125000 vddc: 1090 vddci: 875 pcie gen: 3 [380784.625390] status: r -- You are receiving this mail because: You are the assignee for the bug.

1 10

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel March 2015