mouse and keyboard stop a while when some info requested to ACPI system and 'psmouse.c: TouchPad at isa0060/serio4/input0 lost sync at' in dmesg
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Invalid
|
Undecided
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I have ad Acer Aspire 1362LM. When the system try access the ACPI subsystem (e.g. battery status), the mouse stop working for some seconds, the keyboard too, and sometimes the sound and disk too. (just for some seconds..)
I patched the DSDT with a correct one, but nothing changed.
With dmesg I found:
[17180568.352000] psmouse.c: TouchPad at isa0060/
[17180568.356000] psmouse.c: TouchPad at isa0060/
[17180568.364000] psmouse.c: TouchPad at isa0060/
[17180598.280000] rtc: lost some interrupts at 2048Hz.
[17180628.308000] rtc: lost some interrupts at 2048Hz.
[17180628.352000] psmouse.c: TouchPad at isa0060/
[17180628.356000] psmouse.c: TouchPad at isa0060/
[17180628.356000] psmouse.c: TouchPad at isa0060/
[17180628.356000] psmouse.c: TouchPad at isa0060/
[17180628.360000] psmouse.c: TouchPad at isa0060/
[17180628.368000] psmouse.c: TouchPad at isa0060/
[17180658.284000] rtc: lost some interrupts at 2048Hz.
[17180688.304000] rtc: lost some interrupts at 2048Hz.
[17180688.348000] psmouse.c: TouchPad at isa0060/
[17180688.352000] psmouse.c: TouchPad at isa0060/
[17180688.352000] psmouse.c: TouchPad at isa0060/
[17180688.352000] psmouse.c: TouchPad at isa0060/
[17180688.356000] psmouse.c: TouchPad at isa0060/
[17180688.364000] psmouse.c: TouchPad at isa0060/
[17180748.288000] rtc: lost some interrupts at 2048Hz.
[17180778.284000] rtc: lost some interrupts at 2048Hz.
[17180808.284000] rtc: lost some interrupts at 2048Hz.
[17180838.284000] rtc: lost some interrupts at 2048Hz.
[17180868.288000] rtc: lost some interrupts at 2048Hz.
I think is a Linux kernel bug...
I've find a solution.
I think is a Linux kernel problem with mouse's multiplexer.
I've added "i8042.nomux" to the booting kernel and the problem goes away.