farleysmaster
Posts: 7
Joined: Thu Sep 13, 2018 5:58 pm

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Sat Sep 15, 2018 7:14 am

HawaiianPi wrote:
Fri Sep 14, 2018 8:28 pm
LTolledo wrote:
Fri Sep 14, 2018 7:16 pm
then issued reboot command....

it booted...
The problem is with shutdown, not reboot.
I'm pretty sure I had problems with both.

RonR
Posts: 644
Joined: Tue Apr 12, 2016 10:29 pm
Location: US

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Sun Sep 16, 2018 1:18 am

Add me to the list of those experiencing the problem. Reverting to the earlier firmware + kernel appears to be a work-around for the moment:

Code: Select all

rpi-update 911147a3276beee09afc4237e1b7b964e61fb88a

LTolledo
Posts: 2165
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Sun Sep 16, 2018 1:39 pm

2 of my systems (including this RPi3B+) has finally caught the bug..... applying known cure at the moment....
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

User avatar
dckornbluh
Posts: 20
Joined: Fri Mar 03, 2017 9:31 pm
Location: Seattle, WA

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Mon Sep 17, 2018 10:45 pm

Is there an update on this issue? I'm able to reproduce the problem consistently:

Raspian GNU/Linux 9 (stretch), Kernel Linux 4.14.69-v7+ on RPI 3+ with Bluetooth off hangs on shutdown every time.

Shutdown and reboot work if Bluetooth is on. I can't ship my product with Bluetooth on.

User avatar
DougieLawson
Posts: 36578
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Mon Sep 17, 2018 11:06 pm

dckornbluh wrote:
Mon Sep 17, 2018 10:45 pm
Is there an update on this issue? I'm able to reproduce the problem consistently:
Looks like it's fixed in 4.14.70+ & 4.14.70-v7+
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

fufu65
Posts: 3
Joined: Wed Sep 12, 2018 7:51 am

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Tue Sep 18, 2018 8:09 am

DougieLawson wrote:
Mon Sep 17, 2018 11:06 pm
dckornbluh wrote:
Mon Sep 17, 2018 10:45 pm
Is there an update on this issue? I'm able to reproduce the problem consistently:
Looks like it's fixed in 4.14.70+ & 4.14.70-v7+
Not for me; the problem is still present on my RPI3B+.

User avatar
HawaiianPi
Posts: 4887
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Tue Sep 18, 2018 8:39 am

+1

I tried the 4.14.70 kernel/firmware and shutdown still failed with a panic.

Pi 3B, RPF PSU, Raspbian Stretch Lite, Bluetooth off.

Code: Select all

[   88.309556] Code: e1a04000 e5900060 f57ff05b f590f000 (e1902f9f)
[   88.309561] ---[ end trace 5c4ce2e7c3c38f02 ]---
[   88.309565] Kernel panic - not syncing: Fatal exception in interrupt
Oddly, it doesn't happen every shutdown now. Sometimes it shuts down fine, others it panics. This is the clean Raspbian Lite install I did a day or two ago when I was first testing this.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

farleysmaster
Posts: 7
Joined: Thu Sep 13, 2018 5:58 pm

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Tue Sep 18, 2018 1:56 pm

Has the 'fix' been added as a raspbian update yet?

User avatar
HawaiianPi
Posts: 4887
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Tue Sep 18, 2018 11:07 pm

Forum member Herbaldew noticed there was a new commit with the same version number and said it fixed the problem. I just tried it on my Pi3B, Raspbian Lite, USB-SSD booted system, and I have successfully shutdown and rebooted multiple times without incident. So it may actually be fixed now.

Going to test it on a newly imaged micro SD card...

farleysmaster wrote:
Tue Sep 18, 2018 1:56 pm
Has the 'fix' been added as a raspbian update yet?
Only through rpi-update at the moment (apt-cache policy raspberrypi-kernel still shows buggy 20180910). Either wait for the fix to be thoroughly tested and moved to the stable branch, or use rpi-update to install the testing branch firmware (and hope no more bugs are lurking).
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

User avatar
HawaiianPi
Posts: 4887
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Wed Sep 19, 2018 12:44 am

Alright, I just tested it with a freshly imaged 32GB Samsung EVO+ micro SD card (and my SSD unplugged).

Raspberry Pi model 3B (not +)
Raspbian Lite 2018-06-27 (Bluetooth disabled and serial console output enabled)
Official RPF PSU
Headless, with only the PSU and serial console cable connected.

