Bluetooth error on Raspi 4b+ when updating Twister OS

[raf401]

Anyone having same error when full-upgrading Twister OS?

Job for hciuart.service failed because the control process exited with error code.
See "systemctl status hciuart.service" and "journalctl -xe" for details.

I get it back when command systemctl restart hciuart.service but everytime I restart it, is the same story.

[pelwell]

Have you looked at the suggested details? What do they say?

[raf401]

Yeah.

journalctl -xe does not say anything about hciuart or any bluetooth adaptor. And bellow is hciuart service status.

hciuart.service - Configure Bluetooth Modems connected by UART
Loaded: loaded (/lib/systemd/system/hciuart.service; disabled; vendor preset:
Active: inactive (dead)
lines 1-3/3 (END)

I have seen many people having problem with it on different OS and also as I said I solve it temporarily when I command systemctl restart hciuart.service but service doesnt switch on when I restart raspi.

[bokkiedog]

I have a very similar issue on a pi 400 running latest stable buster. With me, though, restarting the service doesn't work. On boot, bluetooth shows no devices, and that error message in the log. When I try to restart the service, the restart times out and fails:

Aug 10 15:13:43 dinky bthelper[490]: Can't init device hci0: Invalid argument (22)
Aug 10 15:13:43 dinky systemd[1]: bthelper@hci0.service: Main process exited, code=exited, status=1/FAILURE
Aug 10 15:13:43 dinky systemd[1]: bthelper@hci0.service: Failed with result 'exit-code'.
Aug 10 15:13:43 dinky systemd[1]: Failed to start Raspberry Pi bluetooth helper.

Then, trying things manually:

root@dinky:/etc# /usr/bin/btuart
bcm43xx_init
Initialization timed out.

btuart correctly works out the hciattach commandline, which it runs thus:

root@dinky:/var/log# hciattach /dev/serial1 bcm43xx 3000000 flow -
bcm43xx_init
Initialization timed out.

Then, via strace, you can see it times out waiting here:

setitimer(ITIMER_REAL, {it_interval={tv_sec=0, tv_usec=0}, it_value={tv_sec=10, tv_usec=0}}, {it_interval={tv_sec=0, tv_usec=0}, it_value={tv_sec=0, tv_usec=0}}) = 0
openat(AT_FDCWD, "/dev/serial1", O_RDWR|O_NOCTTY) = 3
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, SNDCTL_TMR_START or TCSETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, TCGETS, {B115200 -opost -isig -icanon -echo ...}) = 0
ioctl(3, TCFLSH, TCIOFLUSH)             = 0
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}) = 0
brk(NULL)                               = 0x132d000
brk(0x134e000)                          = 0x134e000
write(1, "bcm43xx_init\n", 13bcm43xx_init
)          = 13
write(3, "\1\3\f\0", 4)                 = 4
read(3,0xbe955fcc, 1)                  = ? ERESTARTSYS (To be restarted if SA_RESTART is set)
--- SIGALRM {si_signo=SIGALRM, si_code=SI_KERNEL} ---

[Zelex]

This occurs when doing and apt-upgrade from a base buster install. Something wrong with that.

[Zelex]

bump

[pelwell]

It was discovered recently that attempting to restart Bluetooth as part of the update was failing because there is nothing to reset the BT modem hardware, which causes the firmware download to fail. At some point the pi-bluetooth package will be modified to not restart the services, but until then this error is to be expected and Bluetooth may have limited functionality until the next reboot.

If you are claiming that there are errors after the reboot then this report should be reworded.

[Zelex]

It happens after a reboot.