Summary: | GPU hangs on 2.6.38, triggered by mplayer | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Josh Triplett <josh> | ||||
Component: | DRM/Intel | Assignee: | Chris Wilson <chris> | ||||
Status: | CLOSED FIXED | QA Contact: | |||||
Severity: | major | ||||||
Priority: | medium | CC: | jbarnes, yan.i.li | ||||
Version: | XOrg git | ||||||
Hardware: | x86-64 (AMD64) | ||||||
OS: | Linux (All) | ||||||
Whiteboard: | |||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Josh Triplett
2011-04-02 10:13:14 UTC
Intel(R) GM45 chipset, Lenovo X200. Can you please attach the contents of /sys/kernel/debug/dri/0/i915_error_state after a hang? http://intellinuxgraphics.org/how_to_report_bug.html (In reply to comment #2) > Can you please attach the contents of /sys/kernel/debug/dri/0/i915_error_state > after a hang? http://intellinuxgraphics.org/how_to_report_bug.html Will do when I encounter another hang. Created attachment 45364 [details]
/sys/kernel/debug/dri/0/i915_error_state
GPU hang occurred again. i915_error_state attached.
0x0d900028: 0x61010004: STATE_BASE_ADDRESS 0x0d90002c: 0x00000001: general state base address 0x00000000 0x0d900030: 0x0dad9001: surface state base address 0x0dad9000 0x0d900034: 0x00000001: indirect state base address 0x00000000 0x0d900038: 0x10000001: general state upper bound 0x10000000 0x0d90003c: 0x10000001: indirect state upper bound 0x10000000 Should be fixed by: commit 23f9b14df7c102c1036134835dd5d1a508059858 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Sat Feb 12 10:42:34 2011 +0000 i965: Remove broken maximum base addresses from video WRONG. The hardware was never limited to 0x1000000 and the kernel can quite rightly place objects above that limit. Specifying such had no relation to reality, so why did we do it? TWICE! Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=34017 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> |
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.