[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#407036: xserver-xorg: Server crashes each time after hibernate with suspend2



Hi Brice, ssh from another machine and screen is a good idea thanks. I
tried that and gdb attaches properly to X but when I suspend the
laptop it crashes (ie the whole machine crashes, not just the X
server; I had to force a power down then power up again). That is even
with the old xserver that normally suspends ok.

I also tried again for a core file (I didn't have ulimit set properly
and now I do), but no core file is created when the resume crashes my
laptop (using the latest xserver-xorg-core). I do have the
NoTrapSignals option set and it is recognized in the Xorg log file.

So run out of things to try again ... 

Bruce

On Sun, Jun 17, 2007 at 01:31:38PM +0200, Brice Goglin wrote:
> Bruce MacDonald wrote:
> > Hi, Any ideas for debugging this problem? I can't login from a second
> > machine since the resume script has to remove and reinstall the
> > network driver for both wired and wireless. I couldn't get a core dump
> > by setting the NoTrapSignals option in ServerFlags. I tried a script
> > suggested on x.org for server debugging but X would not start at all, 
> > from
> >
> > http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
> >
> > But I've never debugged the X server before.
> >
> > Bruce
> >   
> 
> One idea would be to keep gdb in a screen that you attach/detach from ssh:
> * login through ssh before suspend, launch "screen", and attach "gdb -p
> $(pidof X)" from there
> * suspend/resume, and make sure the network is back
> * login again by ssh again, reacquire the screen with something like
> "screen -rd"
> * once X has crashed, work in gdb with 'bt full' or so
> 
> Somebody put some Debian-specific hints about debugging (including with
> a coredump) at http://wiki.debian.org/XStrikeForce/XserverDebugging by I
> never actually tried it.
> 
> Brice
> 
> 
> 



Reply to: