mesa 7.7 DRI crash, assertion in driNewRenderbuffer()

Bug #515846 reported by Badalian Vyacheslav
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mesa
Fix Released
High
X.Org X server
Invalid
Undecided
Unassigned
mesa (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

root@ubuntu:~# lspci
00:00.0 Host bridge: VIA Technologies, Inc. P4M266 Host Bridge
00:01.0 PCI bridge: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP]
00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 80)
00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82)
00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74)
01:00.0 VGA compatible controller: S3 Inc. VT8375 [ProSavage8 KM266/KL266]

root@ubuntu:~# cat /var/log/kdm.log
...
record: RECORD extension enabled at configure time.
record: This extension is known to be broken, disabling extension now..
record: http://bugs.freedesktop.org/show_bug.cgi?id=20500
(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
(EE) PreInit returned NULL for ""ImPS/2 Generic Wheel Mouse""
(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device
(EE) PreInit returned NULL for ""Macintosh mouse button emulation""
QFont::fromString: Invalid description 'Serif,20,5,0,50,0'
QFont::fromString: Invalid description 'Sans Serif,10,5,0,50,0'
QFont::fromString: Invalid description 'Sans Serif,10,5,0,75,0'
X: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.

root@ubuntu:~# glxinfo
name of display: :0.0
glxinfo: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.
Аварийный останов (core dumped)

Revision history for this message
Badalian Vyacheslav (slavon-net) wrote :

Hmmm... Lucid is release name... not text editor

affects: lucid → xorg-server
Revision history for this message
Selenia (samuraihell666) wrote :

I am using the Lucid version of the xserver and intel xorg video driver on Karmic and still experience this. I have identical installs for ATI and nvidia for the xserver versions and other components with their latest drivers and see no such issue. I am not so sure this is an issue with the xserver itself. It seems to be an issue with the Intel video driver.

lagmeister@1337-desktop:~$ glxinfo
name of display: :0.0
glxinfo: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.
Aborted

Ironically, the driver is more stable than its stable x-updates counterpart(solves freezing in Adobe Flash and other issues), but they seemed to have it right in the version in Jaunty and the regular Karmic package. So, it seems the driver is going downhill, at least for i810.

lagmeister@1337-desktop:~$ lspci | grep Graphics
00:00.0 Host bridge: Intel Corporation 82810E DC-133 (GMCH) Graphics Memory Controller Hub (rev 03)
00:01.0 VGA compatible controller: Intel Corporation 82810E DC-133 (CGC) Chipset Graphics Controller (rev 03)

I will stick with this version for now in hopes for a correction. I can always purge the PPA(how I installed this version and the x-updates one before) later if I have to. Kinda sad since upgrading like this has improved performance for all but this gfx adaptor. None of the others are Intel, however.

Revision history for this message
In , Bugzi09-fdo-tormod (bugzi09-fdo-tormod) wrote :

Created an attachment (id=33530)
full backtrace

glxinfo (or the DRI-enabled) xserver crashes with this assertion in mesa 7.7 on a number of drivers:

glxinfo: ../common/drirenderbuffer.c:69: driNewRenderbuffer: Assertion `format == 0x1908 || format == 0x8050 || format == 0x8058 || format == 0x81A5 || format == 0x81A6 || format == 0x81A7 || format == 0x8D48' failed.

From looking at the code, I think this happened with http://cgit.freedesktop.org/mesa/mesa/commit/?h=mesa_7_7_branch&id=1160acbfea986a821761d18f5f14d5d2cb0dea8c

The assertion should probably be updated or removed.

Revision history for this message
In , Bugzi09-fdo-tormod (bugzi09-fdo-tormod) wrote :
Revision history for this message
In , Brian-e-paul (brian-e-paul) wrote :

I've removed the obsolete assertion. Commit 293f4d51b473783d5c5ab773a1c438e0a2fe46f2.

As I've suspected, the older DRI drivers aren't getting much testing.

Revision history for this message
Tormod Volden (tormodvolden) wrote : Re: After update to lucid dri crash

Also reported here http://bugs.archlinux.org/task/17638 but launchpad does not let me add the link. Downgrading mesa works around it apparently.

Changed in xorg-server:
status: New → Invalid
Changed in mesa (Ubuntu):
status: New → Confirmed
summary: - After update to lucid dri crash
+ mesa 7.7 DRI crash, assertion in driNewRenderbuffer()
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Changed in mesa:
importance: Undecided → Unknown
status: New → Unknown
Changed in mesa:
status: Unknown → Confirmed
Revision history for this message
Tormod Volden (tormodvolden) wrote :
Revision history for this message
Luca Aluffi (aluffilu) wrote :

I'll test as soon updates will bring down the package.

Revision history for this message
Tormod Volden (tormodvolden) wrote :

The fix will be included in 7.7-4ubuntu1.

Changed in mesa (Ubuntu):
status: Confirmed → Fix Committed
Changed in mesa:
status: Confirmed → Fix Released
Revision history for this message
Luca Aluffi (aluffilu) wrote :

Great job!
Now it works and all gears spin around.

Sadly, we have to get back to my original issue https://bugs.launchpad.net/bugs/526760. Is there anything I can do to help?

Changed in mesa (Ubuntu):
status: Fix Committed → Fix Released
Changed in mesa:
importance: Unknown → High
Changed in mesa:
importance: High → Unknown
Changed in mesa:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.