mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mikolaj J. Habryn" <dichro-evo@rcpt.to>
To: "Maksim (Max)  " Krasnyanskiy <maxk@qualcomm.com>
Cc: bluez-users@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Bluez-users] keyboard and mouse lost when bluez does things
Date: 13 Sep 2002 09:30:56 +1000	[thread overview]
Message-ID: <1031873456.21031.135.camel@orthos> (raw)
In-Reply-To: <5.1.0.14.2.20020912111832.0669a0b8@mail1.qualcomm.com>

On Fri, 2002-09-13 at 04:19, Maksim (Max) Krasnyanskiy wrote:
> At 02:27 PM 9/12/2002 +1000, Mikolaj J. Habryn wrote:
> >I have a Brainboxes CF card inside a Toshiba Portege 2000. When I do
> >just about anything with it - hciattach, for example - the keyboard and
> >mouse stop responding. The interrupt counts in /proc/interrupts for them
> >stop incrementing (*boggle*). Switching into and out of X fixes it. Any
> >suggestions?
> I never seen this kind of thing before.
> What kernel is this ?

I was afraid of that :P I see it with 2.4.20-pre{5,6}, 2.4.19 (I think),
and 2.5.32. It's a Toshiba Portege 2000, and I guess that means that
something excitingly wacky is happening with the interrupt hardware.
linux-kernel cc'd in case anyone there has ideas.

I did do some instrumenting inside the bluez code, and it appears to
lose the plot within the serial code somewhere - but not necessarily on
any given call into there. The behaviour is quite odd - for example,
starting an l2ping will immediately lock out the keyboard and mouse, and
the first ping response will show an RTT of ~5500 ms, following which
the remainder will come back within ~45ms. If I leave l2ping running
while restoring the keyboard and mouse by switching in and out of X,
they'll almost immediately freeze up again and there'll be another ~5500
ms burp in the l2ping replies.

m.

           reply	other threads:[~2002-09-12 23:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <5.1.0.14.2.20020912111832.0669a0b8@mail1.qualcomm.com>]

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=1031873456.21031.135.camel@orthos \
    --to=dichro-evo@rcpt.to \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    /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®