You have device resets occurring in the kernel, even while the device is
blacklisted. I see this more as a kernel bug or a faulty hardware
s3nt fr0m a $martph0ne, excuse typ0s
On 13-Oct-2017 9:03 PM, <wg...@china.com> wrote:
> Yes, this is after I added the device ID in the configuration file.
>
>
> -----原始邮件-----
> *发件人:*"Ritesh Raj Sarraf" <r...@debian.org>
> *发送时间:*2017-10-12 18:14:39 (星期四)
> *收件人:* wg...@china.com
> *抄送:* 877...@bugs.debian.org
> *主题:* Re: Re: Bug#877519: Re: Re: Re: Bug#877519: Bluetooth mouse suspend
> while using cell
>
> Hello,
>
> Thank you for the log. Though it is *limited* in information, I think I
> have some clue from it.
>
> On Thu, 2017-10-12 at 15:11 +0800, wg...@china.com wrote:
>
> Oct 12 15:10:07 athena kernel: [ 572.402472] usb 1-7: new full-speed USB
> device number 7 using xhci_hcd
> Oct 12 15:10:08 athena kernel: [ 572.543621] usb 1-7: New USB device
> found, idVendor=8087, idProduct=0a2b
> Oct 12 15:10:08 athena kernel: [ 572.543631] usb 1-7: New USB device
> strings: Mfr=0, Product=0, SerialNumber=0
>
>
> You have device resent occuring in the kernel.
>
> Oct 12 15:10:08 athena kernel: [ 572.545725] Bluetooth: hci0: Bootloader
> revision 0.0 build 26 week 38 2015
> Oct 12 15:10:08 athena kernel: [ 572.546733] Bluetooth: hci0: Device
> revision is 16
> Oct 12 15:10:08 athena kernel: [ 572.546742] Bluetooth: hci0: Secure boot
> is enabled
> Oct 12 15:10:08 athena kernel: [ 572.546746] Bluetooth: hci0: OTP lock is
> enabled
> Oct 12 15:10:08 athena kernel: [ 572.546750] Bluetooth: hci0: API lock is
> enabled
> Oct 12 15:10:08 athena kernel: [ 572.546754] Bluetooth: hci0: Debug lock
> is disabled
> Oct 12 15:10:08 athena kernel: [ 572.546759] Bluetooth: hci0: Minimum
> firmware build 1 week 10 2014
> Oct 12 15:10:08 athena kernel: [ 572.547328] bluetooth hci0: firmware:
> direct-loading firmware intel/ibt-12-16.sfi
> Oct 12 15:10:08 athena kernel: [ 572.547339] Bluetooth: hci0: Found
> device firmware: intel/ibt-12-16.sfi
>
>
> Which leads to the bt stack being reinitialized.
>
> Oct 12 15:10:08 athena gnome-shell[7272]: Allocating size to
> ShellEmbeddedWindow 0x562665108ba0 without calling
> gtk_widget_get_preferred_width/height().
> How does the code know the size to allocate?
> Oct 12 15:10:08 athena laptop-mode: enabled, active
> Oct 12 15:10:08 athena cpufreqd: cpufreqd_set_profile : Couldn't set
> profile "On Demand High" set for cpu0 (3900000-390000-ondemand)
> Oct 12 15:10:08 athena cpufreqd: cpufreqd_loop : Cannot set
> policy, Rule unchanged ("none").
> Oct 12 15:10:08 athena root: Device /sys/bus/usb/devices/1-0:1.0 is
> blacklisted, skipping auto suspend.
> Oct 12 15:10:08 athena root: Device /sys/bus/usb/devices/1-7 is
> blacklisted, skipping auto suspend.
> Oct 12 15:10:08 athena root: Device /sys/bus/usb/devices/2-0:1.0 is
> blacklisted, skipping auto suspend.
> Oct 12 15:10:08 athena laptop-mode: enabled, active
> Oct 12 15:10:09 athena root: Device /sys/bus/usb/devices/1-0:1.0 is
> blacklisted, skipping auto suspend.
> Oct 12 15:10:09 athena kernel: [ 573.919793] Bluetooth: hci0: Waiting for
> firmware download to complete
> Oct 12 15:10:09 athena kernel: [ 573.920670] Bluetooth: hci0: Firmware
> loaded in 1344228 usecs
> Oct 12 15:10:09 athena kernel: [ 573.920694] Bluetooth: hci0: Waiting for
> device to boot
>
>
> And then enumerated.
>
> Oct 12 15:10:09 athena root: Device /sys/bus/usb/devices/1-7 is
> blacklisted, skipping auto suspend.
>
>
> Yet, all aside, this bug was about laptop-mode-tools not skipping the BT
> Mouse. But in this log, it is skipping it.
>
> Is this after you added the device ID in the configuration file, or before
> it itself ?
>
>
> --
> Ritesh Raj Sarraf | http://people.debian.org/~rrs
> Debian - The Universal Operating System
>
>
