Bug 21621

Summary: [G45] Random hangs
Product: xorg Reporter: Sven Arvidsson <sa>
Component: Driver/intelAssignee: Eric Anholt <eric>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
backtrace at the time of the hang
none
dmesg output after hang
none
Xorg log after hang
none
gpu dump after hang none

Description Sven Arvidsson 2009-05-07 13:34:15 UTC
Created attachment 25606 [details]
backtrace at the time of the hang

I'm having X hangs, more or less at random. Killing X results in wedged hardware and a reboot is necessary.

I'm not using KMS.

System environment:
-- chipset: G45 / ICH10R
-- system architecture: 64-bit
-- Linux distribution: Debian unstable
-- Machine or mobo model: Asus P5Q-EM
-- Display connector: DVI
-- xf86-video-intel: 2.7.99.1
-- xserver: 1.6.1
-- mesa: 7.4.1
-- drm: 2.4.9
-- kernel: 2.6.30-rc4 (debian package)
Comment 1 Sven Arvidsson 2009-05-07 13:34:57 UTC
Created attachment 25607 [details]
dmesg output after hang
Comment 2 Sven Arvidsson 2009-05-07 13:35:18 UTC
Created attachment 25608 [details]
Xorg log after hang
Comment 3 Eric Anholt 2009-05-09 08:07:25 UTC
Backtraces are never useful for GPU hangs.  But intel_gpu_dump output could be very useful.
Comment 4 Sven Arvidsson 2009-05-09 14:13:23 UTC
Created attachment 25676 [details]
gpu dump after hang
Comment 5 Sven Arvidsson 2009-05-09 14:14:22 UTC
Output from intel_gpu_dump after such a hang is attached.
Comment 6 Jesse Barnes 2009-05-11 11:21:59 UTC
Adjusting severity: crashes & hangs should be marked critical.
Comment 7 Eric Anholt 2009-05-15 17:10:44 UTC
Thanks for the dump!  Looks like another copy of #21488.

0x0fffff80:      0x00000000: MI_NOOP
0x0fffff84:      0x05000000: MI_BATCH_BUFFER_END
0x0fffff88: HEAD 0x00000000: MI_NOOP


*** This bug has been marked as a duplicate of bug 21488 ***

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.