Bug 92168

Thanks :)

(The downstream bug says he could reproduce the segfault with mesa-10.6.[1-3])

(In reply to Matt Turner from comment #1)
> Thanks :)
> 
> (The downstream bug says he could reproduce the segfault with
> mesa-10.6.[1-3])

Let me join.
I see this happening on a system using Ati FirePro 5950M and on another with Ati FirePro V4800.
The symptom can be triggered using a range of mesa versions - the latest I've tried was 11.0.
It only occurs after bumping xorg-seever to 1.17.2 and I don't experience it running xorg version 1.17.1.

Thanks:
Dw.

Please attach the full Xorg.0.log file.

Created attachment 118532 [details]
Xorg log from the crash (Starting KDE from KDM)

Created attachment 118533 [details]
Xorg log with the same setup starting Fluxbox from KDM)

Can you bisect xserver and/or attach a gdb backtrace of the crash?

If you tell me how to do it I can try.

For getting a gdb backtrace, see http://wiki.x.org/wiki/Development/Documentation/ServerDebugging/ .

For bisecting, search for "git bisect howto".

https://bugs.gentoo.org/show_bug.cgi?id=554606#c11 (same commentor as comment #2 here) says that 1.17.1-r1 works and 1.17.2-r1 fails. In addition to the changes from 1.17.1 -> 1.17.2 (of which there are a few glamor commits), we also added this patch [1].

Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will let us determine whether the patch at [1] is at fault.

[1] https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/xorg-server-1.17.2-uninit-clientsWritable.patch

(In reply to Matt Turner from comment #9)
> https://bugs.gentoo.org/show_bug.cgi?id=554606#c11 (same commentor as
> comment #2 here) says that 1.17.1-r1 works and 1.17.2-r1 fails. In addition
> to the changes from 1.17.1 -> 1.17.2 (of which there are a few glamor
> commits), we also added this patch [1].
> 
> Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will
> let us determine whether the patch at [1] is at fault.
> 
> [1]
> https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/
> xorg-server-1.17.2-uninit-clientsWritable.patch

I didn't have time to test yesterday. I hope I can spend some time on this issue during the weekend. Let me report back later.
According to the log attached I may have a different issue compared to Dimitar, because in my case Xorg cannot even detect my card and dies early during launch. I will attach my version of failing Xorg as well.

Thx: Dw.

Created attachment 118828 [details]
working Xorg log file 1.17.1-r1

Created attachment 118829 [details]
failing Xorg log file 1.17.2

(In reply to Matt Turner from comment #9)
> https://bugs.gentoo.org/show_bug.cgi?id=554606#c11 (same commentor as
> comment #2 here) says that 1.17.1-r1 works and 1.17.2-r1 fails. In addition
> to the changes from 1.17.1 -> 1.17.2 (of which there are a few glamor
> commits), we also added this patch [1].
> 
> Attila, could you try plain xorg-server-1.17.2 (without the -r1)? That will
> let us determine whether the patch at [1] is at fault.
> 
> [1]
> https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/files/
> xorg-server-1.17.2-uninit-clientsWritable.patch

It fails with 1.17.2. In my case Xorg dies early with "(EE) No devices detected". So this might be a different problem compared to Dimitar's.

Please note, that the working log contains this line after probing the card:
(WW) Falling back to old probe method for modesetting
(II) [KMS] Kernel modesetting enabled.

While failing version says:
(II) modeset(G0): using drv /dev/dri/card0
(EE) No devices detected.

Do I have a configuration problem?

Thanks: Dw.

(In reply to Attila Tóth from comment #13)
> It fails with 1.17.2. In my case Xorg dies early with "(EE) No devices
> detected". So this might be a different problem compared to Dimitar's.

Looks like it, please file your own report. Can you bisect?

(In reply to Michel Dänzer from comment #14)
> (In reply to Attila Tóth from comment #13)
> > It fails with 1.17.2. In my case Xorg dies early with "(EE) No devices
> > detected". So this might be a different problem compared to Dimitar's.
> 
> Looks like it, please file your own report. Can you bisect?

I haven't lost my bisect virginity, yet. I do my first bisect and get back.

Hello guys,

It seems this issue is now resolved. Yesterday I saw some new xorg-server packages with a fix for a crash because of xproto. I updated two systems to xorg-server 1.17.4. mesa 11.0.4, one with xproto 7.0.28 (the problematic one) and one with 7.0.27, both are so far working fine.

We believe this was due to the xserver not being compatible with the changes in xproto-7.0.28. xserver-1.17.4 is compatible.