You are not logged in.

Pages: 1

#1 2017-11-13 05:30:16

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

[SOLVED] Bluetooth Fails on Lid Close

Hello,
I have noticed a very particular issue pertaining bluetooth.
I have a Logitech K810 connected to my Zenbook UX330UAK, and I want to be able to use my bluetooth keyboard when I have my laptop docked to my monitor.
The problem that I have having is that when I connect my keyboard via bluetooth and after 2 - 8 seconds of having the lid close the "Link Quality" drops to 0 (What Blueman calls it), the keyboard is still "connected", as bluetoothctl is saying, but on the keyboard it clearly says its not connected. Sometimes when this happens whatever key I press last is repeated many times, until I forcefully quit in bluetoothctl or blueman-manager.

(This is what I mean by "Link Quality")
https://lh3.googleusercontent.com/-CHjz … -11-01.png

Trying to reconnect the keyboard again when the laptop lid is opened again does not work.
The only way to get the keyboard working again is do restart the kernel module itself by doing:

sudo modprobe -r btusb && sudo modprobe btusb

There has been one incident where there has been OOPS when trying to shutdown the system (pictures are added below)

This is what dmesg is outputing during the connection, and failure of the keyboard:

--SNIP--
[    2.560912] usbcore: registered new interface driver btusb
[    2.565338] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[    2.565554] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    2.572224] Bluetooth: hci0: Device revision is 5
[    2.572225] Bluetooth: hci0: Secure boot is enabled
[    2.572225] Bluetooth: hci0: OTP lock is enabled
[    2.572226] Bluetooth: hci0: API lock is enabled
[    2.572226] Bluetooth: hci0: Debug lock is disabled
[    2.572227] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[    2.574912] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[    2.583905] media: Linux media interface: v0.10
[    2.584725] usbcore: registered new interface driver usbhid
[    2.584725] usbhid: USB HID core driver
[    2.591420] Linux video capture interface: v2.00
[    2.604240] uvcvideo: Found UVC 1.00 device USB2.0 HD UVC WebCam (0bda:58d1)
[    2.606733] uvcvideo 1-5:1.0: Entity type for entity Realtek Extended Controls Unit was not initialized!
[    2.606735] uvcvideo 1-5:1.0: Entity type for entity Extension 4 was not initialized!
[    2.606736] uvcvideo 1-5:1.0: Entity type for entity Processing 2 was not initialized!
[    2.606737] uvcvideo 1-5:1.0: Entity type for entity Camera 1 was not initialized!
[    2.606802] input: USB2.0 HD UVC WebCam: USB2.0 HD as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input17
[    2.606871] usbcore: registered new interface driver uvcvideo
[    2.606871] USB Video Class driver (1.1.1)
[    2.647772] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    2.647773] Bluetooth: BNEP filters: protocol multicast
[    2.647775] Bluetooth: BNEP socket layer initialized
[    2.672983] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:25A7:2433.0002/input/input18
[    2.726886] hid-generic 0003:25A7:2433.0002: input,hidraw1: USB HID v1.01 Keyboard [2.4G 2.4G Wireless Device] on usb-0000:00:14.0-2/input0
[    2.727373] input: 2.4G 2.4G Wireless Device as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:25A7:2433.0003/input/input19
[    2.783594] hid-generic 0003:25A7:2433.0003: input,hiddev0,hidraw2: USB HID v1.01 Mouse [2.4G 2.4G Wireless Device] on usb-0000:00:14.0-2/input1
[    2.809919] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    3.067076] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    3.091227] Console: switching to colour frame buffer device 240x67
[    3.112335] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[    3.149004] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    3.330564] [drm] RC6 on
[    4.072500] Bluetooth: hci0: Waiting for firmware download to complete
[    4.072957] Bluetooth: hci0: Firmware loaded in 1476640 usecs
[    4.072992] Bluetooth: hci0: Waiting for device to boot
[    4.083996] Bluetooth: hci0: Device booted in 10759 usecs
[    4.085594] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[    4.088976] Bluetooth: hci0: Applying Intel DDC parameters completed
[    4.350319] fuse init (API version 7.26)
[    4.366716] EXT4-fs (sda5): re-mounted. Opts: data=ordered,commit=600
[    7.390678] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[    8.565633] Bluetooth: RFCOMM TTY layer initialized
[    8.565640] Bluetooth: RFCOMM socket layer initialized
[    8.565643] Bluetooth: RFCOMM ver 1.11
[    8.742989] wlp2s0: authenticate with b4:75:0e:52:72:19
[    8.755015] wlp2s0: send auth to b4:75:0e:52:72:19 (try 1/3)
[    8.763512] wlp2s0: authenticated
[    8.766780] wlp2s0: associate with b4:75:0e:52:72:19 (try 1/3)
[    8.771090] wlp2s0: RX AssocResp from b4:75:0e:52:72:19 (capab=0x1411 status=0 aid=2)
[    8.772235] wlp2s0: associated
[    8.772269] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[  936.781963] traps: xfce4-notifyd[7927] trap stack segment ip:7f9f70ca2fc3 sp:7ffd23cd4ce0 error:0 in libc-2.26.so[7f9f70c25000+1ae000]
[ 1127.076713] polybar[7465]: segfault at 1a ip 000055904f0f1305 sp 00007ffe97819290 error 4 in polybar[55904f019000+2e7000]
[ 1127.080302] wlp2s0: deauthenticating from b4:75:0e:52:72:19 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1127.131640] wlp2s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
[ 1127.149496] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1129.592797] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 1131.026143] wlp2s0: authenticate with b4:75:0e:52:72:19
[ 1131.034335] wlp2s0: send auth to b4:75:0e:52:72:19 (try 1/3)
[ 1131.037463] wlp2s0: authenticated
[ 1131.040415] wlp2s0: associate with b4:75:0e:52:72:19 (try 1/3)
[ 1131.044353] wlp2s0: RX AssocResp from b4:75:0e:52:72:19 (capab=0x1411 status=0 aid=2)
[ 1131.046046] wlp2s0: associated
[ 1131.046078] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[ 1349.200804] ntfs: driver 2.1.32 [Flags: R/W MODULE].
[ 1349.223355] ntfs: volume version 3.1.
[ 1349.227145] ntfs: (device sda3): load_system_files(): Windows is hibernated.  Mounting read-only.  Run chkdsk.
[ 1659.361211] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 1659.361216] Bluetooth: HIDP socket layer initialized
[ 1692.395525] usbcore: deregistering interface driver btusb
[ 1692.395659] Bluetooth: hci0 urb ffff9356e11c8b40 failed to resubmit (2)
[ 1692.473884] usbcore: registered new interface driver btusb
[ 1692.478997] Bluetooth: hci0: Firmware revision 0.0 build 118 week 50 2016
[ 1701.076838] hid-generic 0005:046D:B319.0004: unknown main item tag 0x0
[ 1701.077589] input: Logitech K810 as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input20
[ 1701.078270] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 14:ab:c5:ed:10:ab

