Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Raspberry Pi Bluetooth Crashing #940

Closed
Veldkornet opened this issue Oct 27, 2020 · 10 comments
Closed

Raspberry Pi Bluetooth Crashing #940

Veldkornet opened this issue Oct 27, 2020 · 10 comments
Labels
board/raspberrypi Raspberry Pi Boards REL-4

Comments

@Veldkornet
Copy link

Veldkornet commented Oct 27, 2020 •
edited

HassOS release with the issue:

RaspberryPi 4 (4GB) 64-bit:

Item Value
arch aarch64
chassis embedded
dev false
docker true
docker_version 19.03.11
hassio true
host_os HassOS 4.15
installation_type Home Assistant OS
os_name Linux
os_version 4.19.127-v8
python_version 3.8.5
supervisor 249
timezone Europe/Amsterdam
version 0.116.4
virtualen false

Description of problem:
It seems that after a period of time of usage, the Bluetooth becomes unstable and crashes. This is noticable when using the room-assistant add-on.

10/25/2020, 11:23:39 AM - error - BluetoothClassicService: Command failed: hcitool -i hci0 cc "64:a2:f9:f1:b8:7b" && hcitool -i hci0 rssi "64:a2:f9:f1:b8:7b"
Invalid device: Network is down
10/25/2020, 11:23:45 AM - error - BluetoothClassicService: Command failed: hcitool -i hci0 cc "88:63:DF:8A:1B:DC" && hcitool -i hci0 rssi "88:63:DF:8A:1B:DC"
Invalid device: Network is down

Rebooting the host resolves the problem temporarily.
See also mKeRix/room-assistant#314
@agners
Copy link
Member

agners commented Oct 27, 2020

What environment is that exactly? can you fill out the sections please?

@Veldkornet
Copy link
Author

Updated version info

@Veldkornet
Copy link
Author

Veldkornet commented Oct 27, 2020 •
edited

I initially thought that it was just the Bluetooth Crashing, but it seems that all my USB dongles also stop working when the bluetooth crashes. Since this never happened before, and me using the bluetooth is new, I'm assuming that the use of the bluetooth is causing everything to crash.

See below from the OpenZWave add-on

