mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Murilo Pontes <murilo_pontes@yahoo.com.br>
To: LINUX KERNEL MAILING LIST <linux-kernel@vger.kernel.org>
Subject: Re: psmouse.c, throwing 3 bytes away
Date: Thu, 5 Feb 2004 19:33:47 +0000	[thread overview]
Message-ID: <200402051933.47597.murilo_pontes@yahoo.com.br> (raw)
In-Reply-To: <4022BC15.4090502@wanadoo.es>

I am not problems only using kde-3.2! 
I have problems running any Window manager,

The problem is similar for "Kernel losing many ticks", 
I think which problem is in VM system, "Kernel losing many ticks" is worst case of
kernel wait(long) get data from disk without DMA, but this is solve by activing DMA for all disks.

The time service maybe depend "wait kernel VM flush", like flush g++ buffers 
or disk cache in systems with ~512MB without swap partitions. 
This long wait increase kernel jiffes is not suficient for cause "Kernel losing many ticks",
but is suficient for break fewer bytes in mouse stream data..... 

In parallel may be I2c/acpi thermal and fan monitoring software like gkrellm, well like S.M.A.R.T.
on disks, increase wait states in hardware. 
Anyone is take this BUG always which i2c/acpi thermal and fan/s.m.a.r.t. is off????

Thanks

Em Qui 05 Fev 2004 21:56, Luis Miguel García escreveu:
> It's only me or we're having problems with kde 3.2?? Does it make sense? 
> perhaps it's only that it's big compile? or not?
> 
> I have this problemsometimes and even another problem in which 
> double-click converts itself in 40-clicks.
> 
> Any tip on that?
> 
> 
> 

  reply	other threads:[~2004-02-05 22:33 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 21:56 Luis Miguel García
2004-02-05 19:33 ` Murilo Pontes [this message]
2004-02-06  7:02 ` Claudio Martins
2004-02-06 10:12   ` Christian Unger
2004-02-06 17:52     ` Adrian Bunk
2004-02-06 18:03       ` Michael Buesch
2004-02-06 21:49     ` Claudio Martins
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05  6:18 Bob Gill
2004-02-05  2:20 Walt Nelson
2004-02-05  4:54 ` Claudio Martins
2004-02-05 10:20   ` Isaac Claymore
2004-02-09  6:15     ` Isaac Claymore
2004-02-09  9:09       ` Vojtech Pavlik
2004-02-09  9:49         ` Isaac Claymore
2004-02-09  9:52           ` Vojtech Pavlik
2004-02-05 13:40   ` Michael Buesch
2004-02-05 15:31     ` johann lombardi
2004-02-05  5:05 ` Mike Houston
2004-02-05 17:24 ` Murilo Pontes
2004-02-05 20:38   ` Vojtech Pavlik
2004-02-05 18:14     ` Murilo Pontes
2004-02-05 19:08     ` Murilo Pontes
2004-02-05 21:06     ` Michael Buesch
2004-02-05 22:10     ` Mike Houston
2004-02-06  7:15       ` Mike Houston
2004-02-06  8:06         ` Walt Nelson
2004-02-07  5:47           ` Mike Houston
2004-02-07  9:11             ` Murilo Pontes
2004-02-08 21:59               ` Vojtech Pavlik
2004-02-08 22:19                 ` aeriksson
2004-02-08 22:32                   ` Vojtech Pavlik
2004-02-08 23:03                   ` Bernd Schubert
2004-02-08 23:30                     ` Vojtech Pavlik
     [not found]                       ` <40278077.5070409@free.fr>
2004-02-09 22:25                         ` Bernd Schubert
2004-02-06  0:33     ` Pete Clements
2004-02-06 22:44     ` Kronos
2004-02-07  2:35     ` Jamie Lokier
2004-02-07  4:19       ` Gene Heskett

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200402051933.47597.murilo_pontes@yahoo.com.br \
    --to=murilo_pontes@yahoo.com.br \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®