Syniurge
commented
4 years ago Sorry for not noticing your issue earlier, it looks interesting.
It looks like plugging some USB device triggers the interrupt line for the MP2 I2C controller, but since the MP2 interrupt handler in the driver doesn't see any new info from the MP2 it ignores the interrupt (passes it to other interrupt handlers if there are any, but there's only one in your case) which triggers this error.
I have no clue why plugging something in a USB port would have anything to do with the I2C controller interrupt. Could be a hardware issue if it's random. I tried to find similar cases on Google but couldn't find any, and you're the first person to report this to me.
The workaround below would be to always tell the kernel that the IRQ was handled so that the IRQ doesn't get disabled, but that's assuming that the interrupt line isn't shared with other devices. In your case it isn't, but it might cause problems for other laptops.
static irqreturn_t amd_mp2_irq_isr(int irq, void *dev)
{
// (...)
for (bus_id = 0; bus_id < 2; bus_id++) {
// (...)
}
if (ret != IRQ_HANDLED) {
// (...)
}
ret = IRQ_HANDLED; // <===== WORKAROUND
return ret;
}Or maybe the MP2 is meant to always have its own interrupt line and the assumption holds (which may be why the problem doesn't occur on Windows). I'll ask AMD people..
Hi! I'm using KDE neon, based on Ubuntu 18.04, with the Xanmod kernel (currently kernel 5.5, but I've tried everything since kernel 5.0). Ever since I have started using this computer one years ago I have been experiencing the touchpad suddenly and apparently randomly stopping to work. I have recently been able to pinpoint the issue in some kind of incompatibility with USB - whenever I plug something in a USB port the touchpad may stop working. Whenever that happens I am met with these messages in dmesg:
After this happens the touchpad will just click randomly whenever I touch it, but it won't move the cursor. Does anyone have any idea what's going on? Thanks!