dri-devel April 2018

dri-devel@lists.freedesktop.org

267 participants
1852 discussions

[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 90284] radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed.
by bugzilla-daemon＠freedesktop.org 03 Apr '18

03 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=90284 Bug ID: 90284 Summary: radeon crashes (ring 0 stall) with GPU fault detected: 147, and *ERROR* radeon: dpm resume failed. Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon Assignee: dri-devel(a)lists.freedesktop.org Reporter: niklas(a)trippler.no Created attachment 115515 --> https://bugs.freedesktop.org/attachment.cgi?id=115515&action=edit journalctl -r -x --boot=-4 Graphics card: AMD R9 290 Kernel: Linux archfractal 4.0.1-1-ARCH #1 SMP PREEMPT Monitors connected: 2 DE: Xfce Relevant packages: local/xf86-video-ati 1:7.5.0-2 (xorg-drivers xorg) local/lib32-mesa 10.5.4-1 local/lib32-mesa-libgl 10.5.4-1 local/lib32-mesa-vdpau 10.5.4-1 local/linux 4.0.1-1 (base) local/xorg-server 1.17.1-5 (xorg) This bug, which is triggered by dota2 (Valve game), locks up both displays for a few seconds before they blink black and freeze in the last frame displayed, requireing a system reboot. The bug seems to happen with others (same symptoms / log messages) using other applications (chrome html5 video was mentioned), but dota2 seems like one of the few recreatable ways to trigger the bug. Steps to recreate: Have steam and dota 2 installed (might have to remove steams own bundled libstdc++ libraries as they conflict with mesa). Launch dota 2 with any video settings Start a new lobby with "cheats enabled" and "all pick" game mode (these don't matter, but make it faster to recreate) Pick the hero "Chaos Knight" and enter the game Type in chat "-lvlup 24" to gain max level and skill up everything Click R to use ulti (which spawns copies of himself) Hold-drag mouse over all the illusions and the hero. When the mouse button is released the above bug triggers, crashing the displaydriver and taking the computer down with it. In the log attached (journal_log) the bug is triggered at 17:43:50, the first line there is: "kernel: radeon 0000:01:00.0: GPU fault detected: 147 0x000cc801" I noticed a few lines later the following lines appeared: May 02 17:44:01 archfractal kernel: [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed May 02 17:44:01 archfractal kernel: [drm:ci_dpm_enable [radeon]] *ERROR* ci_start_dpm failed I guessed the bug had something to do with dpm, and disabled it (kernel parameter radeon.dpm=0). When I had done this the bug could still be recreated, but the log showed completely different error messages. This log is also attached as "journal_log_radeon_dpm_is_0" I had to gzip the first log to fit within the 3M file size limit -- You are receiving this mail because: You are the assignee for the bug.

1 14

[PATCH v5 00/10] Implement proper MST fallback retraining in i915
by Lyude Paul 02 Apr '18

02 Apr '18

Latest version of https://patchwork.freedesktop.org/series/39642/ , hopefully patchwork understands this and doesn't break anything! Lots of changes. Lyude Paul (10): drm/atomic: Print debug message on atomic check failure drm/i915: Move DP modeset retry work into intel_dp drm/dp_mst: Fix naming on drm_atomic_get_mst_topology_state() drm/dp_mst: Remove all evil duplicate state pointers drm/dp_mst: Make drm_dp_mst_topology_state subclassable drm/dp_mst: Add reset_state callback to topology mgr drm/i915: Only use one link bw config for MST topologies drm/i915: Make intel_dp_mst_atomic_check() idempotent drm/dp_mst: Add MST fallback retraining helpers drm/i915: Implement proper fallback training for MST drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 14 +- .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.c | 35 +- .../amd/display/amdgpu_dm/amdgpu_dm_mst_types.h | 4 +- drivers/gpu/drm/drm_atomic.c | 5 +- drivers/gpu/drm/drm_dp_mst_topology.c | 548 ++++++++++++++++++++- drivers/gpu/drm/i915/intel_ddi.c | 10 +- drivers/gpu/drm/i915/intel_display.c | 14 +- drivers/gpu/drm/i915/intel_dp.c | 361 ++++++++++---- drivers/gpu/drm/i915/intel_dp_link_training.c | 6 +- drivers/gpu/drm/i915/intel_dp_mst.c | 180 +++++-- drivers/gpu/drm/i915/intel_drv.h | 20 +- drivers/gpu/drm/nouveau/nv50_display.c | 15 +- drivers/gpu/drm/radeon/radeon_dp_mst.c | 13 +- include/drm/drm_dp_mst_helper.h | 42 +- 14 files changed, 1088 insertions(+), 179 deletions(-) -- 2.14.3