Immediately after imaging it will boot, reboot and shutdown fine.

Code: Select all

[email protected]:~$ cat /sys/firmware/devicetree/base/model;echo
Raspberry Pi 3 Model B Rev 1.2
[email protected]:~$ uname -r
4.14.50-v7+
[email protected]:~$ sudo shutdown now
[  OK  ] Started Show Plymouth Power Off Screen.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Deactivated swap /var/swap.
[  OK  ] Stopped LSB: Autogenerate and use a swap file.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target NFS client services.
[  OK  ] Stopped dhcpcd on all interfaces.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed triggerhappy.socket.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Stopped target System Initialization.
         Stopping Update UTMP about System Boot/Shutdown...
         Stopping Network Time Synchronization...
[  OK  ] Stopped target Swap.
         Stopping Restore / save the current clock...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped target Encrypted Volumes.
         Stopping Load/Save Random Seed...
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped Restore / save the current clock.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
         Unmounting /boot...
         Unmounting /run/user/1000...
[  OK  ] Unmounted /run/user/1000.
[  OK  ] Unmounted /boot.
[  OK  ] Stopped File System Check on /dev/disk/by-partuuid/3d9e8996-01.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Reached target Shutdown.
[   62.791404] reboot: Power down
Next, I updated with,

Code: Select all

sudo apt update && sudo apt full-upgrade -y
followed by a reboot.

Code: Select all

