IRQ MSFT?
- Inicie sesión o regístrese para enviar comentarios
I have a process on my computer that is called "irq/153-MSFT0001:01".
https://docs.kernel.org/core-api/irq/concepts.html
So if there is an IRQ is that a bad thing? Like the hardware trying to communicate that something is wrong?
The below is from dmesg
[ 1.033905] input: MSFT0001:01 06CB:CE2D Mouse as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-MSFT0001:01/0018:06CB:CE2D.0001/input/input3
[ 1.034752] input: MSFT0001:01 06CB:CE2D Touchpad as /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-MSFT0001:01/0018:06CB:CE2D.0001/input/input4
[ 1.034997] hid-generic 0018:06CB:CE2D.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:01 06CB:CE2D] on i2c-MSFT0001:01
In short, your touchpad/mouse are operating properly.
https://en.wikipedia.org/wiki/Interrupt_request
"In a computer, an interrupt request (or IRQ) is a hardware signal ... to handle events such as receiving data from ... mouse movements."
Imagine your computer is a busy chef.
Instead of the chef stopping work every five seconds to walk out and ask if you're ready to order, you have a bell on your table. You ring it only when you need something.
That bell is an IRQ (Interrupt Request).
The process irq/153-MSFT0001:01 is literally just the specific bell for your touchpad/mouse. Every time you use it, the touchpad/mouse rings bell #153 to tell the computer, "Hey, the human did something!" The kernel stops to get the message about what you did and then does the appropriate thing in response which might be just moving the arrow on your screen or whatever.
It's not an alarm siren; it's just the normal bell that makes your touchpad/mouse work.