2 11

[Bug 104825] [amdgpu] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) when unbinding
by bugzilla-daemon＠freedesktop.org 02 Apr '18

02 Apr '18

https://bugs.freedesktop.org/show_bug.cgi?id=104825 Bug ID: 104825 Summary: [amdgpu] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) when unbinding Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel(a)lists.freedesktop.org Reporter: mlen(a)mlen.pl I use two amdgpu rx480 cards. During boot one of them is rebound to vfio-pci driver using the following script: pci_ids=("0000:03:00.0" "0000:03:00.1") for id in "${pci_ids[@]}"; do vendor="$(cat "/sys/bus/pci/devices/$id/vendor")" device="$(cat "/sys/bus/pci/devices/$id/device")" if [ -e "/sys/bus/pci/devices/$id/driver/unbind" ]; then echo "$id" >"/sys/bus/pci/devices/$id/driver/unbind" fi echo "$vendor $device" >/sys/bus/pci/drivers/vfio-pci/new_id done Starting from Linux 4.15 with amdgpu DC enabled (I wanted to use it for HDMI audio), unbind operation causes general protection failure: [ 68.011473] [drm] amdgpu: finishing device. [ 68.377945] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 68.575193] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 68.770107] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 68.971775] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 69.164265] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 69.350089] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 69.538302] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 69.729260] [drm:gfx_v8_0_hw_fini] *ERROR* KCQ disabled failed (scratch(0xC040)=0x00000000) [ 69.729733] general protection fault: 0000 [#1] PREEMPT SMP PTI [ 69.730901] Modules linked in: [ 69.731936] CPU: 2 PID: 3934 Comm: openrc-run.sh Not tainted 4.15.0-gentoo #2 [ 69.733009] Hardware name: ASUSTeK COMPUTER INC. Z10PE-D16 WS/Z10PE-D16 WS, BIOS 3407 03/10/2017 [ 69.734240] RIP: 0010:dm_read_reg_func.isra.0+0x3/0xc [ 69.735314] RSP: 0018:ffffa80d8bd4fc40 EFLAGS: 00010282 [ 69.736353] RAX: ccea607dac10c354 RBX: ffff95af35bfca80 RCX: 0000000180200008 [ 69.737408] RDX: 0000000180200009 RSI: 0000000000005c02 RDI: ffff95af362b91c0 [ 69.738494] RBP: ffff95af35b75c90 R08: 0000000000000001 R09: ffffffffb30fced2 [ 69.739561] R10: ffff95af2f770a40 R11: 00000000ffffff80 R12: ffff95af35f30100 [ 69.740638] R13: 0000000000000000 R14: ffff95af358a3c20 R15: ffff95bf2d5f9c20 [ 69.742007] FS: 00007fe7530af740(0000) GS:ffff95af3da00000(0000) knlGS:0000000000000000 [ 69.743083] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 69.744134] CR2: 000000c420870008 CR3: 0000001027426003 CR4: 00000000003606e0 [ 69.745190] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 69.746246] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 69.747320] Call Trace: [ 69.748359] destroy+0x21/0x9c [ 69.749395] dal_i2caux_destruct+0x6f/0xab [ 69.750459] destroy+0x15/0x27 [ 69.751495] dal_i2caux_destroy+0x26/0x2f [ 69.752537] destruct+0x86/0xfd [ 69.753571] dc_destroy+0x11/0x22 [ 69.754626] dm_hw_fini+0x1e/0x22 [ 69.755632] amdgpu_fini+0xf3/0x2d6 [ 69.756616] amdgpu_device_fini+0x5c/0x158 [ 69.757597] amdgpu_driver_unload_kms+0x6b/0x7e [ 69.758601] drm_dev_unregister+0x4c/0xc6 [ 69.759584] amdgpu_pci_remove+0x19/0x37 [ 69.760576] pci_device_remove+0x3b/0x8b [ 69.761563] device_release_driver_internal+0x125/0x1f9 [ 69.762580] unbind_store+0x60/0x90 [ 69.763568] kernfs_fop_write+0x111/0x159 [ 69.764557] __vfs_write+0x33/0xd7 [ 69.765543] ? preempt_count_sub+0x8b/0x94 [ 69.766552] ? __sb_start_write+0xc0/0x180 [ 69.767525] vfs_write+0xa5/0xe2 [ 69.768490] SyS_write+0x5f/0xa3 [ 69.769439] do_syscall_64+0x72/0x81 [ 69.770419] entry_SYSCALL64_slow_path+0x25/0x25 [ 69.771373] RIP: 0033:0x7fe7529a1408 [ 69.772324] RSP: 002b:00007ffe1885c200 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 69.773300] RAX: ffffffffffffffda RBX: 000000000000000d RCX: 00007fe7529a1408 [ 69.774290] RDX: 000000000000000d RSI: 0000558994641890 RDI: 0000000000000001 [ 69.775290] RBP: 0000558994641890 R08: 000000000000000a R09: 00005589946475f0 [ 69.776260] R10: 000000000000009b R11: 0000000000000246 R12: 000000000000000d [ 69.777248] R13: 0000000000000001 R14: 00007fe752c6e740 R15: 000000000000000d [ 69.778244] Code: f7 74 24 04 89 43 5c 48 8b 4c 24 08 65 48 33 0c 25 28 00 00 00 4c 89 e0 74 05 e8 39 58 9e ff 48 83 c4 10 5b 5d 41 5c c3 48 8b 07 <48> 8b 40 30 e9 03 4a 70 00 0f 1f 44 00 00 48 8b 47 30 8b 70 04 [ 69.779406] RIP: dm_read_reg_func.isra.0+0x3/0xc RSP: ffffa80d8bd4fc40 [ 69.780491] ---[ end trace 6aa4681ba3a43ec3 ]--- [ 71.815503] [drm:amdgpu_fill_buffer] *ERROR* Trying to clear memory with ring turned off. [ 71.899258] amdgpu 0000:03:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 71.899263] amdgpu 0000:02:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none [ 72.217918] [drm:amdgpu_fill_buffer] *ERROR* Trying to clear memory with ring turned off. -- You are receiving this mail because: You are the assignee for the bug.

