Stan,
Please file a separate bug so logs can be collected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notification
I am running into exactly the same problem as Bas Zoetekouw. I added the
enable_autosuspend=0 option:
stan@stan-desktop:~$ cat /etc/modprobe.d/btusb.conf
options btusb enable_autosuspend=0
But I see the following in dmesg after reboot:
[4.026743] btusb: unknown parameter 'enable_autosuspend
** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications about this bug go to:
https://bugs.la
Please test this patch.
** Patch added: "btusb-no-autosuspend.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/527/+files/btusb-no-autosuspend.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Emiliano,
That means it's a different issue. Please file a new bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage no
"enable_autosuspend=0" did not fix the issue for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications abou
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications about this bug go to:
https://bugs.l
Bas,
Please test this patch, thanks!
** Patch added: "0001-patch-for-LP-1790454.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5227688/+files/0001-patch-for-LP-1790454.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Yeah, "enable_autosuspend=0" by itself fixes the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications a
DH, I think this can workaround your issue:
[1] https://github.com/endlessm/linux/pull/424
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspe
Bas,
Does "enable_autosuspend=0" alone fix your issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications a
If the enable_autosuspend option doesn't fix your issue, I think you are
encountering a different bug (with overlapping symptoms). For clarity,
it might be best to open a separate bug report for your issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I am having a similar issue with Intel 8260. Wifi and BT works correctly
after cold boot. Wifi works correctly after suspend, but BT was showing
no adapters available in KDE plasma widget. dmesg would report "[
150.064149] Bluetooth: hci0: Failed to send firmware data (-38)" after
each resume.
My
I'm still planning to run a bisect to find the offending commit, but
havne't found the time yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after
Same issue here.
Adding this to options + cold boot seems to have fixed it.
% cat /etc/modprobe.d/btusb.conf
options btusb enable_autosuspend=0
~ % uname -r
4.18.19-041819-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Yes please.
Or even better, do a full kernel bisection between v4.15 and v4.17 to
make sure btusb.enable_autosuspend introduced the regression.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
T
I'm happy to report that everything seems stable now.
I'm now running the following config
- kernel 4.19.0-041900rc7-generic
- delay after reset set to 200ms (see #38)
- unload iwlwifi on suspend/sleep
- btusb.enable_autosuspend=0
Should I try with a regular kernel and only btusb.enable_auto
My bad, I didn't saw it works on 4.15 but fails since 4.17.
Before doing a kernel bisect, can you try if
"btusb.enable_autosuspend=0" helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Titl
Hmm, running the current setup (200ms sleep+iwlwifi unload-on-suspend),
I must say that the bt loading has become more reliable. It still
doesn't work 100% of the time, but it definitely is working more often
than before (maybe 75% of the time it works ok now).
--
You received this bug notificat
Also doesn't seem to make any difference...
Dmesg (attached) shows that iwlwifi is loading after initial btusb
initialization, but it still fails about 2/3 of the time.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5202421/+files/dme
Hmm, can you try removing iwlwifi before suspend, not sure if there's an
internal race happen inside the Intel wireless module.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth
I've changed the delay to 200ms, but now I get
[16936.380848] Bluetooth: hci0: Device boot timeout
in addition to the original symptons.
Dmesg is attached.
** Attachment added: "dmesg-200ms.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5201246/+files/dmesg-20
ok, will do
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications about this bug go to:
https://bugs.launchpad.
I've seen similar things recently, and seems like increase the delay
after reset can alleviate the issue.
Can you try something like 100ms or 200ms instead of (10 + 40)ms in [1]?
[1]
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/usb/core/hub.c#n2889
--
You rece
Sorry, bug is still occurring, even with the patch. Dmesg is attached.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5200246/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
Ok, running a patched kernel now. Let's see if I can still trigger the
bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To m
Is it possible for you to try this patch?
https://patchwork.kernel.org/patch/10624303/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/re
Problem still occurs. Dmesg is attached.
** Attachment added: "dmesg.4.19.0-041900rc7-generic+usbcore.quirks.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5199005/+files/dmesg.4.19.0-041900rc7-generic+usbcore.quirks.txt
--
You received this bug notification b
Ah yes, cold boot seems to fix it for now. I'll need to wait and see if
the bug now occurs during normal operation.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel)
Hmmm, do you still see this if you cold boot with the quirk?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notificati
** Attachment added: "dmesg-4.19rc7.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198639/+files/dmesg-4.19rc7.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790
With kernel 4.19rc7 and the kernel parameter as you prescribed, the BT adapter
won't work at all. The timeouts that would only occur sporadically after
resume, are now present from boot, and the previous
unload-modules/suspend/resume/load-modules cycle no longer works to get BT back
on.
Dme
Ok, please use v4.19-rc6 or rc7, and boot with kernel parameter
"usbcore.quirks=8087:0a2b:k" which disables LPM for the Bluetooth
device, and see if this issue still persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Sure, here it is.
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790454/+attachment/5198582/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Is it possible for you to attach full dmesg? i.e. everything from boot.
I'd like to check if LPM is enabled for this device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (b
Hmm, I guess the dmesg above was mispasted.
"modprobe -r btusb" gives
[ 6998.064598] usbcore: deregistering interface driver btusb
[ 6998.064608] usb usb1: usb auto-resume
[ 6998.064639] hub 1-0:1.0: hub_resume
[ 6998.064659] usb usb1-port2: status 0507 change
[ 6998.064674] usb usb1-port7:
The bug triggered again this morning:
> modprobe -r btusb
gives
[ 6998.064598] usbcore: deregistering interface driver btusb
[ 6998.064608] usb usb1: usb auto-resume
[ 6998.064639] hub 1-0:1.0: hub_resume
[ 6998.064659] usb usb1-port2: status 0507 change
[ 6998.064674] usb usb1-port7: statu
When the bug is triggered.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications about this bug go to:
https://
Do you need a dmesg when the bug is triggered, or does a regular boot
log suffice? It's hard to trigger the bug manually (but it occurs
every couple of days).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Can you attach full dmesg with `usbcore.dyndbg=+p`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790454
Title:
Bluetooth (btintel) stops working after suspend/resume
To manage notifications about
Adding to that, there is a (somewhat) reliable way to get bluetooth back. It
involves goign to the following process _twice_: stopping the bluetooth
service, unloading all relevant modules, suspending the laptop, resuming,
reloading all modules, starting the bluetooth service.
Rather cumbersome
41 matches
Mail list logo
