public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "christophe barbé" <christophe.barbe.ml@online.fr>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: usb-ohci, ov511, video4linux
Date: Sun, 20 Jan 2002 18:04:59 -0500	[thread overview]
Message-ID: <20020120230459.GN2873@online.fr> (raw)
In-Reply-To: <20020120154119.GB2873@online.fr> <20020120162258.GC16166@sliepen.warande.net> <20020120170837.GD2873@online.fr> <20020120225423.GA27088@kroah.com>
In-Reply-To: <20020120225423.GA27088@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

On Sun, Jan 20, 2002 at 02:54:23PM -0800, Greg KH wrote:
> On Sun, Jan 20, 2002 at 12:08:37PM -0500, christophe barbé wrote:
> > 
> > The problem with the usb mouse is there with or without webcam.
> 
> Is there any kernel log messages when the mouse "goes away"?
> It could be a flaky hub that is dropping the connection to your device,
> or a flaky mouse.  I've seen both of these before.

I see the mouse problem without hub.
So it could be a flaky mouse.
Is the fact that 'switching to the console and switching back to X
restore X' compatible with your idea ?

What sounds strange is that this appears only when CPU is mainly used by
others apps.

My idea is a timeout in X (without output : strange) due to a latency.

An important point here is that the mouse works fine with the 2.2 kernel
(I should have used 2.2.17 to 2.2.19).

Christophe

> 
> thanks,
> 
> greg k-h

-- 
Christophe Barbé <christophe.barbe@ufies.org>
GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8  F67A 8F45 2F1E D72C B41E

A qui sait comprendre, peu de mots suffisent.
(Intelligenti pauca.) 

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

      reply	other threads:[~2002-01-20 23:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-20 15:41 usb-ohci, ov511, video4linux christophe barbé
2002-01-20 16:22 ` Guus Sliepen
2002-01-20 17:08   ` christophe barbé
2002-01-20 22:54     ` Greg KH
2002-01-20 23:04       ` christophe barbé [this message]

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=20020120230459.GN2873@online.fr \
    --to=christophe.barbe.ml@online.fr \
    --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