1 20

Re: 2018 Election voting OPEN
by Rob Clark 02 Apr '18

02 Apr '18

To all X.Org Foundation Members: Due to some technical difficulties, the earlier election notification messages to members(a)x.org list did not go through (but also did not trigger bounce/moderator notification). We cross referenced the members list to the subscriber lists for xorg-devel, xorg, mesa-dev, and wayland-devel lists and concluded that there are a small percentage of x.org foundation members who were not also subscribed to one of the lists CC'd on the original notification about election period. For this reason, to ensure that all x.org foundation members have an opportunity to vote, we are extending the voting period by one week. The voting period will now remain open until 23:59 UTC on 12 April 2018. Rob Clark, on behalf of the X.Org elections committee On Wed, Mar 21, 2018 at 8:40 PM, Rob Clark <robdclark(a)gmail.com> wrote: > To all X.Org Foundation Members: > > The X.Org Foundation's annual election is now open and will remain > open until 23:59 UTC on 5 April 2018. > > Four of the eight director seats are open during this election, with > the four nominees receiving the highest vote totals serving as > directors for two year terms. > > There were six candidates nominated. For a complete list of the > candidates and their personal statements, please see the following: > > https://www.x.org/wiki/BoardOfDirectors/Elections/2018/ > > Here are some instructions on how to cast your vote: > > Login to the membership system at: https://members.x.org/ > > If you do not remember your password, you can click on the "lost > password" button and enter your user name. An e-mail will be sent to > you with your password. If you have problems with the membership > system, please e-mail membership(a)x.org. > > When you login you will see a row of buttons that will allow you to > update your info, list the members, list the open ballots and logout. > Below this you will see a list of open ballots, for which you can cast > votes. At the bottom of this page you will see another row of buttons > with the current privacy policy, the provisional By-laws, the > provisional Membership Agreement and instructions on how to contact > the admin. > > Note that if you click on the "Ballots" button at any time, you will > see a list of the open ballots. > > To cast your vote in a ballot, click on the "Cast" button to the right > of the ballot you wish to vote on. This will bring up another page > with the list of the candidates, and a question of whether or not to > approve the new By-laws. > > For the election: There is a pull-down selection box next to each > candidate. For your top choice, select "1". For your second choice, > select "2" and so forth. You should think of the numbers that you are > selecting as the ranking of your preferences. > > Note that you are NOT required to select your preferences for all four > positions. You can leave more than one blank. The only restriction is > that you cannot duplicate any of your choices (i.e., you can only > select one "1", one "2" and so forth). > > After you have completed your ballot, click the "Vote" button. Note > that once you click this button, your votes will be cast and you will > not be able to make further changes, so please make sure you are > satisfied with your votes before clicking the "Vote" button. > > After you click the "Vote" button, the system will verify that you > have completed a valid ballot. If your ballot is invalid (e.g., you > duplicated a selection), it will return you to the previous voting > page. If your ballot is valid, your votes will be recorded and the > system will show you a notice that your votes were cast. > > Note that the election will close at 23:59 UTC on 5 April 2018. At > that time, the election committee will count the votes and present the > results to the current board for validation. After the current board > validates the results, the election committee will present the results > to the Members. > > Rob Clark, > on behalf of the X.Org elections committee