What systemctl status bluetooth.service gives out

● bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disable
   Active: active (running) since Sun 2017-11-12 21:41:21 MST; 31min ago
     Docs: man:bluetoothd(8)
 Main PID: 1606 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/bluetooth.service
           └─1606 /usr/lib/bluetooth/bluetoothd

Nov 12 22:00:05 Zenbook bluetoothd[1606]: Endpoint unregistered: sender=:1.141 path=/MediaEnd
Nov 12 22:00:09 Zenbook bluetoothd[1606]: Endpoint registered: sender=:1.446 path=/MediaEndpo
Nov 12 22:00:09 Zenbook bluetoothd[1606]: Endpoint registered: sender=:1.446 path=/MediaEndpo
Nov 12 22:08:58 Zenbook bluetoothd[1606]: Can't get HIDP connection info
Nov 12 22:09:31 Zenbook bluetoothd[1606]: connect error: Software caused connection abort (10
Nov 12 22:09:31 Zenbook bluetoothd[1606]: Endpoint unregistered: sender=:1.446 path=/MediaEnd
Nov 12 22:09:31 Zenbook bluetoothd[1606]: Endpoint unregistered: sender=:1.446 path=/MediaEnd
Nov 12 22:09:31 Zenbook bluetoothd[1606]: Endpoint registered: sender=:1.446 path=/MediaEndpo
Nov 12 22:09:31 Zenbook bluetoothd[1606]: Endpoint registered: sender=:1.446 path=/MediaEndpo
Nov 12 22:09:34 Zenbook bluetoothd[1606]: Can't get HIDP connection info

What journalctl -b outputs

Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Logs begin at Thu 2017-07-27 07:11:07 MST, end at Sun 2017-11-12 22:04:51 MST. --
Nov 12 21:41:26 Zenbook systemd[7435]: Reached target Paths.
Nov 12 21:41:26 Zenbook systemd[7435]: Reached target Timers.
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on GnuPG cryptographic agent and passphrase 
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on GnuPG cryptographic agent (ssh-agent emul
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on Sound System.
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on GnuPG cryptographic agent and passphrase 
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on GnuPG cryptographic agent and passphrase 
Nov 12 21:41:26 Zenbook systemd[7435]: Starting D-Bus User Message Bus Socket.
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on GnuPG network certificate management daem
Nov 12 21:41:26 Zenbook systemd[7435]: Listening on D-Bus User Message Bus Socket.
Nov 12 21:41:26 Zenbook systemd[7435]: Reached target Sockets.
Nov 12 21:41:26 Zenbook systemd[7435]: Reached target Basic System.
Nov 12 21:41:26 Zenbook systemd[7435]: Reached target Default.
Nov 12 21:41:26 Zenbook systemd[7435]: Startup finished in 15ms.
Nov 12 21:41:26 Zenbook systemd[7435]: Started D-Bus User Message Bus.
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Virtual filesystem service...
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Virtual filesystem service.
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Sound Service...
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Accessibility services bus...
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Accessibility services bus.
Nov 12 21:41:26 Zenbook at-spi-bus-launcher[7550]: dbus-daemon[7560]: Activating service name
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating service nam
Nov 12 21:41:26 Zenbook at-spi-bus-launcher[7550]: dbus-daemon[7560]: Successfully activated 
Nov 12 21:41:26 Zenbook at-spi-bus-launcher[7550]: SpiRegistry daemon is running with well-kn
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Zeitgeist activity log service...
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Zeitgeist activity log service.
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Zeitgeist full-text search indexer...
Nov 12 21:41:26 Zenbook zeitgeist-daemon[7577]: [04:41:26.699227 WARNING] zeitgeist-daemon.va
Nov 12 21:41:26 Zenbook zeitgeist-daemon[7577]: [04:41:26.699668 WARNING] zeitgeist-daemon.va
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Virtual filesystem service - disk device moni
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Zeitgeist full-text search indexer.
Nov 12 21:41:26 Zenbook zeitgeist-daemon[7577]: [04:41:26.730321 WARNING] zeitgeist-daemon.va
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Virtual filesystem service - disk device monit
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Activating via systemd
Nov 12 21:41:26 Zenbook systemd[7435]: Starting Virtual filesystem service - Media Transfer P
Nov 12 21:41:26 Zenbook dbus-daemon[7454]: [session uid=1000 pid=7454] Successfully activated
Nov 12 21:41:26 Zenbook systemd[7435]: Started Virtual filesystem service - Media Transfer Pr

The OOPS
https://lh3.googleusercontent.com/-Sdip … -11-12.png
https://lh3.googleusercontent.com/-4NNQ … -11-12.png
https://lh3.googleusercontent.com/-yLY_ … -11-12.png
https://lh3.googleusercontent.com/-5Q6b … -11-12.png
https://lh3.googleusercontent.com/-W-Fo … -11-12.png
https://lh3.googleusercontent.com/-LEug … -11-12.png
https://lh3.googleusercontent.com/-p6lz … -11-12.png


Right now I'm not entirely sure what I should be looking for... There hasn't been anything for me that is a red flag.

Other things to mention:
I have created a service that will automatically run this piece of code:

#!/bin/bash

echo -e 'power on\nconnect 34:88:5D:5D:EF:64\t\nquit' | bluetoothctl

This is to enable me to use my bluetooth keyboard on login.
I do have a power manager (laptop-mode-tools), but I have tested if the bluetooth with it REMOVED, and it still did even with laptop-mode-tools removed.

EDIT:
NOT SOLVED

Last edited by Hacksaurus_Babu (2017-11-29 05:57:15)

Offline

#2 2017-11-13 08:42:40

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

Did you check rfkill?
Sounds as if either systemd or acpid map the lid switch to an rfkill trigger.
Maybe the lid is even unrelated and your dock includes an ethernet connection (and switches the wifi chip which often does bluetooth on the fly)?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2017-11-13 23:10:55

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

By using this line of code:

sleep 3; rfkill; cat /proc/acpi/button/lid/LID/state

I connected my bluetooth keyboard closed my lid, and the got these results:

ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked
state:      closed

It doesn't seem like rkill is doing anything...

Offline

#4 2017-11-13 23:49:41

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

stuvwxyz This is quite weird, I updated my kernel to 4.13.12-1 and magically my this problem disappeared...
I'm going to keep this unsolved for a while, because this may or may not be a fluke...

Last edited by Hacksaurus_Babu (2017-11-13 23:50:59)

Offline

#5 2017-11-14 01:14:41

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

This clearly seems not to be a fluke... The kernel updated fixed up everything...

Marking as solved.

Offline

#6 2017-11-14 03:47:22

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

After rebooting a couple of times going from Windows to Linux, I finally thought I solved this problem, but no! The problem came up again and it isn't going away...

I got this oops when trying to connect to my keyboard... Does this mean anything to anyone?

[  202.066980] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/bluetooth/hci0/hci0:256'
[  202.066991] ------------[ cut here ]------------
[  202.066996] WARNING: CPU: 3 PID: 1161 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
[  202.066997] Modules linked in: hidp ccm rfcomm fuse cmac bnep hid_generic uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops videobuf2_v4l2 usbhid videobuf2_core videodev media snd_hda_codec_hdmi arc4 snd_hda_codec_realtek snd_hda_codec_generic joydev mousedev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_skl kvm_intel snd_soc_skl_ipc kvm snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_soc_core irqbypass iTCO_wdt iwlmvm asus_nb_wmi iTCO_vendor_support crct10dif_pclmul hid_multitouch asus_wmi crc32_pclmul wmi_bmof snd_compress sparse_keymap snd_pcm_dmaengine mac80211 ac97_bus ghash_clmulni_intel nls_iso8859_1 nls_cp437 pcbc vfat fat evdev snd_hda_intel input_leds iwlwifi snd_hda_codec aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate
[  202.067035]  intel_rapl_perf mac_hid pcspkr i915 hci_uart i2c_i801 snd_hda_core snd_hwdep snd_pcm snd_timer snd i2c_algo_bit soundcore drm_kms_helper cfg80211 btbcm processor_thermal_device btqca drm mei_me shpchp intel_gtt idma64 agpgart mei syscopyarea sysfillrect sysimgblt fb_sys_fops intel_soc_dts_iosf intel_lpss_pci i2c_hid btintel intel_pch_thermal thermal wmi hid ac bluetooth battery ecdh_generic pinctrl_sunrisepoint intel_lpss_acpi int3403_thermal int340x_thermal_zone rfkill intel_lpss video pinctrl_intel tpm_crb tpm_tis acpi_pad tpm_tis_core acpi_als int3400_thermal tpm kfifo_buf industrialio asus_wireless acpi_thermal_rel button led_class sch_fq_codel crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto sd_mod serio_raw atkbd libps2 crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common i8042 serio
[  202.067085] CPU: 3 PID: 1161 Comm: kworker/u9:2 Not tainted 4.13.12-1-ARCH #1
[  202.067086] Hardware name: ASUSTeK COMPUTER INC. UX330UAK/UX330UAK, BIOS UX330UAK.305 05/02/2017
[  202.067093] Workqueue: hci0 hci_rx_work [bluetooth]
[  202.067095] task: ffff98ad48bf3e00 task.stack: ffffaf6241e3c000
[  202.067098] RIP: 0010:sysfs_warn_dup+0x56/0x70
[  202.067099] RSP: 0018:ffffaf6241e3fb80 EFLAGS: 00010282
[  202.067100] RAX: 0000000000000073 RBX: ffff98acbf9f9000 RCX: 0000000000000000
[  202.067101] RDX: 0000000000000000 RSI: ffff98ad5ed8dc78 RDI: ffff98ad5ed8dc78
[  202.067102] RBP: ffffaf6241e3fb98 R08: 000000000000031d R09: 0000000000000004
[  202.067103] R10: 0000000000000001 R11: 0000000000000001 R12: ffff98acf821ed20
[  202.067104] R13: ffff98ad48875d20 R14: ffff98ad47009288 R15: ffff98ad53cd2c50
[  202.067106] FS:  0000000000000000(0000) GS:ffff98ad5ed80000(0000) knlGS:0000000000000000
[  202.067107] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  202.067108] CR2: 000009bccf2fe000 CR3: 00000002048e8000 CR4: 00000000003406e0
[  202.067109] Call Trace:
[  202.067114]  sysfs_create_dir_ns+0x77/0x90
[  202.067117]  kobject_add_internal+0xaa/0x2b0
[  202.067119]  kobject_add+0x71/0xd0
[  202.067122]  ? kfree_const+0x20/0x30
[  202.067125]  device_add+0x12c/0x680
[  202.067132]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
[  202.067138]  hci_conn_complete_evt.isra.46+0xe3/0x430 [bluetooth]
[  202.067144]  hci_event_packet+0x12ee/0x2c70 [bluetooth]
[  202.067150]  ? _raw_spin_unlock_irq+0x17/0x30
[  202.067155]  hci_rx_work+0x19f/0x3b0 [bluetooth]
[  202.067160]  ? hci_rx_work+0x19f/0x3b0 [bluetooth]
[  202.067162]  ? __schedule+0x241/0x890
[  202.067165]  process_one_work+0x1de/0x430
[  202.067167]  worker_thread+0x48/0x400
[  202.067169]  kthread+0x125/0x140
[  202.067170]  ? process_one_work+0x430/0x430
[  202.067172]  ? kthread_create_on_node+0x70/0x70
[  202.067175]  ret_from_fork+0x25/0x30
[  202.067176] Code: 85 c0 48 89 c3 74 12 b9 00 10 00 00 48 89 c2 31 f6 4c 89 ef e8 5c c8 ff ff 4c 89 e2 48 89 de 48 c7 c7 a8 82 95 b4 e8 bb 27 e3 ff <0f> ff 48 89 df e8 00 3c f5 ff 5b 41 5c 41 5d 5d c3 66 0f 1f 84 
[  202.067205] ---[ end trace 9407d396d0c27e0e ]---
[  202.067207] kobject_add_internal failed for hci0:256 with -EEXIST, don't try to register things with the same name in the same directory.
[  202.067217] ------------[ cut here ]------------
[  202.067219] WARNING: CPU: 3 PID: 1161 at lib/kobject.c:240 kobject_add_internal+0x269/0x2b0
[  202.067220] Modules linked in: hidp ccm rfcomm fuse cmac bnep hid_generic uvcvideo btusb videobuf2_vmalloc btrtl videobuf2_memops videobuf2_v4l2 usbhid videobuf2_core videodev media snd_hda_codec_hdmi arc4 snd_hda_codec_realtek snd_hda_codec_generic joydev mousedev intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_skl kvm_intel snd_soc_skl_ipc kvm snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match snd_soc_core irqbypass iTCO_wdt iwlmvm asus_nb_wmi iTCO_vendor_support crct10dif_pclmul hid_multitouch asus_wmi crc32_pclmul wmi_bmof snd_compress sparse_keymap snd_pcm_dmaengine mac80211 ac97_bus ghash_clmulni_intel nls_iso8859_1 nls_cp437 pcbc vfat fat evdev snd_hda_intel input_leds iwlwifi snd_hda_codec aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate
[  202.067253]  intel_rapl_perf mac_hid pcspkr i915 hci_uart i2c_i801 snd_hda_core snd_hwdep snd_pcm snd_timer snd i2c_algo_bit soundcore drm_kms_helper cfg80211 btbcm processor_thermal_device btqca drm mei_me shpchp intel_gtt idma64 agpgart mei syscopyarea sysfillrect sysimgblt fb_sys_fops intel_soc_dts_iosf intel_lpss_pci i2c_hid btintel intel_pch_thermal thermal wmi hid ac bluetooth battery ecdh_generic pinctrl_sunrisepoint intel_lpss_acpi int3403_thermal int340x_thermal_zone rfkill intel_lpss video pinctrl_intel tpm_crb tpm_tis acpi_pad tpm_tis_core acpi_als int3400_thermal tpm kfifo_buf industrialio asus_wireless acpi_thermal_rel button led_class sch_fq_codel crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto sd_mod serio_raw atkbd libps2 crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common i8042 serio
[  202.067294] CPU: 3 PID: 1161 Comm: kworker/u9:2 Tainted: G        W       4.13.12-1-ARCH #1
[  202.067295] Hardware name: ASUSTeK COMPUTER INC. UX330UAK/UX330UAK, BIOS UX330UAK.305 05/02/2017
[  202.067301] Workqueue: hci0 hci_rx_work [bluetooth]
[  202.067302] task: ffff98ad48bf3e00 task.stack: ffffaf6241e3c000
[  202.067304] RIP: 0010:kobject_add_internal+0x269/0x2b0
[  202.067305] RSP: 0018:ffffaf6241e3fbd0 EFLAGS: 00010286
[  202.067307] RAX: 000000000000007d RBX: ffff98ad47009298 RCX: 0000000000000006
[  202.067307] RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff98ad5ed8dc70
[  202.067308] RBP: ffffaf6241e3fc00 R08: 0000000000000346 R09: 0000000000000004
[  202.067309] R10: ffffee6d06fe7e00 R11: 0000000000000001 R12: ffff98ad53cd2c50
[  202.067310] R13: 00000000ffffffef R14: ffff98ad47009288 R15: ffff98ad53cd2c50
[  202.067311] FS:  0000000000000000(0000) GS:ffff98ad5ed80000(0000) knlGS:0000000000000000
[  202.067312] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  202.067313] CR2: 000009bccf2fe000 CR3: 00000002048e8000 CR4: 00000000003406e0
[  202.067314] Call Trace:
[  202.067316]  kobject_add+0x71/0xd0
[  202.067319]  ? kfree_const+0x20/0x30
[  202.067321]  device_add+0x12c/0x680
[  202.067328]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
[  202.067333]  hci_conn_complete_evt.isra.46+0xe3/0x430 [bluetooth]
[  202.067339]  hci_event_packet+0x12ee/0x2c70 [bluetooth]
[  202.067341]  ? _raw_spin_unlock_irq+0x17/0x30
[  202.067346]  hci_rx_work+0x19f/0x3b0 [bluetooth]
[  202.067351]  ? hci_rx_work+0x19f/0x3b0 [bluetooth]
[  202.067352]  ? __schedule+0x241/0x890
[  202.067354]  process_one_work+0x1de/0x430
[  202.067356]  worker_thread+0x48/0x400
[  202.067358]  kthread+0x125/0x140
[  202.067360]  ? process_one_work+0x430/0x430
[  202.067361]  ? kthread_create_on_node+0x70/0x70
[  202.067363]  ret_from_fork+0x25/0x30
[  202.067365] Code: 49 89 c4 48 85 ff 0f 84 44 fe ff ff 48 83 c7 18 e9 01 fe ff ff 48 8b 13 48 c7 c6 70 79 89 b4 48 c7 c7 48 2f 9a b4 e8 58 49 a8 ff <0f> ff e9 92 fe ff ff 0f ff eb a5 0f ff eb 98 41 bd fe ff ff ff 
[  202.067395] ---[ end trace 9407d396d0c27e0f ]---
[  202.067396] Bluetooth: Failed to register connection device

