Bug 26966

Summary: Blender 2.50 alpha1 crash with intel_regions.c:195 error
Product: Mesa Reporter: Petar Velkovski <pvelkovski>
Component: Drivers/DRI/i965Assignee: Eric Anholt <eric>
Status: RESOLVED FIXED QA Contact:
Severity: critical    
Priority: high CC: anssi, eric, pvelkovski, sarvatt
Version: git   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Xorg log

Description Petar Velkovski 2010-03-08 15:44:38 UTC
Created attachment 33871 [details]
Xorg log

When trying to start blender-2.50-alpha1-linux-glibc27-i686, Blender crashes and I get this error message:

blender: intel_regions.c:195: intel_region_alloc: Assertion `aligned_pitch == pitch * cpp' failed.


OS: Ubuntu 9.10 32bit
Kernel: 2.6.33-020633-generic (Vanilla kernel)
Xorg: 7.4
Mesa: 7.8.0~git20100304.4c0c728b
libdrm: 2.4.19+git20100307.04fd3872
intel driver: 2.10.901+git20100305.1cd55642

I believe this bug was introduced in the last 3-4 days so it would be easier to locate!
Comment 1 Gordon Jin 2010-03-08 17:31:03 UTC
The error info looks like bug#26901, which has been fixed in the latest libdrm. Can you double check if you've already included that patch?
Comment 2 Petar Velkovski 2010-03-08 20:35:04 UTC
(In reply to comment #1)
> The error info looks like bug#26901, which has been fixed in the latest libdrm.
> Can you double check if you've already included that patch?
> 

As stated in my previous post, the libdrm version I am using is 2.4.19+git20100307.04fd3872. The version number comes from the Ubuntu xorg-edgers package naming conversion. They include the first 8 numbers of the latest commit included in the deb package they've built. Bug #26901 mentions the libdrm with latest commit 04fd3872ee8bd8d5e2c27740508c67c2d51dbc11. As you can see we are talking about the same thing :). I will write a message to the person that built the package and see what he has to say.
Comment 3 roberth 2010-03-08 21:37:34 UTC
yep, it is the latest libdrm(In reply to comment #2)
> (In reply to comment #1)
> > The error info looks like bug#26901, which has been fixed in the latest libdrm.
> > Can you double check if you've already included that patch?

Yeah it is current libdrm. Petar, try disabling the texture tiling option in driconf that was just changed to be enabled by default right before the mesa 7.8 checkout you are using if you need to use blender until it's fixed. I am still getting the same assert using mutter or cairo-gl even with mesa master from a few hours ago (bc632d04370566c1156cbd0345fe303834f0b910) on my 945 if I have texture tiling enabled.
Comment 4 Tobias Jakobi 2010-03-10 14:10:21 UTC
Same problem here with a different application: mplayer with GL video output

intel_regions.c:193: intel_region_alloc: Assertion `aligned_pitch == pitch * cpp' failed.

Crashes immediately, no interesting stuff found in the kernel log

Setup:
xorg-server-1.7.5.901
libdrm, mesa, xf86-video-intel all git master
vanilla-linux-2.6.33
Comment 5 Tobias Jakobi 2010-03-10 14:12:10 UTC
My mplayer commandline:
vo_settings="gl:yuv=2:rectangle=2:force-pbo"
misc_settings="-fs -ass -dr -noslices"
mplayer $misc_settings -vo $vo_settings -- "${1}"
Comment 6 Tobias Jakobi 2010-03-10 14:17:04 UTC
Also here disabling texture tiling helps to avoid the issue - however this kills the benefit of using GL over Xv.
Comment 7 Gordon Jin 2010-03-11 17:41:07 UTC

*** This bug has been marked as a duplicate of bug 27030 ***
Comment 8 Eric Anholt 2010-03-16 12:44:41 UTC
Ouch.  This is *not* a duplicate of the other bug.
Comment 9 Eric Anholt 2010-03-17 11:25:47 UTC
commit da011faf48155a5c02ebc1fe1fa20a4f54b8c657
Author: Eric Anholt <eric@anholt.net>
Date:   Tue Mar 16 16:20:03 2010 -0700

    intel: Rely on allocated region pitch for the miptree pitch.
    
    Bug #26966: 945 miptree pitch disagreement with libdrm.
Comment 10 Anssi Hannula 2010-03-24 10:17:14 UTC
I guess this should go to 7.8 branch as well.

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.