[ubuntu-x] Xorg crash on PS3/hardy

[Timo Aaltonen]

On Tue, 15 Apr 2008, Bryce Harrington wrote:

> On Tue, Apr 15, 2008 at 05:38:11PM +0100, Dan Munckton wrote:
>> Hi ubuntu-x list
>>
>> I'm trying to follow up on the next big Playstation 3 + hardy show
>> stopper:
>> Crash at startup on PS3 (hardy)
>> https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/217647/
>>
>> I've been chatting with cjwatson about it on IRC, his gut feeling is
>> this is memory corruption.
>>
>> In the short-term I am hoping that re-applying explicit xorg.conf from
>> the gutsy install will help us workaround the problem for the first
>> hardy release.
>>
>> In the long term does anyone have any ideas what could be causing this
>> crash?
>
> From the Xorg.0.log (thanks for including it!)
>
> (II) LoadModule: "vesa"
> (WW) Warning, couldn't open module vesa
> (II) UnloadModule: "vesa"
> (EE) Failed to load module "vesa" (module does not exist, 0)
> (II) LoadModule: "mouse"
>
> Looks like it had trouble loading the vesa driver.  Should that work on
> ppc?  Maybe try specifying it to use the framebuffer or other driver?
>
>> I've seen the X debugging tips on the wiki, I will try these in the next
>> few days. If it is a memory corruption issue what is going to be the
>> quickest way to nail this? Would valgrind work with X?
>
> I've not tried valgrind against X.  I would probably suggest the
> standard approach for troubleshooting crash bugs - install debug symbols
> for the server and drivers, and then obtain a full backtrace.  Then
> examine pointers around the point of crash for endianness issues, not
> being properly defined, etc.
>
> When you get further along with the troubleshooting (like once you have
> a backtrace), make sure to open a bug upstream with Xorg on it.

Julien Cristau pointed out on #ubuntu-x that upstream xorg-server commit 
9500033b9ecdfaf5a56a4355ffc94d74cb17ca17 should fix this, see Debian bug 
472823:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=472823

t