Offline

#7 2017-11-14 07:59:05

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/bluetooth/hci0/hci0:256'

Seems like you're trying to register a device that had previously not been unregistered.

"Windows" however was a trigger, see your dmesg

[ 1349.227145] ntfs: (device sda3): load_system_files(): Windows is hibernated.  Mounting read-only.  Run chkdsk.

Deactivate that **************** "fastboot" ******* thing.
Windows is cheating on you. Nothing boots "fast", this is simply hibernation and not only leaves HW in undefined states but also expects those changes not to change. It's an absolute no-go for *any* kind of dualbooting, you can not even reliably boot a live-linux or a rescue medium (incl. any other Windows OS). This is a strictly "one os ever boots" approach.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#8 2017-11-15 01:22:15

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

I actually have disabled "fastboot", What I did was I went to the Control Panel and then when to the Power Settings and I checked off fastboot.
I might have to check again if I actually did do it, or if this may even be a Windows bug....

Offline

#9 2017-11-15 01:53:45

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

There could also be another possibility of why this is occuring, as dmesg outputs:

[    1.922209] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80
[    1.922284] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80

As you said before the acpid map could be a problem.

This may or may not be a related problem, but I made a topic on it earlier: This describes the problem that I have with bluetooth: https://bbs.archlinux.org/viewtopic.php?id=229227

