Hello Joonyoung, On 02/06/2015 06:27 AM, Joonyoung Shim wrote: > On 02/05/2015 11:45 PM, Javier Martinez Canillas wrote: >> >> I also tested on an Exynos5420 Peach Pit Chromebook and both the "Power >> domain power-domain disable failed" message and the system crash are gone. >> > > Really gone out "Power domain power-domain disable failed" message? > > Still i get the message from second try, > > # modetest -M exynos -s 23@21:1920x1080 > setting mode 1920x1080@XR24 on connectors 23, crtc 21 > > # modetest -M exynos -s 23@21:1920x1080 > setting mode 1920x1080@XR24 on connectors 23, crtc 21 > > [ 39.608881] Power domain power-domain disable failed > # modetest -M exynos -s 23@21:1920x1080 > setting mode 1920x1080@XR24 on connectors 23, crtc 21 > > [ 42.827637] Power domain power-domain disable failed > ... > You are right, I tested that if I execute: # for val in 1 0; do echo $val > /sys/class/drm/card0/device/graphics/fb0/blank; done many times I see the "Power domain power-domain disable failed" message again and there is no output in the HDMI display when dpms on. But even in that case, the imprecise external abort does not happen when the exynos_mixer driver tries to access the mixer registers and the system does not crash anymore. So I think that Andrzej's patches are at least a step in the right direction. Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
