Bug 47162 - Screen went black for seconds, 100% cpu usage on dri2Throttle/sched_yield
Summary: Screen went black for seconds, 100% cpu usage on dri2Throttle/sched_yield
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/r600 (show other bugs)
Version: 8.0
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-09 10:14 UTC by Cyp
Modified: 2019-09-18 18:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Backtrace from program that froze (used 100% of a cpu) after screen went black. (2.01 KB, text/plain)
2012-03-09 10:14 UTC, Cyp
Details

Description Cyp 2012-03-09 10:14:58 UTC
Created attachment 58245 [details]
Backtrace from program that froze (used 100% of a cpu) after screen went black.

Only happened once, using a program that I often use, so probably not very reproducible.

Screen went completely black for a few (2?) seconds.
When the screen went back to normal, the OpenGL program I was using was frozen (not refreshing), and using 100% cpu.
I attached a debugger, and got a backtrace.
No debug info for /usr/lib64/dri/r600_dri.so, don't know why.

Not using compositing.

Linux version 2.6.39-gentoo (gcc version 4.4.6 (Gentoo 4.4.6-r1 p1.0, pie-0.4.5) ) #3 SMP Fri Aug 26 20:15:20 CEST 2011

Using gentoo:
x11-base/xorg-drivers 1.11
x11-base/xorg-server 1.11.4
x11-drivers/radeon-ucode 20110531
x11-libs/libdrm 2.4.31

Part of glxinfo:
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.4
client glx vendor string: Mesa Project and SGI
client glx version string: 1.4
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV710
OpenGL version string: 2.1 Mesa 8.0
OpenGL shading language version string: 1.20

Nothing in /var/log/Xorg.0.log.

dmesg:
radeon 0000:01:00.0: GPU lockup CP stall for more than 200213msec
------------[ cut here ]------------
WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x247/0x2e5()
Hardware name: G31MX-S2
GPU lockup (waiting for 0x05A4BE07 last fence id 0x05A4BDFC)
Modules linked in:
Pid: 3297, comm: X Not tainted 2.6.39-gentoo #3
Call Trace:
 [<ffffffff810319c4>] warn_slowpath_common+0x80/0x98
 [<ffffffff81031a70>] warn_slowpath_fmt+0x41/0x43
 [<ffffffff812ef5be>] radeon_fence_wait+0x247/0x2e5
 [<ffffffff8104831d>] ? wake_up_bit+0x25/0x25
 [<ffffffff812efdde>] radeon_sync_obj_wait+0xc/0xe
 [<ffffffff812c13f6>] ttm_bo_wait+0xbc/0x151
 [<ffffffff812c205d>] ? ttm_bo_list_ref_sub+0x23/0x25
 [<ffffffff8130314c>] radeon_gem_wait_idle_ioctl+0x81/0xe8
 [<ffffffff812adf2c>] drm_ioctl+0x271/0x338
 [<ffffffff813030cb>] ? radeon_gem_set_tiling_ioctl+0x9d/0x9d
 [<ffffffff810b6925>] do_vfs_ioctl+0x42e/0x47d
 [<ffffffff810b69b6>] sys_ioctl+0x42/0x65
 [<ffffffff816b3c3b>] system_call_fastpath+0x16/0x1b
---[ end trace 8eb2c2cc05afbcd4 ]---
[drm] Disabling audio support
HDMI hot plug event: Pin=3 Presence_Detect=0 ELD_Valid=0
radeon 0000:01:00.0: GPU softreset 
radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0xA0021028
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00000002
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200000C0
radeon 0000:01:00.0:   R_008020_GRBM_SOFT_RESET=0x00007FEE
radeon 0000:01:00.0: R_008020_GRBM_SOFT_RESET=0x00000001
radeon 0000:01:00.0:   R_008010_GRBM_STATUS=0x00003028
radeon 0000:01:00.0:   R_008014_GRBM_STATUS2=0x00000002
radeon 0000:01:00.0:   R_000E50_SRBM_STATUS=0x200000C0
radeon 0000:01:00.0: GPU reset succeed
radeon 0000:01:00.0: WB enabled
[drm] ring test succeeded in 1 usecs
[drm] ib test succeeded in 1 usecs
[drm] Enabling audio support
HDMI hot plug event: Pin=3 Presence_Detect=0 ELD_Valid=0
Comment 1 Michel Dänzer 2012-03-10 01:19:06 UTC
(In reply to comment #1)
> OpenGL version string: 2.1 Mesa 8.0

The r600g driver from Mesa 8.0.1 or newer should deal with this more gracefully.
Comment 2 GitLab Migration User 2019-09-18 18:59:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/405.


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.