From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.sf.net, LKML <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Eric Anholt <eric@anholt.net>
Subject: Re: [REGRESSION] i915 VT switch with AIGLX causes X lock up
Date: Tue, 24 Feb 2009 22:59:30 +0000 [thread overview]
Message-ID: <20090224225930.GA3745@silver.sucs.org> (raw)
In-Reply-To: <200902240844.09424.jbarnes@virtuousgeek.org>
On Tue, Feb 24, 2009 at 08:44:09AM -0800, Jesse Barnes wrote:
> Can you get a backtrace of the hung process, maybe by logging in from another
> machine and using gdb on the Xorg process?
(Done via sleep 30s; gdb.sh where gdb.sh contained the following:
gdb -batch-silent \
-ex 'set logging overwrite on' \
-ex "set logging file /tmp/gdb.log" \
-ex 'set logging on' \
-ex 'handle SIG33 pass nostop noprint' \
-ex 'set pagination 0' \
-ex 'run' \
-ex 'backtrace full' \
-ex 'info registers' \
-ex 'thread apply all backtrace' \
-ex 'quit' \
-p `pidof X` < /dev/null
< /dev/null
Xorg never seems happy after the above finishes and always wedged itself
after the script ran)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ccea30 (LWP 2972)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGUSR1, User defined signal 1.
[Switching to Thread 0xb7ccea30 (LWP 2972)]
0xb7fe8424 in __kernel_vsyscall ()
#0 0xb7fe8424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7e3984d in select () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#2 0x081b22e5 in WaitForSomething ()
No symbol table info available.
#3 0x0808d69d in Dispatch ()
No symbol table info available.
#4 0x0807471b in main ()
No symbol table info available.
eax 0xfffffdfe -514
ecx 0x820a240 136356416
edx 0x0 0
ebx 0x100 256
esp 0xbf902cc0 0xbf902cc0
ebp 0xbf902f58 0xbf902f58
esi 0x0 0
edi 0xbf902f40 -1081069760
eip 0xb7fe8424 0xb7fe8424 <__kernel_vsyscall+16>
eflags 0x3246 [ PF ZF IF #12 #13 ]
cs 0x73 115
ss 0x7b 123
ds 0x7b 123
es 0x7b 123
fs 0x0 0
gs 0x33 51
Thread 1 (Thread 0xb7ccea30 (LWP 2972)):
#0 0xb7fe8424 in __kernel_vsyscall ()
#1 0xb7e3984d in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x081b22e5 in WaitForSomething ()
#3 0x0808d69d in Dispatch ()
#4 0x0807471b in main ()
The program is running. Exit anyway? (y or n) [answered Y; input not from terminal]
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2009-02-24 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 15:38 [REGRESSION] i915 VT switch with AIGLX causes X lock up Sitsofe Wheeler
2009-02-23 22:32 ` Sitsofe Wheeler
2009-02-24 16:44 ` Jesse Barnes
2009-02-24 22:59 ` Sitsofe Wheeler [this message]
2009-03-09 23:56 ` [REGRESSION,BISECTED] " Sitsofe Wheeler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090224225930.GA3745@silver.sucs.org \
--to=sitsofe@yahoo.com \
--cc=dri-devel@lists.sf.net \
--cc=eric@anholt.net \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox