Created attachment 99837 [details] dmesg [BDW] kernel v3.15-rc7: GPU HANG: ecode 0:0x0fdf00ac, in Xorg [1060], reason: Ring hung, action: reset This is only happened on broadwell platform. Attached the /sys/class/drm/card0/error and dmesg Please help to check it. if you need any information, please let me know. Thanks!
Created attachment 99838 [details] /sys/class/drm/card0/error
Is this a regression? If so, please bisect.
Eva, I'm still waiting for some information from you. 1. Is this reproducible? 1a. If yes, please submit dmesg with drm.debug=0x6 1b. If no, please lower the priority 2. Is this a regression? 2a. If yes, please bisect. 3. What were you doing at the time of the hang? 4. Did the system recover after the hang. As for the bug itself, the PDPs seem to have lost their minds on the render ring. 5. Please try to reproduce with rc6 disabled.
> 1. Is this reproducible? > 1a. If yes, please submit dmesg with drm.debug=0x6 Eva:Yes, please refer attachment dmesg_315rc8.log > 1b. If no, please lower the priority > 2. Is this a regression? > 2a. If yes, please bisect. Eva: It seems 3.15 has the issue, but 3.14 has no issue. we will spend hours to verify whether it is a regression. which branch do you suggest to bisect? > 3. What were you doing at the time of the hang? Eva: I enter to tty4 to get the dmesg and error. if do not press tty4, system will hang and can't enter to tty even if press tty4. > 4. Did the system recover after the hang. Eva: It can't recover. > 5. Please try to reproduce with rc6 disabled. Eva: It still happen with rc6 disabled.
Created attachment 100380 [details] dmesg with kernel 3.15-rc8
3.15 formal kernel also has the issue.
Created attachment 102956 [details] dmesg We just checked kernel 3.16 rc5 on Broadwell platform, it still can't enter to desktop, but there is no GPU HANG messages. Please refer attachment dmesg with drm.debug=0xe. 3.16 rc5 is OK on Baytrail-M and HSWwell.
Please try 3.17-rc4.
(In reply to comment #8) > Please try 3.17-rc4. 3.17-rc4 kernel can enter to desktop and it is OK. BTW, 3.15 and 3.16 kernel both version has the issue, but 3.17 kernel fixed it. Thanks!
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.