public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bob Gill <gillb4@telusplanet.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] 2.6.2 crazy mouse under heavy load
Date: Thu, 05 Feb 2004 13:59:12 -0700	[thread overview]
Message-ID: <1076014751.4682.22.camel@localhost.localdomain> (raw)

The exception seems to be coming from
linux-2.6.2/drivers/input/mouse/psmouse-base.c, specifically from

if (psmouse->state == PSMOUSE_ACTIVATED &&
            psmouse->pktcnt && time_after(jiffies, psmouse->last +
HZ/2)) {
                printk(KERN_WARNING "psmouse.c: %s at %s lost
synchronization, throwing %d bytes away.\n",
                       psmouse->name, psmouse->phys, psmouse->pktcnt);
                psmouse->pktcnt = 0;
        }


where (for me) HZ is 1804768000, and therefore HZ/2 is 902384000,  
psmouse->pktcnt is 3, and (I assume) PSMOUSE_ACTIVATED is non-0 after
boot.  I assume that pktcnt is fed by interrupt, and the problem then is
that psmouse->last + HZ/2 blows past the jiffies value, causing the
warning message to be issued.  When mouse service finally comes back,
pktcnt is non-zero (and possibly whatever the maximum is that it will
hold), and when it flushes, the mouse pointer goes nuts for a second. 
The real problem then, is why does the sum of ps->last + HZ/2 grow to
beyond the size of jiffies (or what is delaying the mouse service)?

This is just a rough guesstimate of what is going on, but seems to fit
the facts.   Cheers!

Bob


             reply	other threads:[~2004-02-05 20:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-05 20:59 Bob Gill [this message]
2004-02-05 22:05 ` [BUG] 2.6.2 crazy mouse under heavy load Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2004-02-05 17:34 Luis Miguel García
2004-02-05 17:34 Luis Miguel García
2004-02-05 15:24 ` Murilo Pontes
2004-02-05 14:17 Murilo Pontes
2004-02-05 18:18 ` Norberto Bensa
2004-02-06  8:38   ` Wichert Akkerman
2004-02-06  9:50 ` hungerburg
2004-02-08  5:58 ` Harald Dunkel

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=1076014751.4682.22.camel@localhost.localdomain \
    --to=gillb4@telusplanet.net \
    --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