mouse still losing sync and thus jumping around
Quoted 1 line · On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
On Wed, 23 Feb 2005 17:29:49 +0100, Nils Kalchhauser wrote:
[...]
Quoted 8 lines
Quoted 2 lines
it seems to me like it is connected to disk activity... is that possible?
Yes, It usually happens either under high load, when mouse interrupts are significantly delayed. Or sometimes it happen when applications poll battey status and on some boxes it takes pretty long time. And because it is usually the same chip that serves keyboard/mouse it again delays mouse interrupts.
My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
model: 1, fw: 5.8, id: 0x9248b1, caps: 0x904713/0x4000
Kernels 2.6.11.11 and 2.6.12-rc6
Synaptics driver 0.14.2
The "lost sync at byte" and "driver resynched" began flooding the logs when I enabled Sensors --> Temperatures --> thermal_zone [THRC/THRS] in the system monitor gkrellm. I haven't tried battery monitoring.
There are only occasional mouse pointer jumps, but the logfiles grow very quickly. I tried reducing the gkrellm updates from 10 times a second to 2, but it only had a marginal effect. It seems a bit silly that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask' correctly.
I thought about just erasing the warning messages from the kernel source (don't want to disable warn in syslog completely), but when I found the gkrellm culprit I turned off the monitoring instead, reluctantly.
My system has no taxing desktop, just a window manager.
Mvh
Mats Johannesson
--
Quoted 23 lines · Voluspa
Quoted 1 line · On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
On Wed, 23 Feb 2005 17:29:49 +0100, Nils Kalchhauser wrote:
[...]
Quoted 8 lines
Quoted 2 lines
it seems to me like it is connected to disk activity... is that possible?
Yes, It usually happens either under high load, when mouse interrupts are significantly delayed. Or sometimes it happen when applications poll battey status and on some boxes it takes pretty long time. And because it is usually the same chip that serves keyboard/mouse it again delays mouse interrupts.
My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
model: 1, fw: 5.8, id:0x9248b1, caps: 0x904713/0x4000Kernels 2.6.11.11 and 2.6.12-rc6
Synaptics driver 0.14.2The "lost sync at byte" and "driver resynched" began flooding the logs when I enabled Sensors --> Temperatures -->
thermal_zone[THRC/THRS] in the system monitor gkrellm. I haven't tried battery monitoring.
Quoted 6 lines
There are only occasional mouse pointer jumps, but the logfiles grow very quickly. I tried reducing the gkrellm updates from 10 times a second to 2, but it only had a marginal effect. It seems a bit silly that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask' correctly.
Try setting frequency to once a minute, that should help.
Signature · 1 line
Dmitry
Quoted 1 line · On Mon, 13 Jun 2005 16:47:53 -0500 Dmitry Torokhov wrote:
Try setting frequency to once a minute, that should help.
I don't think I'd get much work done if the mouse was updated once a minute only...
Gkrellm can go as low as 1 update per second for its graphical output. Don't know if the "below the hood" polling is reduced to the same freq.
Mvh
Mats Johannesson
--
Quoted 28 lines · On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
Quoted 1 line · Nils Kalchhauser
[...]
Quoted 8 lines
Quoted 2 lines
it seems to me like it is connected to disk activity... is that possible?
Yes, It usually happens either under high load, when mouse interrupts are significantly delayed. Or sometimes it happen when applications poll battey status and on some boxes it takes pretty long time. And because it is usually the same chip that serves keyboard/mouse it again delays mouse interrupts.
My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
model: 1, fw: 5.8, id:0x9248b1, caps: 0x904713/0x4000Kernels 2.6.11.11 and 2.6.12-rc6
Synaptics driver 0.14.2The "lost sync at byte" and "driver resynched" began flooding the logs when I enabled Sensors --> Temperatures -->
thermal_zone[THRC/THRS] in the system monitor gkrellm. I haven't tried battery monitoring.There are only occasional mouse pointer jumps, but the logfiles grow very quickly. I tried reducing the gkrellm updates from 10 times a second to 2, but it only had a marginal effect. It seems a bit silly that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask' correctly.
Quoted 7 lines
I thought about just erasing the warning messages from the kernel source (don't want to disable warn in syslog completely), but when I found the gkrellm culprit I turned off the monitoring instead, reluctantly.
My system has no taxing desktop, just a window manager.
I had this problem with the ps2 mouse on my desktop even under very light load. This problem went away the very instant I started using a USB mouse. So, I don't buy the delayed interrupts explanation.
My 2 cents
-G
Quoted 33 lines · bhaskara
Quoted 33 lines · On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
Quoted 1 line · Nils Kalchhauser
[...]
Quoted 8 lines
Quoted 2 lines
it seems to me like it is connected to disk activity... is that possible?
Yes, It usually happens either under high load, when mouse interrupts are significantly delayed. Or sometimes it happen when applications poll battey status and on some boxes it takes pretty long time. And because it is usually the same chip that serves keyboard/mouse it again delays mouse interrupts.
My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
model: 1, fw: 5.8, id:0x9248b1, caps: 0x904713/0x4000Kernels 2.6.11.11 and 2.6.12-rc6
Synaptics driver 0.14.2The "lost sync at byte" and "driver resynched" began flooding the logs when I enabled Sensors --> Temperatures -->
thermal_zone[THRC/THRS] in the system monitor gkrellm. I haven't tried battery monitoring.There are only occasional mouse pointer jumps, but the logfiles grow very quickly. I tried reducing the gkrellm updates from 10 times a second to 2, but it only had a marginal effect. It seems a bit silly that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask' correctly.
I thought about just erasing the warning messages from the kernel source (don't want to disable warn in syslog completely), but when I found the gkrellm culprit I turned off the monitoring instead, reluctantly.
Quoted 7 lines
Quoted 2 lines
My system has no taxing desktop, just a window manager.
I had this problem with the ps2 mouse on my desktop even under very light load. This problem went away the very instant I started using a USB mouse. So, I don't buy the delayed interrupts explanation.
You do not have to buy anything, you just need to read the code. pmouse driver emits this warning if delay between 2 bytes in a middle of a packet exceeds 0.5 sec. USB works slightly differently.
Signature · 1 line
Dmitry
Quoted 37 lines · bhaskara
Quoted 36 lines
Quoted 35 lines · On 2005-02-23 16:53:04 Dmitry Torokhov wrote:
Quoted 1 line · Nils Kalchhauser
[...]
Quoted 8 lines
Quoted 2 lines
it seems to me like it is connected to disk activity... is that possible?
Yes, It usually happens either under high load, when mouse interrupts are significantly delayed. Or sometimes it happen when applications poll battey status and on some boxes it takes pretty long time. And because it is usually the same chip that serves keyboard/mouse it again delays mouse interrupts.
My notebook is an Acer Aspire 1520 (1524) with a Synaptics Touchpad,
model: 1, fw: 5.8, id:0x9248b1, caps: 0x904713/0x4000Kernels 2.6.11.11 and 2.6.12-rc6
Synaptics driver 0.14.2The "lost sync at byte" and "driver resynched" began flooding the logs when I enabled Sensors --> Temperatures -->
thermal_zone[THRC/THRS] in the system monitor gkrellm. I haven't tried battery monitoring.There are only occasional mouse pointer jumps, but the logfiles grow very quickly. I tried reducing the gkrellm updates from 10 times a second to 2, but it only had a marginal effect. It seems a bit silly that this powerful notebook (AMD64 Athlon 3400+) can't 'multitask' correctly.
I thought about just erasing the warning messages from the kernel source (don't want to disable warn in syslog completely), but when I found the gkrellm culprit I turned off the monitoring instead, reluctantly.
My system has no taxing desktop, just a window manager.
Quoted 8 lines
Quoted 4 lines
I had this problem with the ps2 mouse on my desktop even under very light load. This problem went away the very instant I started using a USB mouse. So, I don't buy the delayed interrupts explanation.
You do not have to buy anything, you just need to read the code. pmouse driver emits this warning if delay between 2 bytes in a middle of a packet exceeds 0.5 sec. USB works slightly differently.
No offense ..... but, I did some googling and figured out where the mesg was being printed from. So I ripped out all the unnecessary stuff from the kernel and also stopped all the unnecessary services, but still got this behavior (with XFCE and KDE). By the way , my desktop
started exhibiting this behaviour after a couple of months of usage and not immediately after a kernel upgrade (2.6.8+). However, I remember not seeing this behavior on older 2.6.* kernels.
The .5 second delay is a symptom rather than the cause ( bad hardware ? ).
-G