linux-kernel - Re: USB autosuspend causing trouble with bluetooth

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CABVT_gcm0-3in9uOhpwM7VJrEdaE6982X01TGD29if8OQEW4Uw@mail.gmail.com>
Date:	Mon, 26 Jan 2015 21:00:36 +0400
From:	Kirill Elagin <kirelagin@...il.com>
To:	Oliver Neukum <oneukum@...e.de>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: USB autosuspend causing trouble with bluetooth

Things just got way worse with this hotplug thing.
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
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/