LKML Archive on
help / color / mirror / Atom feed
From: Kirill Elagin <>
To: Oliver Neukum <>
Subject: Re: USB autosuspend causing trouble with bluetooth
Date: Tue, 20 Jan 2015 16:18:49 +0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

I use a Logitech wireless keyboard (with a Unifying receiver) and it
keeps working fine even with `auto`.

That is, everything is OK if the receiver is plugged before
`power/control` is switched to `auto`.
But if I first set it to `auto`, then plug the receiver in, it is not
detected (nothing in dmesg). Kernel
detects it as soon as I `echo on` to the relevant `power/control`.

This laptop is too old to have USB3.0, both the receiver and BT are
attached to USB1.1 ports.
BTW I also noticed a strange thing: USB devices appear on different
buses when attached,
depending on their speed (e.g. the keyboard receiver is on bus 6 which
is USB1.1, while a
USB stick appears on bus 2 which is USB2.0 when I plug it into that
same physical port).
I’m not sure whether this is strange or normal, as I never really
payed attention.

On Tue Jan 20 2015 at 2:03:45 PM Oliver Neukum <> wrote:
> On Sun, 2015-01-18 at 17:30 +0400, Kirill Elagin wrote:
> > Hello,
> >
> > Recently I started having issues with my Apple Magic Trackpad and I
> > realised that the problem was with autosuspend. Whenever I have `auto`
> > in `power/control` of my BT adapter, `btmon` shows no packets,
> > nothing. As soon as I `echo on`, all the missing packets arrive.
> You are not getting remote wakeups. There are two possibilities
> 1. the firmware of your BT adapter is faulty and the device needs to
> be added to the list of quirky devices
> 2. a bug in the kernel breaks remote wakeup.
> We need to distinguish these cases. Could you connect another device
> that uses remote wakeup (HID, CDC-ACM, ... - a keyboard or a mouse is
> easiest) to a port connected to XHCI and test autosuspend on that
> device?
>         Regards
>                 Oliver

  reply	other threads:[~2015-01-20 12:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-18 13:30 Kirill Elagin
2015-01-20 11:03 ` Oliver Neukum
2015-01-20 12:18   ` Kirill Elagin [this message]
2015-01-20 12:34     ` Kirill Elagin
2015-01-20 14:06     ` Oliver Neukum
2015-01-20 14:58       ` Kirill Elagin
2015-01-20 17:41         ` Oliver Neukum
2015-01-20 19:25           ` Kirill Elagin
2015-01-20 21:47             ` Oliver Neukum
2015-01-24  9:55               ` Kirill Elagin
2015-01-26 17:00                 ` Kirill Elagin
2015-01-27 18:00                   ` Oliver Neukum

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:

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

  git send-email \
    --in-reply-to='' \ \ \ \
    --subject='Re: USB autosuspend causing trouble with bluetooth' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).