linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gustavo Padovan <gustavo@padovan.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-bluetooth@vger.kernel.org
Subject: Re: Weird bluetooth keyboard regression - just me?
Date: Tue, 1 May 2012 13:00:14 -0300	[thread overview]
Message-ID: <20120501160014.GB1419@joana> (raw)
In-Reply-To: <20120501073711.028d31d6@lwn.net>

Hi Jon,

* Jonathan Corbet <corbet@lwn.net> [2012-05-01 07:37:11 -0600]:

> Life has not been conducive to frivolities like trying new kernels, but I
> finally gave 3.4-rc5 a go yesterday.  I'm seeing some decidedly weird
> keyboard behavior; it seems surprising that nobody else has complained.
> 
> I have a logitech Dinovo Edge bluetooth keyboard that I've used for
> years.  With 3.4 kernels, the keyboard generates no input until I've
> banged on it for a couple of seconds.  If I continually hit characters,
> they make it through; as soon as I stop for even a brief period (even
> somebody as verbose as me has to come up for air occasionally), it goes
> back to sleep.

This looks weird, I suspect of something. Could you try running
'bluetoothd -nd -P mgmtops' and check if the problem still happens too
you?

	Gustavo

  reply	other threads:[~2012-05-01 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-01 13:37 Weird bluetooth keyboard regression - just me? Jonathan Corbet
2012-05-01 16:00 ` Gustavo Padovan [this message]
2012-05-01 17:01 ` [now bisected] " Jonathan Corbet
2012-05-01 17:19   ` Matthew Garrett
2012-05-01 18:01     ` Jonathan Corbet
2012-05-01 18:31       ` Matthew Garrett
2012-05-01 18:39         ` Jonathan Corbet
2012-05-01 18:54           ` Matthew Garrett
2012-05-01 19:27             ` Matthew Garrett
2012-05-01 23:24               ` Jonathan Corbet
2012-05-02 21:50                 ` Matthew Garrett

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=20120501160014.GB1419@joana \
    --to=gustavo@padovan.org \
    --cc=corbet@lwn.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).