[20201027 12:42:11.569 CET] [ozw.library] [info]: Info - Node: 0   Opening controller /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:11.569 CET] [ozw.library] [info]: Info - Node: 0 Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1) 
[20201027 12:42:11.570 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Cannot open serial port /dev/serial/by-id/usb-0658_0200-if00. Error code 2 
[20201027 12:42:11.570 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Failed to open serial port /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:11.570 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Failed to init the controller (attempt 1) 
[20201027 12:42:16.571 CET] [ozw.library] [info]: Info - Node: 0   Opening controller /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:16.571 CET] [ozw.library] [info]: Info - Node: 0 Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1) 
[20201027 12:42:16.572 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Cannot open serial port /dev/serial/by-id/usb-0658_0200-if00. Error code 2 
[20201027 12:42:16.572 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Failed to open serial port /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:16.572 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Failed to init the controller (attempt 2) 
[20201027 12:42:21.573 CET] [ozw.library] [info]: Info - Node: 0   Opening controller /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:21.574 CET] [ozw.library] [info]: Info - Node: 0 Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1) 
[20201027 12:42:21.574 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Cannot open serial port /dev/serial/by-id/usb-0658_0200-if00. Error code 2 
[20201027 12:42:21.574 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Failed to open serial port /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:21.575 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Failed to init the controller (attempt 3) 
[20201027 12:42:26.576 CET] [ozw.library] [info]: Info - Node: 0   Opening controller /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:26.576 CET] [ozw.library] [info]: Info - Node: 0 Trying to open serial port /dev/serial/by-id/usb-0658_0200-if00 (attempt 1) 
[20201027 12:42:26.577 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Cannot open serial port /dev/serial/by-id/usb-0658_0200-if00. Error code 2 
[20201027 12:42:26.578 CET] [ozw.library] [critical]: Error - Node: 0 ERROR: Failed to open serial port /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:26.578 CET] [ozw.library] [warning]: Warning - Node: 0 WARNING: Failed to init the controller (attempt 4) 
[20201027 12:42:26.578 CET] [ozw.library] [debug]: Detail - Node: 255 Notification: DriverFailed: /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:26.579 CET] [ozw.notifications] [debug]: Notification pvt_driverFailed  0 Thread:  0x7f84e2ee38 
[20201027 12:42:26.579 CET] [ozw.mqtt.publisher] [debug]: Publishing Event stopped 
[20201027 12:42:26.579 CET] [ozw.mqtt.publisher] [debug]: Publishing Event driverFailed: 0 
[20201027 12:42:26.580 CET] [ozw.mqtt.publisher] [warning]: Exiting on Failure 
[20201027 12:42:26.580 CET] [ozw.library] [info]: Info - Node: 0 mgr,     Failed to remove driver for controller /dev/serial/by-id/usb-0658_0200-if00 
[20201027 12:42:26.580 CET] [ozw.manager] [warning]: Couldn't Remove Driver for  "/dev/serial/by-id/usb-0658_0200-if00" 
[20201027 12:42:26.580 CET] [ozw.manager] [debug]: OZW Serial Port Closed 
[20201027 12:42:26.580 CET] [ozw.daemon] [info]: Shutting Down  "ozwdaemon"  Version:  "0.1.0" 
[20201027 12:42:26.580 CET] [ozw.daemon] [info]: OpenZWave Version:  "1.6.1210" 
[20201027 12:42:26.580 CET] [ozw.daemon] [info]: QT-OpenZWave Version:  "1.2.0" 
[20201027 12:42:26.580 CET] [ozw.daemon] [info]: QT Version:  5.12.5 
1603798946: Socket error on client qt-openzwave-1, disconnecting.
In exit
[cont-finish.d] executing container finish scripts...
[cont-finish.d] mqtt.sh: executing... 
1603798946: mosquitto version 1.6.8 terminating
1603798946: Saving in-memory database to /data/mosquitto.db.
[12:42:27] INFO: Ensure upstream MQTT server has the correct OZW status

@agners
Copy link
Member

agners commented Oct 27, 2020

Hm, can you check kernel messages using dmesg?

@Veldkornet
Copy link
Author

Veldkornet commented Oct 27, 2020 •
edited

Hmm, currently all I get is the below:

[ 6989.705735] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 6989.705773] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[ 7208.114252] Bluetooth: hci0: command tx timeout
[ 7305.708295] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 7305.708329] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled

@Veldkornet
Copy link
Author

FYI, I discovered that I can get it working again by issuing the following command:

bluetoothctl power on

@Veldkornet
Copy link
Author

Veldkornet commented Oct 28, 2020 •
edited

Additionally, I discovered the following in the dmesg when the bluetooth and USB dongles all crashed. Surprisingly I could get the bluetooth up and running again with the command form above, but for the USB dongels I needed to reboot the Pi. So it's not clear to me if the one is breaking the other, or that they are both just victims of another issue...

