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

Bug#455570: xserver-xorg: "tossed event which came in late" with kernel 2.6.23-1, keyboard doesn't react



Am Fri, 14 Dec 2007 18:40:47 +0100
schrieb Michel Dänzer <daenzer@debian.org>:

> That's from the time the X server starts or from the time you log in?
> If the latter, what kind of session (desktop environment, window
> manager etc.) are you using?

I am using Gnome. But i have this issue with GDM too. Once i click
"Actions" Xorg everything except mouse is frozen.

> 
> > Keyboard is dead (even switching to VTs is not possible). Mouse
> > works, but clicking buttons doesn't have an effect.
> 
> At that point, does the X server hog the CPU? Can you attach gdb to
> the X server process and get a backtrace?

Ok. I hope i did that right:

Started the machine as usual, ssh from another machine to it, ran gdb,
then attach <PID of Xorg>.

I'm not very familiar with gdb... But as far as I can see the execution
of Xorg stops as soon as I attach gdb to it. If i run "backtrace full"
at the gdm prompt, the output is:
-----------------------------------------
(gdb) backtrace full
#0  0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1  0xb7de1fed in select () from /lib/i686/cmov/libc.so.6
No symbol table info available.
#2  0x081add00 in WaitForSomething (pClientsReady=0xbfe69f00)
at ../../os/WaitFor.c:235 client_priority = <value optimized out>
        client_index = <value optimized out>
        highest_priority = <value optimized out>
        i = <value optimized out>
        waittime = {tv_sec = 50, tv_usec = 996000}
        wt = (struct timeval *) 0xbfe69ec0
        timeout = <value optimized out>
        clientsReadable = {fds_bits = {0 <repeats 32 times>}}
        clientsWritable = {fds_bits = {136434224, 1, -1075405320,
136142732, -1075405320, 1, -1075405196, -1210180984, -1075405196, 12,
78, 136142732, 1, 32, -1075405288, 136020926, 12, -1075405196, 1,
135996684, 138756248, 136142732, -1075405256, 136016079, 138480224,
-1075405196, 1, 136142732, 138888368, 138499112, -1075405160,
135995446}} curclient = <value optimized out> selecterr = 4 nready =
<value optimized out> devicesReadable = {fds_bits = {138499112, 78,
136434224, 136142732, 136594944, 136406552, -1075405432, 134812170,
136319752, 0, -1075405392, 0, 138499112, 4194619, 138773648, 136142732,
-1075405372, 78, -1075405416, 134811824, 136319752, -1075405392,
-1075405352, 135582719, 136319752, -1075405392, 138499112, 136142732,
138499112, 78, -1073741823, 1}} now = 569772 someReady = 0 #3
0x0808cf82 in Dispatch () at ../../dix/dispatch.c:425 result = <value
optimized out> client = (ClientPtr) 0x8415428
        nready = -1
        start_tick = 4280
#4  0x0807470b in main (argc=9, argv=0xbfe6a424, envp=0x0)
at ../../dix/main.c:452 pScreen = <value optimized out>
        i = 1
        error = 136142732
        xauthfile = <value optimized out>
        alwaysCheckForInput = {0, 1}
--------------------------------------
But i fear this is just the ordinary program loop... When i type
"cont", i don't come back to the gdb prompt. Probably because no error
of any sort occours, probably Xorg is just caught in a endless loop or
something like that. CPU is hogged (99,7% usage of Xorg). How do i
track this problem with gdb? I already found
http://xorg.freedesktop.org/wiki/Development/Documentation/ServerDebugging,
but that was no big help... They are also waiting for a crash to do a
backtrace in that page...

But i observed also other error messages in Xorg.0.log:

tossed event which came in late
mieqEnequeue: out-of-order valuator event; dropping.
tossed event which came in late
mieqEnequeue: out-of-order valuator event; dropping.

The original errors were only tossed event...

> > I made a diff between the Xorg.0.log (.22 kernel) and Xorg.0.log.old
> > (.23 kernel) below.
> 
> Thanks. In the future, please use diff -u for better readability.

Didn't know this option until now.

> Did you capture both log files at similar times, e.g. both after
> logging in?

The first was captured with the "faulty" kernel. I logged into Gnome,
waited until it froze, then shut the machine off. Then i rebooted with
2.6.22 and logged in again, then copied the logfiles away.

Oh. If it's important: The machine is an Acer 4002 WLMi Notebook.

Thanks for caring for my problem!

Andreas


-- 
Andreas Juch                                ASCII Ribbon Campaign  /"\
                                               against HTML email  \ /
GPG-Key ID:  21E6864A                                               X 
Fingerprint: D4D2 0F3F 138A F7A4 6DED  76EC F9EA 29BC 21E6 864A    / \

Attachment: signature.asc
Description: PGP signature


Reply to: