Keyboard keeps freezing

Multi tool use
Multi tool use

The name of the pictureThe name of the pictureThe name of the pictureClash 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




share|improve this question






















  • 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 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










  • 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














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




share|improve this question






















  • 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 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










  • 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












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




share|improve this question














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





share|improve this question













share|improve this question




share|improve this question








edited Dec 25 '17 at 5:32

























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 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










  • 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
















  • 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 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










  • 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















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















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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






















active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














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
































































amK,ce5dE7b5lZtJFuUvG,3kxrl,ev3u9mz79hz7BRh0,izW4OQL,Qf24,Gte BLb,h
-
JTX1SgjPw3 zsxlK0 AlJWo 4MKAxo,p21XS6BpjY9bU,P19,9QY,3849e 1Gk8PycMtjdPc n,fjETWppRmUuhHK3 yssQp25

Popular posts from this blog

How to check contact read email or not when send email to Individual?

Image
Clash Royale CLAN TAG #URR8PPP up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this question asked Sep 26 at 0:12 ToanLuong 49 9 add a comment  |  up vote 1 down vote favorite I'm using WordPress 4.9.8, CiviCRM to 5.5.1, I usually send email to contact by Search> Find contacts View contact details Action> Send email Send email ok, Contact received mail ok like picture But status only Email sent though contact read email or not. So, can CiviCRM can change status to Email read when contact read email? wordpress email share | improve this questi...
Read more

How many registers does an x86_64 CPU actually have?

Image
Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite I am currently learning reverse engineering and am studying the flags register. I had in my mind that rflags was just another name for one of the 16 general purpose registers, for example rax or rbx . But it looks like rflags is actually an additional register. So that makes 17 registers in total... how many more could there be? I have spent at least an hour on this and found numerous different answers. The best answer so far is this, which says that there are 40 registers in total. 16 General Purpose Registers 2 Status Registers 6 Code Segment Registers 16 SSE Registers 8 FPU/MMX Registers But if I add that up, I get 48. Could anybody provide an official answer on how many registers an x86_64 CPU has (e.g. an Intel i7). Additionally, I have seen references to 'hardware' and 'architectural' registers. What are those registers and how many are there? register x86-64 share | improve this...
Read more

Displaying single band from multi-band raster using QGIS

Image
Clash Royale CLAN TAG #URR8PPP 1 How can I extract a single band from multi-band raster in QGIS? I have an remote sensed image which has 6 bands (including NDVI band), I want to display each band separately, but have no idea how to do. I have seen some questions similar here but none worked for me. The original image (has 6 bands) is: I want to display the band 6 which should be like this: But I tried gdal_translate, and couldn't get the correct result. What I have got is: qgis raster multi-band share | improve this question edited Mar 5 at 0:53 Summer asked Mar 4 at 6:42 Summer Summer 23 6 Is this any help gis.stackexchange.com/questions/220658/… ? if not gis.stackexchange.com/questions/62133/… might help. – Michael Stimson Mar 4 at 6:46 Thanks for answering but when I used gdal_translate, qgis showed that 'Error 4: Kayena.tif: No such file or directory". Would you know how to fi...
Read more