reset of full-speed USB device using ehci-pci kills Bluetooth
I am on Ubuntu 18.10
Since some weeks my Bluetooth mouse stops working. Each time when this happens I have this message in my logs:
[ 8555.431968] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
after that Bluetooth is dead and a "sudo service bluetooth restart" fails.
[ 9194.210589] Bluetooth: hci0: command 0x0c1a tx timeout
[ 9196.226580] Bluetooth: hci0: command 0x0406 tx timeout
[ 9199.458612] Bluetooth: hci0: command 0x0c03 tx timeout
[ 9207.682541] Bluetooth: hci0: HCI reset during shutdown failed
the only way to get Bluetooth back is reboot.
What can I do to get BT working reliable ?
usb bluetooth 18.10
asked Jan 29 at 14:55
AdrianAdrian
61
add a comment |
I am on Ubuntu 18.10
Since some weeks my Bluetooth mouse stops working. Each time when this happens I have this message in my logs:
[ 8555.431968] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
after that Bluetooth is dead and a "sudo service bluetooth restart" fails.
[ 9194.210589] Bluetooth: hci0: command 0x0c1a tx timeout
[ 9196.226580] Bluetooth: hci0: command 0x0406 tx timeout
[ 9199.458612] Bluetooth: hci0: command 0x0c03 tx timeout
[ 9207.682541] Bluetooth: hci0: HCI reset during shutdown failed
the only way to get Bluetooth back is reboot.
What can I do to get BT working reliable ?
usb bluetooth 18.10
asked Jan 29 at 14:55
AdrianAdrian
61
add a comment |
I am on Ubuntu 18.10
Since some weeks my Bluetooth mouse stops working. Each time when this happens I have this message in my logs:
[ 8555.431968] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
after that Bluetooth is dead and a "sudo service bluetooth restart" fails.
[ 9194.210589] Bluetooth: hci0: command 0x0c1a tx timeout
[ 9196.226580] Bluetooth: hci0: command 0x0406 tx timeout
[ 9199.458612] Bluetooth: hci0: command 0x0c03 tx timeout
[ 9207.682541] Bluetooth: hci0: HCI reset during shutdown failed
the only way to get Bluetooth back is reboot.
What can I do to get BT working reliable ?
usb bluetooth 18.10
asked Jan 29 at 14:55
AdrianAdrian
61
I am on Ubuntu 18.10
Since some weeks my Bluetooth mouse stops working. Each time when this happens I have this message in my logs:
[ 8555.431968] usb 1-1.3: reset full-speed USB device number 3 using ehci-pci
after that Bluetooth is dead and a "sudo service bluetooth restart" fails.
[ 9194.210589] Bluetooth: hci0: command 0x0c1a tx timeout
[ 9196.226580] Bluetooth: hci0: command 0x0406 tx timeout
[ 9199.458612] Bluetooth: hci0: command 0x0c03 tx timeout
[ 9207.682541] Bluetooth: hci0: HCI reset during shutdown failed
the only way to get Bluetooth back is reboot.
What can I do to get BT working reliable ?
usb bluetooth 18.10
usb bluetooth 18.10
asked Jan 29 at 14:55
AdrianAdrian
61
asked Jan 29 at 14:55
AdrianAdrian
61
asked Jan 29 at 14:55
AdrianAdrian
61
asked Jan 29 at 14:55
AdrianAdrian
61
asked Jan 29 at 14:55
AdrianAdrian
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This means there is some kind of issue with the underlying USB bus. I have seen this happen with USB cameras or mice that had damaged wires or internals. Essentially, something at a very low level is sending or receiving corrupted USB data, so as a last resort Linux resets the USB connection.
To complicate things further some systems implement their Bluetooth controllers are USB controllers, which is likely why its' affecting both.
For technical details see this Unix Exchange post.
It's possible that updating your PC firmware could resolve the issue. I would look at the available new versions of your BIOS from your manufacturer and see if they mention improvements in USB or Bluetooth stability. The process of upgrading the firmware/BIOS should involve putting a file onto a USB thumb drive and rebooting, but it depends on your system. There is also the fwupdate command in Ubuntu which can tell you if new firmware exists possibly for the Bluetooth device itself.
Assuming this keeps happening you can at the very least try reloading the kernel module associated with Bluetooth to avoid a complete reboot. You'll have to determine which module is being used for Bluetooth, you likely can get that from lsmod | grep blue, and then you can do the following to reload the module instead of rebooting:
sudo rmmod name_of_module
sudo modprobe name_of_module
If you get an error trying to rmmod you can try passing the -f option to "force" the removal of the module, although with anything in Linux once you start "forcing" something may be creating additional problems and your mileage may vary.
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameterbtusb.enable_autosuspend=nwhich I have added and until now it seems to work.
– Adrian
Feb 5 at 9:58
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113830%2freset-of-full-speed-usb-device-using-ehci-pci-kills-bluetooth%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This means there is some kind of issue with the underlying USB bus. I have seen this happen with USB cameras or mice that had damaged wires or internals. Essentially, something at a very low level is sending or receiving corrupted USB data, so as a last resort Linux resets the USB connection.
To complicate things further some systems implement their Bluetooth controllers are USB controllers, which is likely why its' affecting both.
For technical details see this Unix Exchange post.
It's possible that updating your PC firmware could resolve the issue. I would look at the available new versions of your BIOS from your manufacturer and see if they mention improvements in USB or Bluetooth stability. The process of upgrading the firmware/BIOS should involve putting a file onto a USB thumb drive and rebooting, but it depends on your system. There is also the fwupdate command in Ubuntu which can tell you if new firmware exists possibly for the Bluetooth device itself.
Assuming this keeps happening you can at the very least try reloading the kernel module associated with Bluetooth to avoid a complete reboot. You'll have to determine which module is being used for Bluetooth, you likely can get that from lsmod | grep blue, and then you can do the following to reload the module instead of rebooting:
sudo rmmod name_of_module
sudo modprobe name_of_module
If you get an error trying to rmmod you can try passing the -f option to "force" the removal of the module, although with anything in Linux once you start "forcing" something may be creating additional problems and your mileage may vary.
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameterbtusb.enable_autosuspend=nwhich I have added and until now it seems to work.
– Adrian
Feb 5 at 9:58
add a comment |
This means there is some kind of issue with the underlying USB bus. I have seen this happen with USB cameras or mice that had damaged wires or internals. Essentially, something at a very low level is sending or receiving corrupted USB data, so as a last resort Linux resets the USB connection.
To complicate things further some systems implement their Bluetooth controllers are USB controllers, which is likely why its' affecting both.
For technical details see this Unix Exchange post.
It's possible that updating your PC firmware could resolve the issue. I would look at the available new versions of your BIOS from your manufacturer and see if they mention improvements in USB or Bluetooth stability. The process of upgrading the firmware/BIOS should involve putting a file onto a USB thumb drive and rebooting, but it depends on your system. There is also the fwupdate command in Ubuntu which can tell you if new firmware exists possibly for the Bluetooth device itself.
Assuming this keeps happening you can at the very least try reloading the kernel module associated with Bluetooth to avoid a complete reboot. You'll have to determine which module is being used for Bluetooth, you likely can get that from lsmod | grep blue, and then you can do the following to reload the module instead of rebooting:
sudo rmmod name_of_module
sudo modprobe name_of_module
If you get an error trying to rmmod you can try passing the -f option to "force" the removal of the module, although with anything in Linux once you start "forcing" something may be creating additional problems and your mileage may vary.
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameterbtusb.enable_autosuspend=nwhich I have added and until now it seems to work.
– Adrian
Feb 5 at 9:58
add a comment |
This means there is some kind of issue with the underlying USB bus. I have seen this happen with USB cameras or mice that had damaged wires or internals. Essentially, something at a very low level is sending or receiving corrupted USB data, so as a last resort Linux resets the USB connection.
To complicate things further some systems implement their Bluetooth controllers are USB controllers, which is likely why its' affecting both.
For technical details see this Unix Exchange post.
It's possible that updating your PC firmware could resolve the issue. I would look at the available new versions of your BIOS from your manufacturer and see if they mention improvements in USB or Bluetooth stability. The process of upgrading the firmware/BIOS should involve putting a file onto a USB thumb drive and rebooting, but it depends on your system. There is also the fwupdate command in Ubuntu which can tell you if new firmware exists possibly for the Bluetooth device itself.
Assuming this keeps happening you can at the very least try reloading the kernel module associated with Bluetooth to avoid a complete reboot. You'll have to determine which module is being used for Bluetooth, you likely can get that from lsmod | grep blue, and then you can do the following to reload the module instead of rebooting:
sudo rmmod name_of_module
sudo modprobe name_of_module
If you get an error trying to rmmod you can try passing the -f option to "force" the removal of the module, although with anything in Linux once you start "forcing" something may be creating additional problems and your mileage may vary.
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
This means there is some kind of issue with the underlying USB bus. I have seen this happen with USB cameras or mice that had damaged wires or internals. Essentially, something at a very low level is sending or receiving corrupted USB data, so as a last resort Linux resets the USB connection.
To complicate things further some systems implement their Bluetooth controllers are USB controllers, which is likely why its' affecting both.
For technical details see this Unix Exchange post.
It's possible that updating your PC firmware could resolve the issue. I would look at the available new versions of your BIOS from your manufacturer and see if they mention improvements in USB or Bluetooth stability. The process of upgrading the firmware/BIOS should involve putting a file onto a USB thumb drive and rebooting, but it depends on your system. There is also the fwupdate command in Ubuntu which can tell you if new firmware exists possibly for the Bluetooth device itself.
Assuming this keeps happening you can at the very least try reloading the kernel module associated with Bluetooth to avoid a complete reboot. You'll have to determine which module is being used for Bluetooth, you likely can get that from lsmod | grep blue, and then you can do the following to reload the module instead of rebooting:
sudo rmmod name_of_module
sudo modprobe name_of_module
If you get an error trying to rmmod you can try passing the -f option to "force" the removal of the module, although with anything in Linux once you start "forcing" something may be creating additional problems and your mileage may vary.
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
answered Jan 29 at 15:11
Kristopher IvesKristopher Ives
2,87211525
2,87211525
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameterbtusb.enable_autosuspend=nwhich I have added and until now it seems to work.
– Adrian
Feb 5 at 9:58
add a comment |
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameterbtusb.enable_autosuspend=nwhich I have added and until now it seems to work.
– Adrian
Feb 5 at 9:58
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameter
btusb.enable_autosuspend=n which I have added and until now it seems to work.– Adrian
Feb 5 at 9:58
fwupdate is not supported on my machine. I also believe that the USB bus is the source of the problem. Looking around I found the following kernel parameter
btusb.enable_autosuspend=n which I have added and until now it seems to work.– Adrian
Feb 5 at 9:58
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1113830%2freset-of-full-speed-usb-device-using-ehci-pci-kills-bluetooth%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
