Keyboard keeps freezing
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
Every once in a while the keyboard freezes for a bit, but the mouse still works fine.
The keyboard and mouse are connected to the computer via a single wireless dongle.
The problem is fixed by a reboot.
I confirmed that the CPU and RAM were not being fully utilized.
What else might be causing it?
UPDATE:
It seems like it might have something to do with my GPU.
I found this in /var/syslog right after an incident:
Dec 25 00:28:33 debian kernel: [ 920.350428] NVRM: GPU at PCI:0000:01:00: GPU-60df4653-7e30-ba1b-17c9-f7a69fcdb14a
Dec 25 00:28:33 debian kernel: [ 920.350430] NVRM: GPU Board Serial Number:
Dec 25 00:28:33 debian kernel: [ 920.350432] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000034, engmask 00000105, intr 10000000
debian xfce
asked Dec 25 '17 at 3:20
Person93
1268
 |Â
show 3 more comments
up vote
0
down vote
favorite
Every once in a while the keyboard freezes for a bit, but the mouse still works fine.
The keyboard and mouse are connected to the computer via a single wireless dongle.
The problem is fixed by a reboot.
I confirmed that the CPU and RAM were not being fully utilized.
What else might be causing it?
UPDATE:
It seems like it might have something to do with my GPU.
I found this in /var/syslog right after an incident:
Dec 25 00:28:33 debian kernel: [ 920.350428] NVRM: GPU at PCI:0000:01:00: GPU-60df4653-7e30-ba1b-17c9-f7a69fcdb14a
Dec 25 00:28:33 debian kernel: [ 920.350430] NVRM: GPU Board Serial Number:
Dec 25 00:28:33 debian kernel: [ 920.350432] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000034, engmask 00000105, intr 10000000
debian xfce
asked Dec 25 '17 at 3:20
Person93
1268
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
Start withdmesgoutput and/var/log/syslog, maybe/var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them withtail -f(anddmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.
– multithr3at3d
Dec 25 '17 at 3:45
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (evtest, see if you get events even if you don't get keypresses). After thatusbmon, orxev(or whatever Wayland can use).
– dirkt
Dec 25 '17 at 8:40
 |Â
show 3 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Every once in a while the keyboard freezes for a bit, but the mouse still works fine.
The keyboard and mouse are connected to the computer via a single wireless dongle.
The problem is fixed by a reboot.
I confirmed that the CPU and RAM were not being fully utilized.
What else might be causing it?
UPDATE:
It seems like it might have something to do with my GPU.
I found this in /var/syslog right after an incident:
Dec 25 00:28:33 debian kernel: [ 920.350428] NVRM: GPU at PCI:0000:01:00: GPU-60df4653-7e30-ba1b-17c9-f7a69fcdb14a
Dec 25 00:28:33 debian kernel: [ 920.350430] NVRM: GPU Board Serial Number:
Dec 25 00:28:33 debian kernel: [ 920.350432] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000034, engmask 00000105, intr 10000000
debian xfce
asked Dec 25 '17 at 3:20
Person93
1268
Every once in a while the keyboard freezes for a bit, but the mouse still works fine.
The keyboard and mouse are connected to the computer via a single wireless dongle.
The problem is fixed by a reboot.
I confirmed that the CPU and RAM were not being fully utilized.
What else might be causing it?
UPDATE:
It seems like it might have something to do with my GPU.
I found this in /var/syslog right after an incident:
Dec 25 00:28:33 debian kernel: [ 920.350428] NVRM: GPU at PCI:0000:01:00: GPU-60df4653-7e30-ba1b-17c9-f7a69fcdb14a
Dec 25 00:28:33 debian kernel: [ 920.350430] NVRM: GPU Board Serial Number:
Dec 25 00:28:33 debian kernel: [ 920.350432] NVRM: Xid (PCI:0000:01:00): 31, Ch 00000034, engmask 00000105, intr 10000000
debian xfce
asked Dec 25 '17 at 3:20
Person93
1268
edited Dec 25 '17 at 5:32
asked Dec 25 '17 at 3:20
Person93
1268
asked Dec 25 '17 at 3:20
Person93
1268
asked Dec 25 '17 at 3:20
Person93
1268
1268
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
Start withdmesgoutput and/var/log/syslog, maybe/var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them withtail -f(anddmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.
– multithr3at3d
Dec 25 '17 at 3:45
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (evtest, see if you get events even if you don't get keypresses). After thatusbmon, orxev(or whatever Wayland can use).
– dirkt
Dec 25 '17 at 8:40
 |Â
show 3 more comments
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
Start withdmesgoutput and/var/log/syslog, maybe/var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them withtail -f(anddmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.
– multithr3at3d
Dec 25 '17 at 3:45
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (evtest, see if you get events even if you don't get keypresses). After thatusbmon, orxev(or whatever Wayland can use).
– dirkt
Dec 25 '17 at 8:40
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
Start with
dmesg output and /var/log/syslog, maybe /var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them with tail -f (and dmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.– multithr3at3d
Dec 25 '17 at 3:45
Start with
dmesg output and /var/log/syslog, maybe /var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them with tail -f (and dmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.– multithr3at3d
Dec 25 '17 at 3:45
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (
evtest, see if you get events even if you don't get keypresses). After that usbmon, or xev (or whatever Wayland can use).– dirkt
Dec 25 '17 at 8:40
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (
evtest, see if you get events even if you don't get keypresses). After that usbmon, or xev (or whatever Wayland can use).– dirkt
Dec 25 '17 at 8:40
 |Â
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f412885%2fkeyboard-keeps-freezing%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
What distribution are you running, destkop environment/window manger, kernel, etc? Are there any relevant log snippits?
– multithr3at3d
Dec 25 '17 at 3:26
i'm using buster. Kernel 4.13.0-1-amd64. I don't even know what logs to check!
– Person93
Dec 25 '17 at 3:41
Start with
dmesgoutput and/var/log/syslog, maybe/var/log/Xorg.0.log, and try to capture them around the time of the incident. You could open a couple terminals and follow them withtail -f(anddmesg -w). Also keep in mind that issues like this may be more likely since you are on a testing release of Debian.– multithr3at3d
Dec 25 '17 at 3:45
I added a few lines of the syslog to the OP.
– Person93
Dec 25 '17 at 5:32
It's unlikely (but not impossible) that the delay is caused by the GPU in some way. Assuming it's an USB dongle, the event path is: USB -> dongle driver -> kernel input layer -> X/Wayland input layer. Test systematically where the problem is: First check the kernel input layer (
evtest, see if you get events even if you don't get keypresses). After thatusbmon, orxev(or whatever Wayland can use).– dirkt
Dec 25 '17 at 8:40