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

[fufu65]

Hi,
installed 2018-06-27 raspbian image on new RPI3+; after disabling bluetooth interface the system hangs on shutdown/reboot ONLY if last updates are applied (with a fresh image it's ok).
Tested 3 times with many new sd cards.
Any ideas?
Fulvio

[martin_collins]

I noticed the same issue as well on my RPi 3 Model B last night. I upgraded some packages (see below) and then noticed after the next reboot that the Pi was hanging while shutting down. I left it for a while to see if it would eventually shutdown and noticed that the CPU was getting really hot to the touch and eventually the over temperature icon appeared. I had no choice but to unplug it. I then tried again today and still the same thing is happening. Once I saw this post, I checked my Bluetooth settings and sure enough, my BT is switched off. I enabled it and tried to shutdown/reboot and all was fine. So this leads me to think something in the upgrade I did last night is causing this issue when BT is off.

The list of packages which were upgraded last night were as follows:

2018-09-11 22:45:20 status installed libgs9-common:all 9.20~dfsg-3.2+deb9u4
2018-09-11 22:45:21 status installed rpi-chromium-mods:armhf 20180910
2018-09-11 22:46:35 status installed raspberrypi-bootloader:armhf 1.20180910-1
2018-09-11 22:46:36 status installed libc-bin:armhf 2.24-11+deb9u3
2018-09-11 22:50:13 status installed raspberrypi-kernel:armhf 1.20180910-1
2018-09-11 22:50:14 status installed man-db:armhf 2.7.6.1-2
2018-09-11 22:50:15 status installed libgs9:armhf 9.20~dfsg-3.2+deb9u4
2018-09-11 22:50:15 status installed libraspberrypi0:armhf 1.20180910-1
2018-09-11 22:50:15 status installed libraspberrypi-doc:armhf 1.20180910-1
2018-09-11 22:50:15 status installed libraspberrypi-dev:armhf 1.20180910-1
2018-09-11 22:50:15 status installed ghostscript:armhf 9.20~dfsg-3.2+deb9u4
2018-09-11 22:50:15 status installed libraspberrypi-bin:armhf 1.20180910-1
2018-09-11 22:50:16 status installed libc-bin:armhf 2.24-11+deb9u3

Hopefully the above list helps someone on the RPI Dev team figure out what is going on. For now, I will keep BT enabled to work around this issue.

Martin

[martin_collins]

So I think my other post is still being reviewed by the moderator but in the meantime, I tried rolling back the kernel/firmware to the August 17th Stable release and everything seems fine. If Bluetooth is on/off, the Pi will shutdown and reboot just fine.

For everyone else out there who is experiencing this issue, you can roll back the firmware/kernel by running the following command in the terminal:
sudo rpi-update a05e3e55870367362595d5fa531cedbbc75c62dc

Martin

[HawaiianPi]

I did a full update/upgrade on my Pi3B+ and it reboots and shuts down fine with bluetooth disabled. I added dtoverlay=pi3-disable-bt to config.txt and disabled the splash screen so I could watch the console output, then I did several reboots and shutdowns without any trouble.

Raspbian Stretch Desktop, fully upgraded.

Code: Select all

sudo apt update && sudo apt full-upgrade -y
sudo reboot

~ $ uname -a
Linux LoloPi3 4.14.69-v7+ #1141 SMP Mon Sep 10 15:26:29 BST 2018 armv7l GNU/Linux

~ $ cat /sys/firmware/devicetree/base/model;echo
Raspberry Pi 3 Model B Plus Rev 1.3

I saw someone else report this issue as well (in another thread), but I have been unable to reproduce it on my Pi3B+ in a Flirc case powered by the official RPF PSU and booting from an SanDisk Ultra A1 micro SD card.

[HawaiianPi]

Interesting...

Tried it on my USB (SSD) booted Pi3B (not +) running Raspbian Lite, and reboot hung with a kernel panic after the update.

So are others with this problem booting from USB, or running Raspbian Lite?

Testing a freshly imaged SSD now...

EDIT:
Reboots worked on freshly imaged and updated SSD, but shutdown still kernel panicked.

[farleysmaster]

So turning bluetooth on in raspbian fixed things, but I couldn't work out how to fix things on my raspbian lite installation.

Going to roll back the firmware now.

[HawaiianPi]

I also rolled back to the mid August firmware, and it fixed the shutdown kernel panic.

Code: Select all

sudo rpi-update 911147a3276beee09afc4237e1b7b964e61fb88a

Will install firmware 1.20180817-1 with the 4.14.62-v7+ kernel.

[martin_collins]

I also rolled back to the mid August firmware, and it fixed the shutdown kernel panic.

Code: Select all

sudo rpi-update 911147a3276beee09afc4237e1b7b964e61fb88a

Will install firmware 1.20180817-1 with the 4.14.62-v7+ kernel.

Thanks HawaiianPi, I think I am going to do the same as you did and use the Git commit hash you referenced to enable firmware 1.20180817-1 with the 4.14.62-v7+ kernel.

[HawaiianPi]

Are others experiencing this issue booting from micro SD card, or USB?

My Raspbian Desktop Pi3B+ system that does not have any panic on shutdown is booting from micro SD card. My Raspbian Lite Pi3B system that DID have kernel panics on shutdown is booting from a USB SSD. I tested it with 2 different, freshly imaged drives with the same result (shutdown kernel panic).

But I just tested the same Pi3B system with a freshly imaged Raspbian Lite micro SD card, and I was able to update/full-upgrade it with no shutdown issues. So that has me wondering if it's only happening on USB booted systems?

[yan]

Are others experiencing this issue booting from micro SD card, or USB?

My Raspbian Desktop Pi3B+ system that does not have any panic on shutdown is booting from micro SD card. My Raspbian Lite Pi3B system that DID have kernel panics on shutdown is booting from a USB SSD. I tested it with 2 different, freshly imaged drives with the same result (shutdown kernel panic).

But I just tested the same Pi3B system with a freshly imaged Raspbian Lite micro SD card, and I was able to update/full-upgrade it with no shutdown issues. So that has me wondering if it's only happening on USB booted systems?

I have the same problem. My pi is booting from micro SD card.
For now, i have enable bluetooth to avoid hangs problems during shutdown/restart.

[DirkS]

So are others with this problem booting from USB, or running Raspbian Lite?

No. Works just fine for me.
Pi3B, boot from SSD, BT disabled, running fully up to date Raspbian Stretch.

[HawaiianPi]

... running fully up to date Raspbian Stretch.

Desktop or Lite?

[DirkS]

... running fully up to date Raspbian Stretch.

Desktop or Lite?

Desktop

[farleysmaster]

I had the issue with SD cards using both Raspbian desktop and Raspbian lite. The firmware rollback fixed them.

Are the relevant devs aware of this / how do we make them aware?

Also, how would you normally turn bluetooth on in raspbian lite?

[DirkS]

Are the relevant devs aware of this / how do we make them aware?

They may already be aware, but you could open an issue at https://github.com/raspberrypi/firmware/issues

Also, how would you normally turn bluetooth on in raspbian lite?

AFAIK it's on by default.

[farleysmaster]

Cheers. I couldn’t do anything to get the raspian lite system to work except roll back the firmware.

[Peter Ryan]

Just a "me too" post here. I have a 3B+ booting from SD-card using an official PSU, a wired keyboard and wired mouse connected. Running Raspbian desktop. Oh, and I don't have bluetooth enabled.

I only noticed the problem yesterday; the first time I shutdown, it hung with just the desktop wallpaper showing. The next time, same but with the shutdown dialog window visible. I've since played with enabling Bluetooth and that does seem to work around the problem; I believe I did manage to boot with BT enabled, disabled it and it shutdown fine. With splash screen disabled, I got this screen grab (dunno if it's any use!):

