On 2013-08-27 19:41, Andreas Mohr wrote: >> What could this be? >> Is it really a software issue? >> If so: how could I help fix this? > > Perhaps watching the output of some input event tools could help > gather some clues to eventually get it nailed down?
Sure. First my input: When I run this small script to fix the irq issue, I see that also the stream of ^@^@^@ stops (or at least appears to do so), when those ^@^@^@ were active: service motion stop rmmod pwc echo 0000:00:13.0 >/sys/bus/pci/drivers/ohci_hcd/unbind echo 0000:00:13.0 >/sys/bus/pci/drivers/ohci_hcd/bind modprobe pwc service motion start > Some candidates: > > evtest - utility to monitor Linux input device events > input-utils - utilities for the input layer of the Linux kernel > xinput - Runtime configuration and test of XInput devices I'll look into these! > And what do /proc/interrupts counts say? Does PS/2 (i8042) generate events? Currently it does. But I must see what happens when all is quiet, and the problem reappears, right? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