[email protected]:~$ uname -r
4.14.69-v7+
[email protected]:~$ sudo shutdown now
...
[   59.332879] ---[ end trace a916de937e07a704 ]---
[   59.332883] Kernel panic - not syncing: Fatal exception in interrupt
[   59.332895] CPU1: stopping
[   59.332900] CPU: 1 PID: 94 Comm: systemd-journal Tainted: G      D  C      4.14.69-v7+ #1141
[   59.332902] Hardware name: BCM2835
[   59.332913] [<8010ffd8>] (unwind_backtrace) from [<8010c240>] (show_stack+0x20/0x24)
[   59.332922] [<8010c240>] (show_stack) from [<807879e4>] (dump_stack+0xd4/0x118)
[   59.332930] [<807879e4>] (dump_stack) from [<8010e458>] (handle_IPI+0x2bc/0x33c)
[   59.332937] [<8010e458>] (handle_IPI) from [<801014d8>] (bcm2836_arm_irqchip_handle_irq+0x7c/0xac)
[   59.332945] [<801014d8>] (bcm2836_arm_irqchip_handle_irq) from [<807a357c>] (__irq_svc+0x5c/0x7c)
[   59.332947] Exception stack(0xb9211c68 to 0xb9211cb0)
[   59.332952] 1c60:                   00c43580 b93ee6a0 00000014 6d657473 454d0a64 47415353
[   59.332958] 1c80: 44495f45 3164393d 32616161 00000114 00000114 b9211d04 30366437 b9211cbc
[   59.332961] 1ca0: 62303431 80785eec 20000013 ffffffff
[   59.332968] [<807a357c>] (__irq_svc) from [<80785eec>] (memcpy+0x4c/0x330)
[   59.332977] [<80785eec>] (memcpy) from [<804a1dbc>] (__copy_to_user_memcpy+0x130/0x190)
[   59.332987] [<804a1dbc>] (__copy_to_user_memcpy) from [<804a20a4>] (arm_copy_to_user+0x20/0x2c)
[   59.332994] [<804a20a4>] (arm_copy_to_user) from [<804a7620>] (copyout+0x38/0x44)
[   59.333003] [<804a7620>] (copyout) from [<804a76c4>] (_copy_to_iter+0x98/0x480)
[   59.333013] [<804a76c4>] (_copy_to_iter) from [<8067fc58>] (skb_copy_datagram_iter+0x64/0x264)
[   59.333024] [<8067fc58>] (skb_copy_datagram_iter) from [<80747600>] (unix_dgram_recvmsg+0x198/0x450)
[   59.333033] [<80747600>] (unix_dgram_recvmsg) from [<8066d434>] (sock_recvmsg+0x28/0x2c)
[   59.333042] [<8066d434>] (sock_recvmsg) from [<8066f5a8>] (___sys_recvmsg+0xa0/0x128)
[   59.333051] [<8066f5a8>] (___sys_recvmsg) from [<80670470>] (__sys_recvmsg+0x4c/0x7c)
[   59.333059] [<80670470>] (__sys_recvmsg) from [<806704b8>] (SyS_recvmsg+0x18/0x1c)
[   59.333067] [<806704b8>] (SyS_recvmsg) from [<801081e0>] (__sys_trace_return+0x0/0x10)
[   59.333070] CPU3: stopping
[   59.333075] CPU: 3 PID: 591 Comm: systemd-cgroups Tainted: G      D  C      4.14.69-v7+ #1141
[   59.333077] Hardware name: BCM2835
[   59.333085] [<8010ffd8>] (unwind_backtrace) from [<8010c240>] (show_stack+0x20/0x24)
[   59.333091] [<8010c240>] (show_stack) from [<807879e4>] (dump_stack+0xd4/0x118)
[   59.333098] [<807879e4>] (dump_stack) from [<8010e458>] (handle_IPI+0x2bc/0x33c)
[   59.333104] [<8010e458>] (handle_IPI) from [<801014d8>] (bcm2836_arm_irqchip_handle_irq+0x7c/0xac)
[   59.333111] [<801014d8>] (bcm2836_arm_irqchip_handle_irq) from [<807a38cc>] (__irq_usr+0x4c/0x60)
[   59.333113] Exception stack(0xb6c57fb0 to 0xb6c57ff8)
[   59.333117] 7fa0:                                     001e9579 00000736 00000805 00000a66
[   59.333123] 7fc0: 76f62fd0 00000002 76f56488 f544ba93 00000000 00000000 00000001 00000014
[   59.333128] 7fe0: 76d8baac 7ead3a40 76f3e574 76f3e57c 20000010 ffffffff
[   59.333131] CPU0: stopping
[   59.333136] CPU: 0 PID: 595 Comm: (plymouth) Tainted: G      D  C      4.14.69-v7+ #1141
[   59.333138] Hardware name: BCM2835
[   59.333146] [<8010ffd8>] (unwind_backtrace) from [<8010c240>] (show_stack+0x20/0x24)
[   59.333152] [<8010c240>] (show_stack) from [<807879e4>] (dump_stack+0xd4/0x118)
[   59.333159] [<807879e4>] (dump_stack) from [<8010e458>] (handle_IPI+0x2bc/0x33c)
[   59.333165] [<8010e458>] (handle_IPI) from [<801014d8>] (bcm2836_arm_irqchip_handle_irq+0x7c/0xac)
[   59.333172] [<801014d8>] (bcm2836_arm_irqchip_handle_irq) from [<807a357c>] (__irq_svc+0x5c/0x7c)
[   59.333174] Exception stack(0xb917dce8 to 0xb917dd30)
[   59.333179] dce0:                   b904c010 00000000 00002240 00000000 b7a4db00 80cbfd38
[   59.333184] dd00: b7a4db00 b917dd48 80cc0b58 b7a4dba0 80cc0b58 b917dd94 80c04174 b917dd38
[   59.333188] dd20: 801ae700 801ae704 60000013 ffffffff
[   59.333197] [<807a357c>] (__irq_svc) from [<801ae704>] (find_css_set+0x1e8/0x5b4)
[   59.333206] [<801ae704>] (find_css_set) from [<801af488>] (cgroup_migrate_prepare_dst+0x48/0x1fc)
[   59.333213] [<801af488>] (cgroup_migrate_prepare_dst) from [<801b0004>] (cgroup_attach_task+0xf8/0x1dc)
[   59.333220] [<801b0004>] (cgroup_attach_task) from [<801b47fc>] (__cgroup1_procs_write+0x110/0x144)
[   59.333228] [<801b47fc>] (__cgroup1_procs_write) from [<801b4890>] (cgroup1_procs_write+0x2c/0x34)
[   59.333235] [<801b4890>] (cgroup1_procs_write) from [<801ad770>] (cgroup_file_write+0x9c/0x154)
[   59.333244] [<801ad770>] (cgroup_file_write) from [<803093e8>] (kernfs_fop_write+0xdc/0x1c0)
[   59.333253] [<803093e8>] (kernfs_fop_write) from [<8028b2c0>] (__vfs_write+0x38/0x138)
[   59.333263] [<8028b2c0>] (__vfs_write) from [<8028b588>] (vfs_write+0xb4/0x1bc)
[   59.333270] [<8028b588>] (vfs_write) from [<8028b7d8>] (SyS_write+0x54/0xb0)
[   59.333277] [<8028b7d8>] (SyS_write) from [<80108060>] (ret_fast_syscall+0x0/0x28)
[   60.300429] ---[ end Kernel panic - not syncing: Fatal exception in interrupt
Failed shutdown due to kernel panic.

Updated to latest testing branch firmware.

Code: Select all

[email protected]:~$ uname -r
4.14.69-v7+
[email protected]:~$ sudo rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13545  100 13545    0     0  25516      0 --:--:-- --:--:-- --:--:-- 25556
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** We're running for the first time
 *** Backing up files (this will take a few minutes)
 *** Backing up firmware
 *** Backing up modules 4.14.69-v7+
#############################################################
This update bumps to rpi-4.14.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=197689
##############################################################
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    527      0 --:--:-- --:--:-- --:--:--   529
100 56.0M  100 56.0M    0     0  2977k      0  0:00:19  0:00:19 --:--:-- 3230k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.14.70-v7+
 *** depmod 4.14.70+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to e880e627d11af2b17be3efb6d105e3c28cd63867
 *** A reboot is needed to activate the new firmware
Rebooted to enable the new kernel/firmware (crashed, of course, then power cycled), and...

Code: Select all

[email protected]:~$ uname -r
4.14.70-v7+
[email protected]:~$ sudo shutdown now
[  OK  ] Started Show Plymouth Power Off Screen.
[  OK  ] Stopped User Manager for UID 1000.
[  OK  ] Removed slice User Slice of pi.
         Stopping Login Service...
         Stopping Permit User Sessions...
[  OK  ] Stopped Login Service.
[  OK  ] Stopped Permit User Sessions.
[  OK  ] Stopped target Network.
         Stopping dhcpcd on all interfaces...
         Stopping Raise network interfaces...
[  OK  ] Deactivated swap /var/swap.
[  OK  ] Stopped LSB: Autogenerate and use a swap file.
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target NFS client services.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped dhcpcd on all interfaces.
[  OK  ] Stopped Configure Bluetooth Modems connected by UART.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed triggerhappy.socket.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped target System Initialization.
[  OK  ] Stopped Apply Kernel Variables.
         Stopping Update UTMP about System Boot/Shutdown...
         Stopping Network Time Synchronization...
[  OK  ] Stopped target Swap.
         Stopping Load/Save Random Seed...
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped target Encrypted Volumes.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
         Stopping Restore / save the current clock...
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Restore / save the current clock.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
         Unmounting /run/user/1000...
         Unmounting /boot...
[  OK  ] Unmounted /run/user/1000.
[  OK  ] Unmounted /boot.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped File System Check on /dev/disk/by-partuuid/3d9e8996-01.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[   41.071446] reboot: Power down
Successful clean shutdown.

Reboot was also successful.

Code: Select all

[email protected]:~$ sudo reboot
[  OK  ] Stopped target Remote File Systems.
[  OK  ] Stopped target Remote File Systems (Pre).
[  OK  ] Stopped target NFS client services.
[  OK  ] Stopped Raise network interfaces.
[  OK  ] Stopped dhcpcd on all interfaces.
[  OK  ] Stopped Configure Bluetooth Modems connected by UART.
[  OK  ] Stopped target Basic System.
[  OK  ] Stopped target Paths.
[  OK  ] Stopped Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Stopped target Slices.
[  OK  ] Removed slice User and Session Slice.
[  OK  ] Stopped target Sockets.
[  OK  ] Closed triggerhappy.socket.
[  OK  ] Closed Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Closed Syslog Socket.
[  OK  ] Closed D-Bus System Message Bus Socket.
[  OK  ] Stopped target System Initialization.
         Stopping Update UTMP about System Boot/Shutdown...
         Stopping Load/Save Random Seed...
[  OK  ] Stopped target Encrypted Volumes.
[  OK  ] Stopped Forward Password Requests to Wall Directory Watch.
         Stopping Restore / save the current clock...
[  OK  ] Stopped target Swap.
         Stopping Network Time Synchronization...
[  OK  ] Stopped Apply Kernel Variables.
[  OK  ] Stopped Load Kernel Modules.
[  OK  ] Stopped Load/Save Random Seed.
[  OK  ] Stopped Restore / save the current clock.
[  OK  ] Stopped Network Time Synchronization.
[  OK  ] Stopped Update UTMP about System Boot/Shutdown.
[  OK  ] Stopped Create Volatile Files and Directories.
[  OK  ] Stopped target Local File Systems.
         Unmounting /run/user/1000...
         Unmounting /boot...
[  OK  ] Unmounted /run/user/1000.
[  OK  ] Unmounted /boot.
[  OK  ] Reached target Unmount All Filesystems.
[  OK  ] Stopped File System Check on /dev/disk/by-partuuid/3d9e8996-01.
[  OK  ] Removed slice system-systemd\x2dfsck.slice.
[  OK  ] Stopped target Local File Systems (Pre).
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Reached target Shutdown.
[   35.691448] reboot: Restarting system
So this does seem to be fixed now with the latest testing branch kernel and firmware. Hopefully no new bugs were introduced and it will get pushed to the master branch soon. Until then, either stick with the mid-August stable release, or take your chances with rpi-update.
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?


farleysmaster
Posts: 7
Joined: Thu Sep 13, 2018 5:58 pm

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Thu Sep 20, 2018 9:09 am

The fix seems to be live on apt now. Rebooted my 'lite' system with no issues. Just updating my desktop 'system 'now.

fufu65
Posts: 3
Joined: Wed Sep 12, 2018 7:51 am

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Thu Sep 20, 2018 9:25 am

I can confirm that the last upgrade now online seems to fix the problem.
Tested on a RPI3B+ desktop and even on a RasPBX installation.
Thanks!

User avatar
HawaiianPi
Posts: 4887
Joined: Mon Apr 08, 2013 4:53 am
Location: Aloha, Oregon USA

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Thu Sep 20, 2018 11:29 am

1. Raspberry Pi 3B+ with Raspbian Stretch Desktop booting from a 32GB SanDisk Ultra A1 micro SD card.

Before updating.

Code: Select all

[email protected]:~ $ uname -a
Linux LoloPi3 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux
After an update/upgrade/reboot.

Code: Select all

[email protected]:~ $ uname -a
Linux LoloPi3 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux
Reboot and shutdown seem to be functioning as expected (no kernel panic).

2. Raspberry Pi 3B (not +) with Raspbian Stretch Lite USB booting from a SATA SSD (with a USB-SATA adapter cable).

This system was on the latest testing kernel/firmware, which had seemed to fix the shutdown kernel panic.

After update/upgrade/reboot.

Code: Select all

[email protected]:~$ uname -a
Linux Pi3B128SSD 4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux
Still booting, rebooting and shutting down correctly.

Both systems had been previously updated to the buggy September 10th kernel/firmware, and then rolled back to the mid August stable release using rpi-update with the appropriate hash. The second system was then updated to a more recent testing firmware with the same kernel number as the new master branch.

Both systems found and installed the new master branch kernel and firmware when I ran:

Code: Select all

sudo apt update && sudo apt full-upgrade -y
And neither system is experiencing kernel panics any longer.

So thanks to all those who worked on identifying and fixing this. :ugeek:
My mind is like a browser. 27 tabs are open, 9 aren't responding,
lots of pop-ups...and where is that annoying music coming from?

LTolledo
Posts: 2165
Joined: Sat Mar 17, 2018 7:29 am
Location: Anime Heartland

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Thu Sep 20, 2018 11:57 am

me do "regular" upgrade only...

and can confirm that the "cure" works... on my my once bug-bitten RPi3B and RPi3B+

thanks!
"Don't come to me with 'issues' for I don't know how to deal with those
Come to me with 'problems' and I'll help you find solutions"

Some people be like:
"Help me! Am drowning! But dont you dare touch me nor come near me!"

martin_collins
Posts: 4
Joined: Wed Sep 12, 2018 3:24 pm

Re: After last updates RPI 3+ hangs on shurdown/reboot if bluetooth off

Sun Sep 23, 2018 3:03 am

Yup all good for me as well now. I removed the holds I had placed on the raspberrypi-bootloader and raspberrypi-kernel packages and then ran "sudo apt update && sudo apt full-upgrade -y" then rebooted and confirmed "uname -a" showed I was running "4.14.70-v7+ #1144 SMP Tue Sep 18 17:34:46 BST 2018 armv7l GNU/Linux" version of the kernel and now my Pi is shutting down and rebooting without issue.

Glad it's fixed! :D

Return to “Troubleshooting”