Bug 21739

Summary: [945GME] intel freeze with attached batch buffer dump (EXA)
Product: xorg Reporter: martin <mnemo>
Component: Driver/intelAssignee: Carl Worth <cworth>
Status: RESOLVED INVALID QA Contact: Xorg Project Team <xorg-team>
Severity: critical    
Priority: medium    
Version: 7.4 (2008.09)   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description martin 2009-05-14 14:53:34 UTC
I'm forwarding this on behalf of an downstream Ubuntu user "Ramaddan" who posted logs in comments on this bug:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/365527

It's a batch buffer dump recorded after a freeze on 945GME using 2.6.3 ddx driver in EXA mode.

Logs:
http://launchpadlibrarian.net/26656026/LsPci.txt
http://launchpadlibrarian.net/26656027/XorgConf.txt
http://launchpadlibrarian.net/26656028/XorgLog.txt
http://launchpadlibrarian.net/26656029/XorgLogOld.txt

Batch buffer dump:
http://launchpadlibrarian.net/26332867/dri_debug.tgz
Comment 1 martin 2009-05-14 14:57:16 UTC
Of course, since this is 2.6.3 we can't rule out that this freeze is an instance of the freeze bug keithp fixed with the commit below. I don't know what to look for in the batch buffer dump though so I can't tell (is there an _easy_ method for distinguishing different freeze bugs by trivial inspection?).

commit 1142353b487c155a31011923fbd08ec67e60f505
Author: Keith Packard <keithp@keithp.com>
Date:   Fri May 1 11:44:13 2009 -0700

    intel_batch_start_atomic: fix size passed to intel_batch_require_space (*4)
Comment 2 Eric Anholt 2009-05-15 17:17:36 UTC
The dump doesn't include the batchbuffer (kernel too old, it looks like), so we can't really see anything.  But you definitely need that fix in your packages.
Comment 3 martin 2009-05-16 01:56:32 UTC
@Eric, ah okay... That's too bad, I suggest closing this bug report as INVALID then (don't expect more info from the downstream bug reporter).

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.