[72135.058131] Unable to handle kernel paging request at virtual address 0000000139677138
[72135.058133] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000001
[72135.058138] Mem abort info:
[72135.058152] Mem abort info:
[72135.058162]   ESR = 0x96000006
[72135.058167]   ESR = 0x96000005
[72135.058172]   Exception class = DABT (current EL), IL = 32 bits
[72135.058177]   Exception class = DABT (current EL), IL = 32 bits
[72135.058181]   SET = 0, FnV = 0
[72135.058187]   SET = 0, FnV = 0
[72135.058193]   EA = 0, S1PTW = 0
[72135.058198]   EA = 0, S1PTW = 0
[72135.058202] Data abort info:
[72135.058207] Data abort info:
[72135.058212]   ISV = 0, ISS = 0x00000006
[72135.058216]   ISV = 0, ISS = 0x00000005
[72135.058220]   CM = 0, WnR = 0
[72135.058225]   CM = 0, WnR = 0
[72135.058232] user pgtable: 4k pages, 39-bit VAs, pgdp = 000000002f208dd7
[72135.058239] user pgtable: 4k pages, 39-bit VAs, pgdp = 00000000ffc755c1
[72135.058244] [0000000000000001] pgd=00000000eff87003, pud=00000000eff87003, pmd=0000000000000000
[72135.058252] [0000000139677138] pgd=0000000000000000, pud=0000000000000000
[72135.058261] Internal error: Oops: 96000006 [#1] PREEMPT SMP
[72135.058272] Modules linked in: wireguard rfcomm nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm serdev bluetooth ecdh_generic ftdi_sio cdc_acm sch_fq_codel brcmfmac brcmutil cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) snd_bcm2835(C) v4l2_mem2mem rfkill snd_pcm bcm2835_mmal_vchiq(C) videobuf2_vmalloc raspberrypi_hwmon snd_timer videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 hwmon snd videobuf2_common vc_sm_cma(C) rpivid_mem uio_pdrv_genirq uio
[72135.058344] Process kworker/0:2 (pid: 612004, stack limit = 0x0000000051bd933a)
[72135.058355] CPU: 0 PID: 612004 Comm: kworker/0:2 Tainted: G         C        4.19.127-v8 #1
[72135.058364] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[72135.058382] Workqueue: events acm_softint [cdc_acm]
[72135.058391] pstate: 80000005 (Nzcv daif -PAN -UAO)
[72135.058404] pc : __pi_strcmp+0x88/0x154
[72135.058414] lr : dev_vprintk_emit+0xb0/0x220
[72135.058421] sp : ffffff8009313a80
[72135.058426] x29: ffffff8009313a80 x28: ffffff8009313b29 
[72135.058435] x27: 000000000c27d000 x26: 000000000000006f 
[72135.058443] x25: 0000000000000001 x24: ffffff8008c89e18 
[72135.058451] x23: 0000000000000003 x22: ffffff8008e49f08 
[72135.058459] x21: ffffff8009313bd0 x20: ffffffc0f5fda060 
[72135.058466] x19: 0000000000000011 x18: 0000000000000000 
[72135.058474] x17: ffffffc0f16b0000 x16: ffffffc0f16b2000 
[72135.058481] x15: 0000000000000204 x14: 0000000000000424 
[72135.058489] x13: 0000000000000000 x12: 0000000000000000 
[72135.058496] x11: 0000000000000008 x10: 0101010101010101 
[72135.058504] x9 : ffffffffffffffff x8 : 0000000000000008 
[72135.058512] x7 : 0000000000000007 x6 : 0000000000000006 
[72135.058519] x5 : 0000000000000000 x4 : 00000000000000c2 
[72135.058527] x3 : ffff0a00ffffff04 x2 : f6cd6eee86c30900 
[72135.058535] x1 : ffffff8008c5b988 x0 : 0000000000000001 
[72135.058543] Call trace:
[72135.058550]  __pi_strcmp+0x88/0x154
[72135.058557]  dev_printk_emit+0x80/0xb0
[72135.058565]  __dev_printk+0x5c/0xa0
[72135.058572]  _dev_err+0x78/0xa0
[72135.058580]  acm_submit_read_urb+0xec/0x100 [cdc_acm]
[72135.058589]  acm_softint+0x124/0x190 [cdc_acm]
[72135.058599]  process_one_work+0x1c0/0x430
[72135.058606]  worker_thread+0x50/0x410
[72135.058614]  kthread+0x104/0x130
[72135.058622]  ret_from_fork+0x10/0x1c
[72135.058630] Code: cb0803e8 91002108 eb0800e9 9a8880eb (38401402) 
[72135.058640] ---[ end trace 683d7b34479b3563 ]---
[72135.058648] Internal error: Oops: 96000005 [#2] PREEMPT SMP
[72135.058655] Modules linked in: wireguard rfcomm nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm serdev bluetooth ecdh_generic ftdi_sio cdc_acm sch_fq_codel brcmfmac brcmutil cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) snd_bcm2835(C) v4l2_mem2mem rfkill snd_pcm bcm2835_mmal_vchiq(C) videobuf2_vmalloc raspberrypi_hwmon snd_timer videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 hwmon snd videobuf2_common vc_sm_cma(C) rpivid_mem uio_pdrv_genirq uio
[72135.058716] Process kworker/3:0 (pid: 621443, stack limit = 0x0000000004e6c70c)
[72135.058727] CPU: 3 PID: 621443 Comm: kworker/3:0 Tainted: G      D  C        4.19.127-v8 #1
[72135.058735] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[72135.058747] Workqueue: events acm_softint [cdc_acm]
[72135.058757] pstate: 00000005 (nzcv daif -PAN -UAO)
[72135.058771] pc : usb_submit_urb+0x24/0x520
[72135.058780] lr : acm_submit_read_urb+0xac/0x100 [cdc_acm]
[72135.058787] sp : ffffff8015fabcc0
[72135.058793] x29: ffffff8015fabcc0 x28: ffffff8008e46000 
[72135.058802] x27: 0000000000000000 x26: ffffff8012953cd8 
[72135.058810] x25: 0000000000000001 x24: 0000000000600000 
[72135.058818] x23: ffffffc0ef65c448 x22: ffffffc0ef65c020 
[72135.058826] x21: 0000000000600000 x20: 000000000000000e 
[72135.058833] x19: 0000000139677080 x18: 0000000000000000 
[72135.058841] x17: ffffffc0f5320800 x16: ffffffc0f5324800 
[72135.058849] x15: 0000000000000204 x14: 0000000000000425 
[72135.058856] x13: 0000000000000000 x12: 0000000000000000 
[72135.058864] x11: 0000000000000425 x10: 0000000000001940 
[72135.058872] x9 : 0000000000000000 x8 : 0000000000008980 
[72135.058880] x7 : 0000000000000080 x6 : ffffff8008e4a000 
[72135.058887] x5 : 0000000000000000 x4 : 0000000000000001 
[72135.058895] x3 : ffffff8008e4a680 x2 : 0000000000000000 
[72135.058903] x1 : 0000000000600000 x0 : ffffff800102131c 
[72135.058911] Call trace:
[72135.058918]  usb_submit_urb+0x24/0x520
[72135.058927]  acm_submit_read_urb+0xac/0x100 [cdc_acm]
[72135.058936]  acm_softint+0x124/0x190 [cdc_acm]
[72135.058945]  process_one_work+0x1c0/0x430
[72135.058953]  worker_thread+0x50/0x410
[72135.058960]  kthread+0x104/0x130
[72135.058968]  ret_from_fork+0x10/0x1c
[72135.058976] Code: aa1e03e0 2a0103f5 d503201f b4001cb3 (f9405e60) 
[72135.058985] ---[ end trace 683d7b34479b3564 ]---
[72141.270279] usb 1-1.4.1: USB disconnect, device number 4
[72143.470014] ------------[ cut here ]------------
[72143.470058] WARNING: CPU: 0 PID: 9485 at kernel/workqueue.c:1444 __queue_work+0x508/0x520
[72143.470068] Modules linked in: wireguard rfcomm nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 algif_skcipher af_alg bnep hci_uart btbcm serdev bluetooth ecdh_generic ftdi_sio cdc_acm sch_fq_codel brcmfmac brcmutil cfg80211 bcm2835_codec(C) bcm2835_v4l2(C) snd_bcm2835(C) v4l2_mem2mem rfkill snd_pcm bcm2835_mmal_vchiq(C) videobuf2_vmalloc raspberrypi_hwmon snd_timer videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 hwmon snd videobuf2_common vc_sm_cma(C) rpivid_mem uio_pdrv_genirq uio
[72143.470144] CPU: 0 PID: 9485 Comm: OZW-driver Tainted: G      D  C        4.19.127-v8 #1
[72143.470153] Hardware name: Raspberry Pi 4 Model B Rev 1.1 (DT)
[72143.470162] pstate: 40000085 (nZcv daIf -PAN -UAO)
[72143.470171] pc : __queue_work+0x508/0x520
[72143.470179] lr : __queue_work+0x508/0x520
[72143.470185] sp : ffffff8008003a20
[72143.470190] x29: ffffff8008003a20 x28: ffffffc0fbf6ccc0 
[72143.470199] x27: ffffff8008e2d018 x26: ffffff8008e4ac78 
[72143.470207] x25: ffffff8008e2d018 x24: 0000000000000040 
[72143.470215] x23: 000000000000001f x22: 0000000000000000 
[72143.470223] x21: ffffffc0f700c800 x20: ffffffc0ef65c790 
[72143.470230] x19: ffffffc0fbf70a00 x18: ffffffffffffffff 
[72143.470238] x17: 0000000000000000 x16: 0000000000000000 
[72143.470245] x15: ffffff8088f687a7 x14: 0720072007200720 
[72143.470253] x13: 0720072007200720 x12: 0720072007200720 
[72143.470260] x11: 0720072007200720 x10: 0720072007200720 
[72143.470268] x9 : 0720072007200720 x8 : 0720072007200720 
[72143.470276] x7 : 0000000000000066 x6 : 00000040f3133000 
[72143.470283] x5 : 0000000000010003 x4 : ffffffc0fbf620a0 
[72143.470291] x3 : ffffff8008e2d018 x2 : f6cd6eee86c30900 
[72143.470298] x1 : 0000000000000000 x0 : 0000000000000024 
[72143.470306] Call trace:
[72143.470314]  __queue_work+0x508/0x520
[72143.470322]  queue_work_on+0xb8/0xc0
[72143.470335]  acm_write_bulk+0x78/0x90 [cdc_acm]
[72143.470346]  __usb_hcd_giveback_urb+0x90/0x130
[72143.470353]  usb_hcd_giveback_urb+0x150/0x160
[72143.470362]  xhci_giveback_urb_in_irq.isra.0+0x8c/0x160
[72143.470370]  xhci_td_cleanup+0xdc/0x130
[72143.470378]  finish_td+0xfc/0x130
[72143.470385]  xhci_irq+0x860/0x1ab0
[72143.470392]  xhci_msi_irq+0x20/0x30
[72143.470400]  __handle_irq_event_percpu+0x78/0x2b0
[72143.470408]  handle_irq_event_percpu+0x40/0xa0
[72143.470415]  handle_irq_event+0x50/0x80
[72143.470423]  handle_simple_irq+0xc4/0x100
[72143.470430]  generic_handle_irq+0x34/0x50
[72143.470440]  brcm_pcie_msi_isr+0xb0/0x1b0
[72143.470448]  generic_handle_irq+0x34/0x50
[72143.470455]  __handle_domain_irq+0x98/0x110
[72143.470462]  gic_handle_irq+0x58/0xb0
[72143.470469]  el0_irq_naked+0x50/0x5c
[72143.470475] ---[ end trace 683d7b34479b3565 ]---

