Re: Mouse lags after display wakes from sleep

[Kynn Jones <kynnjo@gmail.com>]

On Sun, Mar 8, 2015 at 8:55 PM, Kynn Jones <kynnjo@gmail.com> wrote:
> My mouse (Logitech TrackMan Wheel) works fine right after the system
> is booted, but if the display (Dell U2713H) goes to sleep, then
> afterwards there's a pronounced lag in the mouse's response, which
> makes it very difficult to position the cursor.  This problem persists
> until I reboot the system.
>
> (Also, the keyboard seems a bit slow as well, but this effect is a lot
> subtler, so I'm not 100% sure it is real.)
>
> I don't see this problem at all if I boot into Windows 7 instead of
> Debian (same computer, monitor, and mouse).  This rules out some
> general defect in the hardware.
>
> I observe the same problem whether I choose Gnome, Xfce4, or OpenBox
> when I log in after rebooting.
>
> How can I troubleshoot this problem further?


FWIW, here are the new messages logged to `/etc/var/messages` between
the time I put the display to sleep (`xset dpms force off`) and the time it
came back on:

    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856436] Pid: 0, comm:
swapper/0 Not tainted 3.2.0-4-amd64 #1 Debian 3.2.65-1+deb7u2
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856441] Call Trace:
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856444]  <IRQ>
[<ffffffff81092ddd>] ? __report_bad_irq+0x2c/0xb5
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856466]
[<ffffffff810931e2>] ? note_interrupt+0x1b8/0x23a
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856474]
[<ffffffff81091554>] ? handle_irq_event_percpu+0x15f/0x17d
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856481]
[<ffffffff810915a6>] ? handle_irq_event+0x34/0x52
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856492]
[<ffffffff8106c305>] ? arch_local_irq_save+0x11/0x17
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856500]
[<ffffffff81093959>] ? handle_fasteoi_irq+0x7c/0xaf
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856510]
[<ffffffff8100fa51>] ? handle_irq+0x1d/0x21
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856518]
[<ffffffff8100f62a>] ? do_IRQ+0x42/0x98
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856528]
[<ffffffff813511ae>] ? common_interrupt+0x6e/0x6e
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856532]  <EOI>
[<ffffffff81024404>] ? lapic_next_event+0xe/0x13
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856566]
[<ffffffffa01b835b>] ? arch_local_irq_enable+0x7/0x8 [processor]
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856578]
[<ffffffffa01b90b3>] ? acpi_idle_enter_c1+0x8d/0xb3 [processor]
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856589]
[<ffffffff8127180d>] ? cpuidle_idle_call+0xec/0x179
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856597]
[<ffffffff8100d242>] ? cpu_idle+0xa5/0xf2
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856608]
[<ffffffff816aab3b>] ? start_kernel+0x3bd/0x3c8
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856617]
[<ffffffff816aa140>] ? early_idt_handlers+0x140/0x140
    Mar  8 21:06:20 xxxxxx kernel: [ 2695.856625]
[<ffffffff816aa3c4>] ? x86_64_start_kernel+0x104/0x111

Does any of this look relevant to the problem I described in my
previous message?

A similar analysis of `/etc/var/Xorg.0.log` did not turn up any
messages.  (I.e. the log file was the same right before and right
after the sleep.)

kj