LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: Kirill Elagin <kirelagin@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: USB autosuspend causing trouble with bluetooth
Date: Tue, 27 Jan 2015 19:00:19 +0100	[thread overview]
Message-ID: <1422381619.14108.21.camel@linux-0dmf.site> (raw)
In-Reply-To: <CABVT_gcm0-3in9uOhpwM7VJrEdaE6982X01TGD29if8OQEW4Uw@mail.gmail.com>

On Mon, 2015-01-26 at 21:00 +0400, Kirill Elagin wrote:
> Things just got way worse with this hotplug thing.

Is that a new test or did you update?

> When the host power/control is set to `auto`, as soon as I insert  the
> Unifying receiver one of kworkers starts eating 100% of one of the

But it does not enumerate the dongle, does it?

> cores, according to `htop`. As soon as I `echo on` to power/control of
> the relevant USB hub the kworker stops doing this. This also happens
> with that other USB1.1 BT-dongle, so I assume any USB1.1 device would
> do. Also just unplugging the device is not enough, the kworker keeps
> eating CPU until I `echo on` to power/control.
> 
> Should I start a separate thread?
> Right now I'm on 3.18.2-gentoo.

Can you tell at which kernel version this started?

	Regards
		Oliver



      reply	other threads:[~2015-01-27 18:00 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
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 [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=1422381619.14108.21.camel@linux-0dmf.site \
    --to=oneukum@suse.de \
    --cc=kirelagin@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --subject='Re: USB autosuspend causing trouble with bluetooth' \
    /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

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