ps2 mouse erratic - parity errors - lost synchronization errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
Medium
|
|||
Ubuntu |
Invalid
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned | ||
linux-source-2.6.20 (Ubuntu) |
Invalid
|
High
|
Unassigned | ||
Bug Description
Binary package hint: linux-source-2.6.20
uname:
2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux
lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333]
00:01.0 PCI bridge: VIA Technologies, Inc. VT8366/A/7 [Apollo KT266/A/333 AGP]
00:08.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:08.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 50)
00:08.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51)
00:0a.0 Communication controller: Intel Corporation 536EP Data Fax Modem
00:0c.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/
00:11.0 ISA bridge: VIA Technologies, Inc. VT8233A ISA Bridge
00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/
00:11.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23)
00:11.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 23)
00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 40)
01:00.0 VGA compatible controller: nVidia Corporation NV17 [GeForce4 MX 440] (rev a3)
dmesg extract:
[13992.656000] psmouse.c: bad data from KBC - bad parity
[13994.192000] psmouse.c: Mouse at isa0060/
[14007.616000] psmouse.c: bad data from KBC - timeout
[14009.432000] psmouse.c: Mouse at isa0060/
[14010.720000] psmouse.c: bad data from KBC - bad parity
[14013.344000] psmouse.c: Mouse at isa0060/
[14048.616000] psmouse.c: bad data from KBC - timeout
[14048.624000] psmouse.c: bad data from KBC - bad parity
[14053.784000] psmouse.c: Mouse at isa0060/
[14055.280000] psmouse.c: bad data from KBC - bad parity
[14055.628000] psmouse.c: bad data from KBC - timeout
[14055.680000] psmouse.c: bad data from KBC - timeout
[14057.476000] psmouse.c: Mouse at isa0060/
[14057.480000] psmouse.c: resync failed, issuing reconnect request
[14057.632000] input: GenPS/2 Genius Mouse as /class/input/input7
[14057.776000] input: GenPS/2 Genius Mouse as /class/input/input8
[14311.032000] psmouse.c: bad data from KBC - bad parity
[14312.612000] psmouse.c: Mouse at isa0060/
[14394.256000] psmouse.c: bad data from KBC - bad parity
[14395.584000] psmouse.c: Mouse at isa0060/
[14768.280000] psmouse.c: bad data from KBC - timeout
[14768.284000] psmouse.c: bad data from KBC - timeout
[14929.396000] psmouse.c: bad data from KBC - bad parity
[14931.560000] psmouse.c: Mouse at isa0060/
[15073.300000] psmouse.c: bad data from KBC - bad parity
[15076.748000] psmouse.c: Mouse at isa0060/
[15177.576000] psmouse.c: bad data from KBC - bad parity
[15179.288000] psmouse.c: Mouse at isa0060/
This started in Dapper, and continues in Feisty, but not in Windows XP.
The mouse moves erratically around the screen, any icons or links that it passes over, it opens. I've seen many references to this error message, but no solutions. I've tried USB mice, but they give other errors, which are under investigation already.
Changed in linux-source-2.6.20: | |
assignee: | nobody → ubuntu-kernel-team |
Changed in linux-source-2.6.20: | |
status: | Incomplete → Triaged |
Changed in linux: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | Confirmed → Triaged |
Changed in linux: | |
status: | Unknown → In Progress |
tags: | added: patch |
tags: |
added: patch-forwarded-upstream removed: patch |
tags: | added: maverick |
Changed in linux: | |
status: | In Progress → Fix Released |
Changed in linux: | |
importance: | Unknown → Medium |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http:// wiki.ubuntu. com/KernelTeamB ugPolicies. Thanks in advance!