[i815] xserver segfaults in DRIFinishScreenInit+0xb1

I have a similar problem with openchrome display driver and Unichrome IGP.

Backtrace:
0: X(xorg_backtrace+0x3b) [0x813281b]
1: X(xf86SigHandler+0x55) [0x80c5dc5]
2: [0xb7f95400]
3: /usr/lib/xorg/modules/extensions//libdri.so(DRIFinishScreenInit+0xb1) [0xb7a50821]
4: /usr/lib/xorg/modules/drivers//openchrome_drv.so(VIADRIFinishScreenInit+0x58e) [0xb7a0beee]
5: /usr/lib/xorg/modules/drivers//openchrome_drv.so [0xb79f6000]
6: X(AddScreen+0x19d) [0x80711dd]
7: X(InitOutput+0x206) [0x80adeb6]
8: X(main+0x1e1) [0x80718d1]
9: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7b6c775]
10: X [0x8070f61]
Saw signal 11. Server aborting.
(II) CHROME(0): VIALeaveVT

Snap to VIA above.

I was having issues with Intrepid crashing when it got to the login screen, I tried Jaunty and the system freezes on boot. In single user mode I can read the Xorg.0.log and it's identical to that above.

Chris, you can try deleting via.ko kernel module from /lib/modules. Then after reboot your system won't be able to load this module -> X won't be able to use DRI -> no error while launching X. This is a dirty workaround while the problem persists. Or you can just use vesa driver for X :)

If I do that will it put it back in when there's a fix, because I
often forget these things. Also it's on a media centre machine so I'm
not sure if I NEED DRI or not...

On 5 Jan 2009, at 19:51, Andrey Melentyev wrote:

> Chris, you can try deleting via.ko kernel module from /lib/modules.
> Then
> after reboot your system won't be able to load this module -> X
> won't be
> able to use DRI -> no error while launching X. This is a dirty
> workaround while the problem persists. Or you can just use vesa driver
> for X :)
>
> --
> [i815] xserver segfaults in DRIFinishScreenInit+0xb1
> https://bugs.launchpad.net/bugs/310075
> You received this bug notification because you are a direct subscriber
> of the bug.

If you do that, to put it back when the bug will be fixes, you will have to reinstall the current kernel version with apt/synaptic or wait for another kernel to update. You can also save this kernel module somewhere and put it back by hand.

Anyway, if you update your system regularly, some day your kernel module will be there again for you.

[This is an automated message]

Hi jouni-mettala,

Please attach the output of `lspci -vvnn` too.

I am having the same issue on my i810.

Note that I am getting this error in dmesg:
[ 178.112038] [drm:i810_wait_ring] *ERROR* space: 65520 wanted 65528
[ 178.112102] [drm:i810_wait_ring] *ERROR* lockup

I'll attach:
output of lspci -vvnn
output of dmesg
Xorg.0.log with backtrace

This bug seems to be related to bug 308485 in xserver-xorg-video-r128 and bug 311544 in xserver-xorg-video-savage.

There are too many open bugs for this problem. Consolidating in bug #319210.