IMG_20180914_144416260_scaled.jpg (212.25 KiB) Viewed 5940 times

[aranra]

Hello! I have several days programmed different sd cards, because first I used 32G Sandisk. Then I moved
smaller ones 16G and 8G different manufact. no help. I used Noobs 2.8.2, everything was okay without update/upgrade.
When done my pi 3B+ hangs when shutdown or reboot, I had bluetooth off. Today I tested several times
bluetooth ON or OFF. Working only bluetooth ON.

[Douglas6]

Been lurking on this thread, and I have a question: what does it mean to "turn Bluetooth on" or "off"? I initially assumed (as have others) it meant disabling the onboard chip by editing config.txt and adding 'dtoverlay=pi3-disable-bt'. But some posters have mentioned "turning it off" in Raspbian (not too specific), or "Bluetooth settings" (only slightly more specific.) Are we all talking the same operation here?

[tubaclarinet]

Lurkers are welcome! I am glad that you asked this question instead of just suffering in silence. In Raspbian with Pixel desktop, there is a Bluetooth icon located on the right-end of the panel near the clock, network icon, CPU usage monitor, etc. When I clicked on that Bluetooth icon, a menu displayed the option to turn on/off Bluetooth and when I enabled Bluetooth, then I was able to reboot/shutdown without the system hanging. No need to edit the configuration file.

HTH

[Douglas6]

Interesting. I wonder what that menu option does.

[LTolledo]

This USB flashdrive boot Rpi3B+'s bluetooth has always been set to OFF for over 5 months now.

Intrigued by the topic, I just did an update and upgrade just a few minutes ago.

closed all the apps properly then issued reboot command.....

it rebooted without any errors/malfunctions/problems.....

Why bluetooth always OFF? I have not use for it, simple as that.

Will try it on an microSD boot RPi3B with Raspbian Lite (installed a week ago) and see if it hangs....

as there is no option to disable bluetooth via raspi-config, I followed the procedures in this link to disable bluetooth
https://scribles.net/disabling-bluetoot ... pberry-pi/
after that I updated and upgraded.... then issued reboot command....

it booted...

[HawaiianPi]

then issued reboot command....

it booted...

The problem is with shutdown, not reboot.

[LTolledo]

The problem is with shutdown, not reboot.

Oh that too...just tried a while ago... no errors/problems during shutdown, either on the Desktop version (bluetooth always OFF) and the Lite version

[HawaiianPi]

Yea, this is an odd one. It's only happening on one of my two systems that have been recently updated, and only on shutdown (even after starting from a fresh image). ¯\_(ツ)_/¯ I'm holding off on upgrading my other systems for now, and I've rolled back the firmware to the last stable mid-August release to fix it on the updated systems.