reassign 607242 linux-2.6 kthxbye Reassigning to the kernel as this doesn't look like an X bug in any case.
On Thu, Dec 23, 2010 at 23:34:48 +0530, shirish शिरीष wrote: > In-line :- > > On Thu, Dec 23, 2010 at 23:05, Jim Hill <gjth...@gmail.com> wrote: > > I'm getting this too. Here's the tail of my syslog. The parity messages > > make me kinda suspect failing hardware. > > <snipped> > Thank you gjthill for also giving me one place to look. I also took a > look there and found this out. > > Dec 23 19:07:48 deb-home kernel: [ 1354.471364] psmouse.c: Wheel Mouse > at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. > > Dec 23 20:11:26 deb-home kernel: [ 5172.509267] psmouse.c: Wheel Mouse > at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. > > Dec 23 21:51:15 deb-home kernel: [11161.670849] psmouse.c: Wheel Mouse > at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. > > Dec 23 22:15:34 deb-home kernel: [12620.856362] psmouse.c: Wheel Mouse > at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. > > Dec 23 22:42:55 deb-home kernel: [14261.187782] psmouse.c: Wheel Mouse > at isa0060/serio1/input0 lost synchronization, throwing 3 bytes away. > > Although there are no bad parity statements in my syslog. If needed > can attach the syslog as well. > On Thu, Dec 23, 2010 at 10:36:20 -0800, Jim Hill wrote: > Okay, digging it seems this is a common hardware problem that Windows > solves by ignoring: https://bugzilla.kernel.org/show_bug.cgi?id=6105 > > Linux does too since 2.6.34: > > $ git describe 6b9d363c49d22395d0cf8729c5963f83cfbb6d69 > v2.6.34-rc1-31-g6b9d363 > Not sure this is what shirish is seeing since he doesn't get the parity error message, but it's either a kernel bug or hardware fail as far as I can tell. Thanks for digging this up though. Cheers, Julien
signature.asc
Description: Digital signature