Last edited by Hacksaurus_Babu (2017-11-15 01:57:53)

Offline

#10 2017-11-15 08:04:44

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

This is not an acpid message and windows *is* hibernated. So if you didn't expicitly hibernate it, you've fastboot active (windows might have reset it with an update or whatever)

For a full windows shutdown run

shutdown /s /f /t 0

from cmd.exe

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#11 2017-11-16 00:23:48

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

Sorry seth, but that did not work... Is there any way to check in Linux if Windows is hibernated?
Just to make sure I'm doing this correctly?

EDIT:
Now it even fails without closing the lid, when shutting down with those options: This is what dmesg outputs:

--SNIP--
[    9.864053] wlp2s0: associated
[    9.864082] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
[   33.554611] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   33.554615] Bluetooth: HIDP socket layer initialized
[   33.555267] hid-generic 0005:046D:B319.0004: unknown main item tag 0x0
[   33.555387] input: Logitech K810 as /devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/bluetooth/hci0/hci0:256/0005:046D:B319.0004/input/input20
[   33.556553] hid-generic 0005:046D:B319.0004: input,hidraw3: BLUETOOTH HID v12.02 Keyboard [Logitech K810] on 14:ab:c5:ed:10:ab
[   43.146860] iwlwifi 0000:02:00.0: Queue 11 is active on fifo 1 and stuck for 10000 ms. SW [153, 37] HW [153, 37] FH TRB=0x0c010b0a8
[   43.147186] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[   43.147442] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[   43.147443] iwlwifi 0000:02:00.0: Status: 0x00000200, count: 6
[   43.147444] iwlwifi 0000:02:00.0: Loaded firmware version: 31.532993.0
[   43.147446] iwlwifi 0000:02:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[   43.147447] iwlwifi 0000:02:00.0: 0x00000230 | trm_hw_status0
[   43.147448] iwlwifi 0000:02:00.0: 0x00000001 | trm_hw_status1
[   43.147449] iwlwifi 0000:02:00.0: 0x00010040 | branchlink2
[   43.147450] iwlwifi 0000:02:00.0: 0x00028DA6 | interruptlink1
[   43.147450] iwlwifi 0000:02:00.0: 0x0002C90E | interruptlink2
[   43.147451] iwlwifi 0000:02:00.0: 0x00000000 | data1
[   43.147452] iwlwifi 0000:02:00.0: 0x00000080 | data2
[   43.147453] iwlwifi 0000:02:00.0: 0x07830000 | data3
[   43.147454] iwlwifi 0000:02:00.0: 0x5140F572 | beacon time
[   43.147455] iwlwifi 0000:02:00.0: 0x1A69BA93 | tsf low
[   43.147456] iwlwifi 0000:02:00.0: 0x0000018D | tsf hi
[   43.147457] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[   43.147457] iwlwifi 0000:02:00.0: 0x02463BC4 | time gp2
[   43.147458] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
[   43.147459] iwlwifi 0000:02:00.0: 0x0000001F | uCode version major
[   43.147460] iwlwifi 0000:02:00.0: 0x00082201 | uCode version minor
[   43.147461] iwlwifi 0000:02:00.0: 0x00000201 | hw version
[   43.147462] iwlwifi 0000:02:00.0: 0x00489008 | board version
[   43.147463] iwlwifi 0000:02:00.0: 0x00BF019C | hcmd
[   43.147464] iwlwifi 0000:02:00.0: 0x2402200A | isr0
[   43.147464] iwlwifi 0000:02:00.0: 0x00800000 | isr1
[   43.147465] iwlwifi 0000:02:00.0: 0x0800180A | isr2
[   43.147466] iwlwifi 0000:02:00.0: 0x004154C0 | isr3
[   43.147467] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[   43.147468] iwlwifi 0000:02:00.0: 0x00BF019C | last cmd Id
[   43.147469] iwlwifi 0000:02:00.0: 0x00000000 | wait_event
[   43.147470] iwlwifi 0000:02:00.0: 0x00000080 | l2p_control
[   43.147470] iwlwifi 0000:02:00.0: 0x00010030 | l2p_duration
[   43.147471] iwlwifi 0000:02:00.0: 0x0000003F | l2p_mhvalid
[   43.147472] iwlwifi 0000:02:00.0: 0x00000080 | l2p_addr_match
[   43.147473] iwlwifi 0000:02:00.0: 0x0000000D | lmpm_pmg_sel
[   43.147474] iwlwifi 0000:02:00.0: 0x15062149 | timestamp
[   43.147475] iwlwifi 0000:02:00.0: 0x0034A0B0 | flow_handler
[   43.147665] iwlwifi 0000:02:00.0: 0x00000000 | ADVANCED_SYSASSERT
[   43.147665] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[   43.147666] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink2
[   43.147667] iwlwifi 0000:02:00.0: 0x00000000 | umac interruptlink1
[   43.147668] iwlwifi 0000:02:00.0: 0x00000000 | umac interruptlink2
[   43.147669] iwlwifi 0000:02:00.0: 0x00000000 | umac data1
[   43.147670] iwlwifi 0000:02:00.0: 0x00000000 | umac data2
[   43.147670] iwlwifi 0000:02:00.0: 0x00000000 | umac data3
[   43.147671] iwlwifi 0000:02:00.0: 0x00000000 | umac major
[   43.147672] iwlwifi 0000:02:00.0: 0x00000000 | umac minor
[   43.147673] iwlwifi 0000:02:00.0: 0x00000000 | frame pointer
[   43.147674] iwlwifi 0000:02:00.0: 0x00000000 | stack pointer
[   43.147675] iwlwifi 0000:02:00.0: 0x00000000 | last host cmd
[   43.147675] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[   43.147678] ieee80211 phy0: Hardware restart was requested

