Bug 59721 - [r600g] drm_mm_remove_node oops GPU hang while restoring firefox windows
Summary: [r600g] drm_mm_remove_node oops GPU hang while restoring firefox windows
Status: RESOLVED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-22 16:59 UTC by Shawn Starr
Modified: 2013-09-05 13:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
Kernel messages from session from start to crash point (90.45 KB, text/plain)
2013-01-22 16:59 UTC, Shawn Starr 		no flags Details
View All

Description Shawn Starr 2013-01-22 16:59:24 UTC 
Created attachment 73462 [details]
Kernel messages from session from start to crash point

While the laptop was left on overnight, monitor VGA port was in DPMS, LVDS was disabled (I disable this output so as to not keep laptop lid open)

After the external LCD monitor via VGA woke up from DPMS mode, I viewed some emails, then I tried to restore firefox windows, to which the screen froze then it went into a GPU reset until i managed to switch VT to console

complete kernel message from that days session is attached to bug

kernel: 3.8.0-0.rc4.git1.1.fc19.x86_64
drm: libdrm-2.4.40-1.fc18.x86_64
mesa: mesa-dri-drivers-9.0.1-3.fc18.x86_64
Comment 1 Shawn Starr 2013-01-22 17:03:28 UTC 
Comment on attachment 73462 [details]
Kernel messages from session from start to crash point

In addition,

It was noted in /sys/kernel/debug/dri/0/radeon_vram_mm

that I had very little VRAM memory left and no 3D activities going on
Comment 2 Jerome Glisse 2013-04-24 18:34:07 UTC 
Still an issue with updated kernel ?
Comment 3 Shawn Starr 2013-04-24 18:37:55 UTC 
I am running 3.9.0-rc6 kernel and will confirm this week to be sure.
Comment 4 Shawn Starr 2013-09-05 13:52:17 UTC 
Close it, dont see this issue

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.