AND

[78888.068025] ftdi_sio ttyUSB0: failed to get modem status: -71
[78888.068497] ftdi_sio ttyUSB0: error from flowcontrol urb
[78888.072631] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity
[78888.073133] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate
[78888.073622] ftdi_sio ttyUSB0: failed to set flow control: -71
[78888.080910] ftdi_sio ttyUSB0: failed to set flow control: -71
[78888.192974] cdc_acm 1-1.4.3:1.0: failed to set dtr/rts
[78897.885365] ftdi_sio ttyUSB0: failed to get modem status: -71
[78897.885945] ftdi_sio ttyUSB0: error from flowcontrol urb
[78921.318248] udevd[190]: starting version 3.2.9
[78921.355004] udevd[191]: starting eudev-3.2.9
[78983.052316] udevd[530]: worker [2675] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 is taking a long time
[78983.055293] udevd[191]: worker [196] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 is taking a long time
[78983.055528] udevd[207]: worker [5692] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 is taking a long time
[79041.540720] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[79041.540756] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[79103.400388] udevd[207]: worker [5692] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 timeout; kill it
[79103.400442] udevd[207]: seq 8298 '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4' killed
[79103.403491] udevd[207]: worker [5692] terminated by signal 9 (Killed)
[79103.403530] udevd[207]: worker [5692] failed while handling '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4'
[79103.404977] udevd[530]: worker [2675] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 timeout; kill it
[79103.405094] udevd[530]: seq 8298 '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4' killed
[79103.406603] udevd[191]: worker [196] /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4 timeout; kill it
[79103.406665] udevd[191]: seq 8298 '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4' killed
[79103.407185] udevd[530]: worker [2675] terminated by signal 9 (Killed)
[79103.407212] udevd[530]: worker [2675] failed while handling '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4'
[79103.408291] udevd[191]: worker [196] terminated by signal 9 (Killed)
[79103.408328] udevd[191]: worker [196] failed while handling '/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4'
[79104.309143] cdc_acm 1-1.4.3:1.1: urb 3 failed submission with -22
[79125.222482] cdc_acm 1-1.4.3:1.1: urb 3 failed submission with -22
[79167.466752] cdc_acm 1-1.4.3:1.1: urb 3 failed submission with -22
[79250.228134] cdc_acm 1-1.4.3:1.1: urb 3 failed submission with -22
[79333.030947] cdc_acm 1-1.4.3:1.1: urb 3 failed submission with -22