Tried to use my bluetooth headset now this came up:

[  229.885216] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:14.0/usb1/1-8/1-8:1.0/bluetooth/hci0/hci0:256'
[  229.885239] ------------[ cut here ]------------
[  229.885251] WARNING: CPU: 0 PID: 355 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x56/0x70
[  229.885253] Modules linked in: hidp cmac ccm rfcomm fuse uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media bnep btusb btrtl snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 joydev mousedev iTCO_wdt iTCO_vendor_support snd_soc_skl intel_rapl snd_soc_skl_ipc snd_soc_sst_ipc hid_multitouch x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match kvm_intel kvm irqbypass crct10dif_pclmul asus_nb_wmi crc32_pclmul asus_wmi sparse_keymap wmi_bmof ghash_clmulni_intel iwlmvm pcbc snd_soc_core mac80211 nls_iso8859_1 nls_cp437 i915 snd_compress vfat fat snd_pcm_dmaengine ac97_bus iwlwifi aesni_intel aes_x86_64 i2c_algo_bit drm_kms_helper crypto_simd glue_helper cryptd cfg80211 snd_hda_intel intel_cstate intel_rapl_perf
[  229.885353]  snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd evdev input_leds mac_hid pcspkr soundcore i2c_i801 shpchp drm intel_gtt idma64 agpgart mei_me syscopyarea sysfillrect sysimgblt fb_sys_fops mei processor_thermal_device intel_lpss_pci intel_pch_thermal intel_soc_dts_iosf thermal wmi i2c_hid hci_uart ac btbcm battery btqca btintel int3403_thermal int340x_thermal_zone bluetooth tpm_crb acpi_als tpm_tis tpm_tis_core kfifo_buf ecdh_generic pinctrl_sunrisepoint intel_lpss_acpi video rfkill pinctrl_intel intel_lpss industrialio tpm asus_wireless button int3400_thermal led_class acpi_pad acpi_thermal_rel sch_fq_codel crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto hid_generic usbhid hid sd_mod serio_raw atkbd libps2 crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common i8042 serio
[  229.885472] CPU: 0 PID: 355 Comm: kworker/u9:1 Not tainted 4.13.12-1-ARCH #1
[  229.885475] Hardware name: ASUSTeK COMPUTER INC. UX330UAK/UX330UAK, BIOS UX330UAK.305 05/02/2017
[  229.885492] Workqueue: hci0 hci_rx_work [bluetooth]
[  229.885496] task: ffff957f92c46c80 task.stack: ffffae2f01530000
[  229.885505] RIP: 0010:sysfs_warn_dup+0x56/0x70
[  229.885508] RSP: 0018:ffffae2f01533b80 EFLAGS: 00010282
[  229.885512] RAX: 0000000000000073 RBX: ffff957f063c7000 RCX: 0000000000000000
[  229.885515] RDX: 0000000000000000 RSI: ffff957f9ec0dc78 RDI: ffff957f9ec0dc78
[  229.885517] RBP: ffffae2f01533b98 R08: 000000000000035c R09: 0000000000000004
[  229.885518] R10: 0000000000000001 R11: 0000000000000001 R12: ffff957f3362d420
[  229.885521] R13: ffff957f931e5ca8 R14: ffff957f06214288 R15: ffff957f942f2c50
[  229.885524] FS:  0000000000000000(0000) GS:ffff957f9ec00000(0000) knlGS:0000000000000000
[  229.885526] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  229.885529] CR2: 000055eb45b86530 CR3: 000000002fa09000 CR4: 00000000003406f0
[  229.885532] Call Trace:
[  229.885543]  sysfs_create_dir_ns+0x77/0x90
[  229.885551]  kobject_add_internal+0xaa/0x2b0
[  229.885558]  ? kvasprintf+0x7f/0xd0
[  229.885563]  kobject_add+0x71/0xd0
[  229.885572]  ? device_private_init+0x23/0x70
[  229.885579]  device_add+0x12c/0x680
[  229.885597]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
[  229.885614]  hci_conn_complete_evt.isra.46+0xe3/0x430 [bluetooth]
[  229.885629]  hci_event_packet+0x12ee/0x2c70 [bluetooth]
[  229.885638]  ? pick_next_task_fair+0x162/0x560
[  229.885651]  hci_rx_work+0x19f/0x3b0 [bluetooth]
[  229.885661]  ? hci_rx_work+0x19f/0x3b0 [bluetooth]
[  229.885666]  ? __schedule+0x241/0x890
[  229.885673]  process_one_work+0x1de/0x430
[  229.885678]  worker_thread+0x48/0x400
[  229.885684]  kthread+0x125/0x140
[  229.885688]  ? process_one_work+0x430/0x430
[  229.885693]  ? kthread_create_on_node+0x70/0x70
[  229.885700]  ret_from_fork+0x25/0x30
[  229.885705] Code: 85 c0 48 89 c3 74 12 b9 00 10 00 00 48 89 c2 31 f6 4c 89 ef e8 5c c8 ff ff 4c 89 e2 48 89 de 48 c7 c7 a8 82 95 9e e8 bb 27 e3 ff <0f> ff 48 89 df e8 00 3c f5 ff 5b 41 5c 41 5d 5d c3 66 0f 1f 84 
[  229.885782] ---[ end trace c2b5939063e09541 ]---
[  229.885787] kobject_add_internal failed for hci0:256 with -EEXIST, don't try to register things with the same name in the same directory.
[  229.885803] ------------[ cut here ]------------
[  229.885809] WARNING: CPU: 0 PID: 355 at lib/kobject.c:240 kobject_add_internal+0x269/0x2b0
[  229.885810] Modules linked in: hidp cmac ccm rfcomm fuse uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core videodev media bnep btusb btrtl snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic arc4 joydev mousedev iTCO_wdt iTCO_vendor_support snd_soc_skl intel_rapl snd_soc_skl_ipc snd_soc_sst_ipc hid_multitouch x86_pkg_temp_thermal intel_powerclamp coretemp snd_soc_sst_dsp snd_hda_ext_core snd_soc_sst_match kvm_intel kvm irqbypass crct10dif_pclmul asus_nb_wmi crc32_pclmul asus_wmi sparse_keymap wmi_bmof ghash_clmulni_intel iwlmvm pcbc snd_soc_core mac80211 nls_iso8859_1 nls_cp437 i915 snd_compress vfat fat snd_pcm_dmaengine ac97_bus iwlwifi aesni_intel aes_x86_64 i2c_algo_bit drm_kms_helper crypto_simd glue_helper cryptd cfg80211 snd_hda_intel intel_cstate intel_rapl_perf
[  229.885882]  snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer snd evdev input_leds mac_hid pcspkr soundcore i2c_i801 shpchp drm intel_gtt idma64 agpgart mei_me syscopyarea sysfillrect sysimgblt fb_sys_fops mei processor_thermal_device intel_lpss_pci intel_pch_thermal intel_soc_dts_iosf thermal wmi i2c_hid hci_uart ac btbcm battery btqca btintel int3403_thermal int340x_thermal_zone bluetooth tpm_crb acpi_als tpm_tis tpm_tis_core kfifo_buf ecdh_generic pinctrl_sunrisepoint intel_lpss_acpi video rfkill pinctrl_intel intel_lpss industrialio tpm asus_wireless button int3400_thermal led_class acpi_pad acpi_thermal_rel sch_fq_codel crypto_user ip_tables x_tables ext4 crc16 mbcache jbd2 fscrypto hid_generic usbhid hid sd_mod serio_raw atkbd libps2 crc32c_intel ahci libahci xhci_pci libata xhci_hcd scsi_mod usbcore usb_common i8042 serio
[  229.885972] CPU: 0 PID: 355 Comm: kworker/u9:1 Tainted: G        W       4.13.12-1-ARCH #1
[  229.885974] Hardware name: ASUSTeK COMPUTER INC. UX330UAK/UX330UAK, BIOS UX330UAK.305 05/02/2017
[  229.885985] Workqueue: hci0 hci_rx_work [bluetooth]
[  229.885989] task: ffff957f92c46c80 task.stack: ffffae2f01530000
[  229.885993] RIP: 0010:kobject_add_internal+0x269/0x2b0
[  229.885995] RSP: 0018:ffffae2f01533bd0 EFLAGS: 00010286
[  229.885998] RAX: 000000000000007d RBX: ffff957f06214298 RCX: 0000000000000006
[  229.886000] RDX: 0000000000000000 RSI: 0000000000000082 RDI: ffff957f9ec0dc70
[  229.886002] RBP: ffffae2f01533c00 R08: 0000000000000386 R09: 0000000000000004
[  229.886004] R10: fffffa73c718f000 R11: 0000000000000001 R12: ffff957f942f2c50
[  229.886006] R13: 00000000ffffffef R14: ffff957f06214288 R15: ffff957f942f2c50
[  229.886009] FS:  0000000000000000(0000) GS:ffff957f9ec00000(0000) knlGS:0000000000000000
[  229.886011] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  229.886013] CR2: 000055eb45b86530 CR3: 000000002fa09000 CR4: 00000000003406f0
[  229.886014] Call Trace:
[  229.886020]  ? kvasprintf+0x7f/0xd0
[  229.886024]  kobject_add+0x71/0xd0
[  229.886031]  ? device_private_init+0x23/0x70
[  229.886036]  device_add+0x12c/0x680
[  229.886051]  hci_conn_add_sysfs+0x49/0xc0 [bluetooth]
[  229.886064]  hci_conn_complete_evt.isra.46+0xe3/0x430 [bluetooth]
[  229.886075]  hci_event_packet+0x12ee/0x2c70 [bluetooth]
[  229.886082]  ? pick_next_task_fair+0x162/0x560
[  229.886092]  hci_rx_work+0x19f/0x3b0 [bluetooth]
[  229.886102]  ? hci_rx_work+0x19f/0x3b0 [bluetooth]
[  229.886106]  ? __schedule+0x241/0x890
[  229.886110]  process_one_work+0x1de/0x430
[  229.886114]  worker_thread+0x48/0x400
[  229.886120]  kthread+0x125/0x140
[  229.886123]  ? process_one_work+0x430/0x430
[  229.886128]  ? kthread_create_on_node+0x70/0x70
[  229.886133]  ret_from_fork+0x25/0x30
[  229.886136] Code: 49 89 c4 48 85 ff 0f 84 44 fe ff ff 48 83 c7 18 e9 01 fe ff ff 48 8b 13 48 c7 c6 70 79 89 9e 48 c7 c7 48 2f 9a 9e e8 58 49 a8 ff <0f> ff e9 92 fe ff ff 0f ff eb a5 0f ff eb 98 41 bd fe ff ff ff 
[  229.886204] ---[ end trace c2b5939063e09542 ]---
[  229.886207] Bluetooth: Failed to register connection device
[  230.139753] input: FC:F1:52:FB:18:D9 as /devices/virtual/input/input21

