can I do it via byobu on the local system (so I can reatach the screen in
case of crash) or should I do it via ssh from a different machine?
I really do not know how long it would take to actually hit gold here, so
think I cannot keep using two systems at once for several days... any
ideas?
every time I enter gdb and try to attach the runnig Xorg pid, it freezes...
if I try to run if with the -keeptty -dumbSched options, it tells me Xorg is
already running (of course)... if I kill it, it simply respawns... the guide
seems pretty useless cause if you follow the steps there, you cannot get any
backtrace whatsoever. How can I ever get X to run inside gdb? (I know I
could sudo /etc/init.d/gdm stop, but the only time it is mentioned there, is
totally unrelated with the steps to get the backtrace)
that said, I did manage to start inside gdb and pretty much as soon as I
have loged in, it halted with a SIGUSR1 adn wont resume no matter what I
try... I am not sure what I am doing wrong or if that could be related with
the issue:
(gdb) run -keeptty -dumbSched
Starting program: /usr/bin/Xorg -keeptty -dumbSched
[Thread debugging using libthread_db enabled]
X.Org X Server 1.10.1
Release Date: 2011-04-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-29-server i686 Ubuntu
Current Operating System: Linux fpc 2.6.38-996-generic #201103251543 SMP Fri
Mar 25 17:11:59 UTC 2011 i686
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-996-generic
root=UUID=4b092518-b996-429c-b41e-9bf39183163c ro quiet splash vt.handoff=7
Build Date: 19 April 2011 03:33:17PM
xorg-server 2:1.10.1-1ubuntu1 (For technical support please see
http://www.ubuntu.com/support)
Current version of pixman: 0.20.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/Xorg.0.log, Time: Thu Apr 28 20:10:11 2011
(==) Using system config directory /usr/share/X11/xorg.conf.d
Program received signal SIGUSR1, User defined signal 1.
0xb7fe1424 in __kernel_vsyscall ()
2011/4/28 Bryce Harrington 771...@bugs.launchpad.net
Hi PresuntoRJ, of course you're not expected to know such details. ;-)
The 'xorg' package is a general inbox, and bugbot takes care of figuring
out your video driver, symptoms, and so on, and moves the bug to the
right location.
Your system appears to be encountering a segmentation fault in the X
server, resulting in it crashing. gdm restarts an X session which is
why you're returned to the login screen each time.
The out of the blue nature of it is troubling. X segmentation faults
are pretty rare and tend to occur only under specific circumstances. So
there are *usually* steps to reproduce them. When there isn't, I start
suspecting hardware faults such as bad memory chips. But let's assume
it to be a software bug in X first.
Can you collect a full backtrace? This will help tell me where in the
code exactly that the crash is happening. Directions for doing this are
at http://wiki.ubuntu.com/X/Backtracing
** Changed in: xserver-xorg-video-intel (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a direct subscriber
of the bug.
https://bugs.launchpad.net/bugs/771837
Title:
xorg died (gracefully to login) but without ado
To unsubscribe from this bug, go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/771837/+subscribe
--
Fábio Leitão
..-. .- -... .. --- .-.. . .. - .- --- ...-.-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771837
Title:
xorg died (gracefully to login) but without ado
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