@agners
Copy link
Member

agners commented Oct 28, 2020

Ugh, this looks like quite some USB issues. Hard to tell what is going on, from bad cables, bad USB device to power issues pretty much everything is possible. I suggest to remove one device and see if it makes bluetooth stable again (and dmesg not showing such errors)....

@agners agners added board/raspberrypi Raspberry Pi Boards REL-4 labels Nov 2, 2020
@mKeRix mKeRix mentioned this issue Nov 2, 2020
Closed
agners added a commit to agners/operating-system that referenced this issue Nov 5, 2020
@agners
Fix CDC ACM error recovery in Raspberry Pi kernels as well (home-assi…
63b4587 
…stant#940)

Backport fixes for CDC ACM error recovery path.
agners added a commit to agners/operating-system that referenced this issue Nov 5, 2020
@agners
Fix CDC ACM error recovery in Raspberry Pi kernels as well (home-assi…
4348624 
…stant#940)

Backport fixes for CDC ACM error recovery path.
pvizeli pushed a commit that referenced this issue Nov 6, 2020
@agners
Fix CDC ACM error recovery in Raspberry Pi kernels as well (#940) (#962)
f9c29ef 
Backport fixes for CDC ACM error recovery path.
@agners
Copy link
Member

agners commented Nov 6, 2020

CDC ACM crash is addressed in the upcoming 4.16 release.

@agners agners closed this as completed Nov 6, 2020
@Veldkornet
Copy link
Author

@agners was this specific to the RaspberryPi? I switched over to am Intel NUC, but the Bluetooth still dies on me every so often.

@samsam-rolon samsam-rolon mentioned this issue Apr 20, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
board/raspberrypi Raspberry Pi Boards REL-4
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@agners @Veldkornet