Now for some sort of reason Blueman thinks that they are connected when they are really not...
https://lh3.googleusercontent.com/-t8tk … -09-36.png

Last edited by Hacksaurus_Babu (2017-11-16 01:11:58)

Offline

#12 2017-11-16 08:45:48

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

Please forget about the GUI frontends and stick to https://wiki.archlinux.org/index.php/Bl … uetoothctl for the moment.
When windows hibernates, hiberfil.sys contains a valid image (and not 0000 in its header) - this is detected on mounting attempts and warns you (as quoted) and mounts the disk ro.

The error is still the same (attempt to add a device that's considered present), try to disable wifi to rule out it impedes with BT on a physical layer.
Did you disable the "bt_coex_activ" parameter? ("systool -vm iwlwifi")

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#13 2017-11-16 23:53:12

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

I think this may be some Windows Bug because I am shutting down with that shutdown command as you said...

This is what systool -vim iwlwif gives me

Module = "iwlwifi"

  Attributes:
    coresize            = "217088"
    initsize            = "0"
    initstate           = "live"
    refcnt              = "1"
    taint               = ""
    uevent              = <store method only>

  Parameters:
    11n_disable         = "0"
    amsdu_size          = "0"
    antenna_coupling    = "0"
    bt_coex_active      = "Y"
    d0i3_disable        = "Y"
    d0i3_timeout        = "1000"
    disable_11ac        = "N"
    fw_monitor          = "N"
    fw_restart          = "Y"
    lar_disable         = "N"
    led_mode            = "0"
    nvm_file            = "(null)"
    power_level         = "0"
    power_save          = "N"
    swcrypto            = "0"
    uapsd_disable       = "3"

  Sections:
    .altinstr_replacement= "0xffffffffc0d4e04a"
    .altinstructions    = "0xffffffffc0d5c858"
    .bss                = "0xffffffffc0d60a80"
    .data.unlikely      = "0xffffffffc0d5f7bc"
    .data               = "0xffffffffc0d5d300"
    .exit.text          = "0xffffffffc0d4e03f"
    .gnu.linkonce.this_module= "0xffffffffc0d60740"
    .init.text          = "0xffffffffc0ae9000"
    .note.gnu.build-id  = "0xffffffffc0d4f000"
    .parainstructions   = "0xffffffffc0d5c9d0"
    .ref.data           = "0xffffffffc0d5f8a0"
    .rodata.str1.1      = "0xffffffffc0d57253"
    .rodata.str1.8      = "0xffffffffc0d58ae8"
    .rodata             = "0xffffffffc0d4f440"
    .smp_locks          = "0xffffffffc0d5c874"
    .strtab             = "0xffffffffc0af3d20"
    .symtab             = "0xffffffffc0aea000"
    .text               = "0xffffffffc0d30000"
    __bug_table         = "0xffffffffc0d5f078"
    __jump_table        = "0xffffffffc0d5d000"
    __kcrctab           = "0xffffffffc0d4f360"
    __kcrctab_gpl       = "0xffffffffc0d4f370"
    __ksymtab_gpl       = "0xffffffffc0d4f070"
    __ksymtab_strings   = "0xffffffffc0d5bb58"
    __ksymtab           = "0xffffffffc0d4f030"
    __mcount_loc        = "0xffffffffc0d5bf68"
    __param             = "0xffffffffc0d5c5d8"
    __tracepoints_ptrs  = "0xffffffffc0d5caf0"
    __tracepoints       = "0xffffffffc0d600e0"
    __tracepoints_strings= "0xffffffffc0d5cbc0"
    _ftrace_events      = "0xffffffffc0d5f7c8"

    bt_coex_active      = "Y"
It seems to be enabled

Offline

#14 2017-11-17 08:17:57

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

Is the partition that fails to mount read/write your windows system partition (maybe the hiberfil.sys is just spurious cruft on a disk that had a windows installation, but is currently not in use?)
Do you have a fast-boot setting in BIOS/UEFI? (Not the quick boot feature that skips memory tests etc.)

Yes, bt_coex_active is enabled, so dead end here as well :-(

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#15 2017-11-18 02:35:52

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

The way that I installed Arch may have affected this:
When I installed GRUB I mounted the Windows partition so that GRUB would detect it. Because GRUB was not able to detect it without it mounted for some sort of reason, but when I did mount it os-prober was able to detect it...
Do you think has something to do with this?
I will check my BIOS System...

EDIT:
Fastboot Option in BIOS is most definitely already disabled
https://s7.postimg.org/y9qj0yr97/image.png
(Just realized you cannot see the text, but it says "Fast Boot")

Last edited by Hacksaurus_Babu (2017-11-18 02:57:47)

Offline

#16 2017-11-18 14:38:27

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

A hibernating windows could very possibly cause this, some cruft hiberfil.sys file won't. Whether or not os-prober found your windows installation un/mounted should not matter.
I assume the lid will trigger some insane BT poweroff, the best workaround I can think of is some acpid event that catches the lid and takes down the bluetooth stack sanely (unregister, stop, unload kernel modules) - maybe even just rfkilling suffices.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#17 2017-11-18 18:34:33

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

Possibly, Right now for some sort of reason Bluetooth is working again, but I'm not willing to trust it.
I think this does have to do something Windows, because I haven't used Windows lately Bluetooth seems to be working again on Linux...

This is quite the issue, but the real question is, why is Windows hibernating?
Maybe one problem is that I have recovery partitions for Windows.
Maybe removing them might fix the problem?
https://lh3.googleusercontent.com/-a8Zi … -11-18.png

Offline

#18 2017-11-18 22:14:23

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

The affected partition is sda3, your windows system.
If you rename or remove hibefil.sys, windows should recreate it on demand.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#19 2017-11-19 00:27:15

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

https://www.techsupportall.com/hiberfil … indows-10/
Should I follow this article? And attempt to remove it?

Offline

#20 2017-11-19 08:03:46

seth
Member
Registered: 2012-09-03
Posts: 51,072

Re: [SOLVED] Bluetooth Fails on Lid Close

Not sure whether disabling hibernation will still remove the file but you can try, sure. (Though maybe take a copy of the file since we don't know whether the system is in some weird broken condition - you don't want to destroy it just to figure that windows won't boot without)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#21 2017-11-19 14:53:08

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

For the last couple of boots, bluetooth has been working perfectly for me...
I checked dmesg and I did dmesg | grep -i hib and this is what it found:

[    0.712778] PM: Hibernation image not present or could not be loaded.

I've been using the shutdown /s /f /t 0 command on Windows, so this may have solved something...

Offline

#22 2017-11-29 05:56:57

Hacksaurus_Babu
Member
Registered: 2017-01-21
Posts: 106

Re: [SOLVED] Bluetooth Fails on Lid Close

After a couple of days I've haven't been getting any bluetooth issues...
Marking as solved...

Offline

Pages: 1

Board footer

Powered by FluxBB