1 0

Re: 2018 Election voting OPEN
by Rob Clark 02 Apr '18

02 Apr '18

On Wed, Mar 21, 2018 at 8:40 PM, Rob Clark <robdclark(a)gmail.com> wrote: > To all X.Org Foundation Members: > > The X.Org Foundation's annual election is now open and will remain > open until 23:59 UTC on 5 April 2018. Reminder that the elections are open until midnight on Thurs, so if you have not already voted, please do. > Four of the eight director seats are open during this election, with > the four nominees receiving the highest vote totals serving as > directors for two year terms. > > There were six candidates nominated. For a complete list of the > candidates and their personal statements, please see the following: > > https://www.x.org/wiki/BoardOfDirectors/Elections/2018/ > > Here are some instructions on how to cast your vote: > > Login to the membership system at: https://members.x.org/ > > If you do not remember your password, you can click on the "lost > password" button and enter your user name. An e-mail will be sent to > you with your password. If you have problems with the membership > system, please e-mail membership(a)x.org. > > When you login you will see a row of buttons that will allow you to > update your info, list the members, list the open ballots and logout. > Below this you will see a list of open ballots, for which you can cast > votes. At the bottom of this page you will see another row of buttons > with the current privacy policy, the provisional By-laws, the > provisional Membership Agreement and instructions on how to contact > the admin. > > Note that if you click on the "Ballots" button at any time, you will > see a list of the open ballots. > > To cast your vote in a ballot, click on the "Cast" button to the right > of the ballot you wish to vote on. This will bring up another page > with the list of the candidates, and a question of whether or not to > approve the new By-laws. > > For the election: There is a pull-down selection box next to each > candidate. For your top choice, select "1". For your second choice, > select "2" and so forth. You should think of the numbers that you are > selecting as the ranking of your preferences. > > Note that you are NOT required to select your preferences for all four > positions. You can leave more than one blank. The only restriction is > that you cannot duplicate any of your choices (i.e., you can only > select one "1", one "2" and so forth). > > After you have completed your ballot, click the "Vote" button. Note > that once you click this button, your votes will be cast and you will > not be able to make further changes, so please make sure you are > satisfied with your votes before clicking the "Vote" button. > > After you click the "Vote" button, the system will verify that you > have completed a valid ballot. If your ballot is invalid (e.g., you > duplicated a selection), it will return you to the previous voting > page. If your ballot is valid, your votes will be recorded and the > system will show you a notice that your votes were cast. > > Note that the election will close at 23:59 UTC on 5 April 2018. At > that time, the election committee will count the votes and present the > results to the current board for validation. After the current board > validates the results, the election committee will present the results > to the Members. > > Rob Clark, > on behalf of the X.Org elections committee

1 0

[Bug 103881] New: HP Compaq dc5750 fails to resume from suspend
by bugzilla-daemon＠bugzilla.kernel.org 02 Apr '18

02 Apr '18

https://bugzilla.kernel.org/show_bug.cgi?id=103881 Bug ID: 103881 Summary: HP Compaq dc5750 fails to resume from suspend Product: Drivers Version: 2.5 Kernel Version: 4.1.6.i386 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) Assignee: drivers_video-dri(a)kernel-bugs.osdl.org Reporter: jefferym(a)gmail.com Regression: No Created attachment 186431 --> https://bugzilla.kernel.org/attachment.cgi?id=186431&action=edit Patch adding the dc5750 to the list of radeon rs4xxx quirks The HP Compaq dc5750 is unable to resume from the suspend state. With the system suspended and I press the power button on the front of the machine I expect it to wake up. When the button is pressed the HDD and CD drive lights activate briefly and the fan powers on. The video output does not appear to resume and stays black. I have to hard power the system to bring it back. Attempting to suspend/resume has this issue every time I have tried it. I observed this behavior on kernels 4.1.6 and 4.0.5. Setting devices in /sys/power/pm_debug resulted in the system failing to resume. The freezer method in /sys/power/pm_debug did not have an issue resuming. I enabled /sys/power/pm_trace and after the hard boot I was able to find a reasonable hash matches line: ' pci 0000:01:05.0: hash matches'. Additionally /sys/power/pm_trace_dev_match was able to resolve this to `radeon`. I was able to boot using a serial console and prevented the radeon driver from loading. In this state it was able to suspend and resume properly. From this state I let the radeon driver load again and the system would fail to resume from suspend. I was able to add this system to the list of RS480 quirks. The system was able to suspend and resume normally with the change. It worked with the Xserver running as well. It appears to be running normally. I have attached the patch I tested against the 4.0.5 and 4.1.6 kernels. Is there anything else I should test? -- You are receiving this mail because: You are watching the assignee of the bug.

1 8

[PATCH v3 0/8] drm/msm: Switch to atomic helpers
by Sean Paul 02 Apr '18

02 Apr '18

I spoke with Rob on IRC about the set and he preferred the private object be isolated in mdp5. So here's the atomic helper set rebased on Archit's series. One notable difference is that I've dropped the first patch from that series which added a new private_obj lock to the core. Instead, it's located in mdp5_kms along with the global state (same as the state_lock which is currently there). Thank you for your feedback thus far! Sean Archit Taneja (3): drm/msm/mdp5: Add global state as a private atomic object drm/msm/mdp5: Use the new private_obj state drm/msm: Don't subclass drm_atomic_state anymore Sean Paul (5): drm/msm: Refactor complete_commit() to look more the helpers drm/msm: Mark the crtc->state->event consumed drm/msm: Issue queued events when disabling crtc drm/msm: Remove msm_commit/worker, use atomic helper commit drm/msm: Switch to atomic_helper_commit() drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c | 1 + drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 10 + drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.c | 105 ++++++--- drivers/gpu/drm/msm/disp/mdp5/mdp5_kms.h | 27 +-- drivers/gpu/drm/msm/disp/mdp5/mdp5_mixer.c | 12 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_pipe.c | 20 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_smp.c | 17 +- drivers/gpu/drm/msm/msm_atomic.c | 236 +-------------------- drivers/gpu/drm/msm/msm_drv.c | 11 +- drivers/gpu/drm/msm/msm_drv.h | 7 +- drivers/gpu/drm/msm/msm_kms.h | 14 -- 11 files changed, 141 insertions(+), 319 deletions(-) -- Sean Paul, Software Engineer, Google / Chromium OS

1 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel April 2018