BBB Rev D Debian 13.7 (Trixie) hangs when rebooting

On the debug serial port, typing sudo reboot starts the reboot process, but then it halts at:

[ OK ] Stopped serial-getty@ttyS0.service - Serial Getty on ttyS0.

No further output or progress. I still get a heartbeat. When I plug/unplug the Ethernet I get messages about link going up or down, but no reaction to keystrokes. At this point, I can ssh in and complete the connection, but again, there is no information on the screen, just a successful connection.
Need a power cycle to recover.
The boards worked fine with the version that was in the box (v12, Bookworm). If I use a SDcard with v12, they work. Problem started after I flashed to the latest version.
I wanted v13 because of libgpiod v2. If there is a simple way to install that on v12 I will take it.

What other info can I provide?

Is this 5.10.x, 6.12.x, or 6.18.x kernel?

Regards,

6.18.x

Can you please run this command and report it’s ouput:

sudo beagle-version

are you using the usb interface for debugging/network? USB for power, or 5V barrel jack?

Regards,

power via USB

terminal via 3V3 serial adapter

debian@BeagleBone:~$ sudo beagle-version [sudo] password for debian: eeprom:[A335BNLT00D02623SBB07417] model:[TI_AM335x_BeagleBone_Black] dogtag:[``BeagleBoard.org`` Debian Trixie Base Image 2026-09-15] bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2022.04-g5509547b (Jan 22 2026 - 19:56:08 +0000)]:[location: dd MBR] UBOOT: Booted Device-Tree:[am335x-boneblack-uboot.dts] UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0.kernel] UBOOT: Loaded Overlay:[BB-ADC-00A0.kernel] UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.kernel] UBOOT: Loaded Overlay:[BB-SPIDEV0-00A0.kernel] kernel:[6.18.52-bone54] /boot/uEnv.txt Settings: uboot_overlay_options:[disable_uboot_overlay_video=1] uboot_overlay_options:[disable_uboot_overlay_audio=1] uboot_overlay_options:[uboot_overlay_addr4=BB-SPIDEV0-00A0.dtbo] uboot_overlay_options:[enable_uboot_overlays=1] uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo] pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>] pkg:[bb-customizations]:[1.20250808.0-0~trixie+20250808] pkg:[bb-usb-gadgets]:[1.20260724.0-0~trixie+20260724] pkg:[bb-wl18xx-firmware]:[1.20230703.0-0~trixie+20240703] pkg:[kmod]:[34.2-2bbbio1~trixie+20250522] groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render netdev i2c gpio bluetooth admin tisdk weston-launch] cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk1p3 ro rootfstype=ext4 rootwait fsck.repair=yes earlycon coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100] dmesg | grep remote [ 2.617814] remoteproc remoteproc0: wkup_m3 is available [ 5.415081] remoteproc remoteproc0: powering up wkup_m3 [ 5.448888] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148 [ 5.507212] remoteproc remoteproc0: remote processor wkup_m3 is now up [ 16.798574] systemd[1]: Reached target remote-fs.target - Remote File Systems. dmesg | grep pru dmesg | grep pinctrl-single [ 2.664838] pinctrl-single 44e10800.pinmux: 142 pins, size 568 dmesg | grep gpio-of-helper dmesg | grep wlcore lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub END

well that formatting didn’t work

debian@BeagleBone:~$ sudo beagle-version
[sudo] password for debian:
eeprom:[A335BNLT00D02623SBB07417]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Trixie Base Image 2026-09-15]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot SPL 2022.04-g5509547b (Jan 22 2026 - 19:56:08 +0000)]:[location: dd MBR]
UBOOT: Booted Device-Tree:[am335x-boneblack-uboot.dts]
UBOOT: Loaded Overlay:[AM335X-PRU-UIO-00A0.kernel]
UBOOT: Loaded Overlay:[BB-ADC-00A0.kernel]
UBOOT: Loaded Overlay:[BB-BONE-eMMC1-01-00A0.kernel]
UBOOT: Loaded Overlay:[BB-SPIDEV0-00A0.kernel]
kernel:[6.18.52-bone54]
/boot/uEnv.txt Settings:
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[disable_uboot_overlay_audio=1]
uboot_overlay_options:[uboot_overlay_addr4=BB-SPIDEV0-00A0.dtbo]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-UIO-00A0.dtbo]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade ]
pkg:[bb-customizations]:[1.20250808.0-0~trixie+20250808]
pkg:[bb-usb-gadgets]:[1.20260724.0-0~trixie+20260724]
pkg:[bb-wl18xx-firmware]:[1.20230703.0-0~trixie+20240703]
pkg:[kmod]:[34.2-2bbbio1~trixie+20250522]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal input render netdev i2c gpio bluetooth admin tisdk weston-launch]
cmdline:[console=ttyS0,115200n8 root=/dev/mmcblk1p3 ro rootfstype=ext4 rootwait fsck.repair=yes earlycon coherent_pool=1M net.ifnames=0 lpj=1990656 rng_core.default_quality=100]
dmesg | grep remote
[ 2.617814] remoteproc remoteproc0: wkup_m3 is available
[ 5.415081] remoteproc remoteproc0: powering up wkup_m3
[ 5.448888] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217148
[ 5.507212] remoteproc remoteproc0: remote processor wkup_m3 is now up
[ 16.798574] systemd[1]: Reached target remote-fs.target - Remote File Systems.
dmesg | grep pru
dmesg | grep pinctrl-single
[ 2.664838] pinctrl-single 44e10800.pinmux: 142 pins, size 568
dmesg | grep gpio-of-helper
dmesg | grep wlcore
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
END

Okay, i’ll test that with a RevD tomorrow, i see nothing mis-configured in the rest of the log..

Regards,

Hi all,

FYI, I am experiencing the same issue on the PocketBeagle2 running the Debian Trixie 13.7 IoT image. The device boots up normally when the serial terminal is disconnected.
Additionally, there is another issue where the login prompt sometimes fails to appear on debug serial port after startup.

Best regards.

@RobertCNelson sounds suspiciously like what we’ve been seeing on BVF,
so albeit not a “new” thing, it seems very persistent.

As the same board reboots normally with Bookworm and the problem started immediately after moving to Debian 13, I’d focus on the Trixie/kernel/device-tree side rather than the hardware. The fact that the heartbeat continues and Ethernet still responds makes it look like the kernel isn’t completely dead, but something in the shutdown sequence is getting stuck. I’d compare the kernel version and boot configuration between the working Bookworm image and Trixie, and check the full journal from the failed reboot with journalctl -b -1 after power cycling. If you mainly need libgpiod v2, it may also be worth checking whether installing/building that separately on Bookworm is easier than dealing with the reboot issue.

Just to add as i’m seeing this locally… one of the systemd scripts is hanging on reboot.. it should timeout after 90 seconds, but this is a fun thing to debug… systemd.log_level=debug

voodoo@BeagleY-AI:~/u-boot$ 
         Stopping session-1.scope - Session 1 of User voodoo...
[  OK  ] Removed slice system-hostapd.slice - Slice /system/hostapd.
[  OK  ] Removed slice system-modprobe.slice - Slice /system/modprobe.
[  OK  ] Stopped target bluetooth.target - Bluetooth Support.
[  OK  ] Stopped target graphical.target - Graphical Interface.
[  OK  ] Stopped target sound.target - Sound Card.
[  OK  ] Stopped target timers.target - Timer Units.
[  OK  ] Stopped apt-daily-upgrade.timer - Daily apt upgrade and clean activities.
[  OK  ] Stopped apt-daily.timer - Daily apt download activities.
[  OK  ] Stopped apt-listchanges.timer - Try hourly to initialize apt-listchanges database for APT.
[  OK  ] Stopped dpkg-db-backup.timer - Daily dpkg database backup timer.
[  OK  ] Stopped e2scrub_all.timer - Periodic ext4 Online Metadata Check for All Filesystems.
[  OK  ] Stopped fstrim.timer - Discard unused filesystem blocks once a week.
[  OK  ] Stopped logrotate.timer - Daily rotation of log files.
[  OK  ] Stopped man-db.timer - Daily man-db regeneration.
[  OK  ] Stopped systemd-tmpfiles-clean.timer - Daily Cleanup of Temporary Directories.
[  OK  ] Stopped target usb-gadget.target - Hardware activated USB gadget.
[  OK  ] Closed systemd-rfkill.socket - Load/Save RF Kill Switch Status /dev/rfkill Watch.
         Stopping bluetooth.service - Bluetooth service...
         Stopping code-server@voodoo.service - code-server...
         Stopping gpio-manager.service - Centralized GPIO manager daemon...
         Stopping polkit.service - Authorization Manager...
         Stopping systemd-networkd-persistent-storage.service - Enable Persistent Storage in systemd-networkd...
         Stopping systemd-random-seed.service - Load/Save OS Random Seed...
[  OK  ] Stopped systemd-udev-load-credentials.service - Load udev Rules from Credentials.
         Stopping wtmpdb-update-boot.service - Write boot and shutdown times into wtmpdb...
[  OK  ] Stopped bluetooth.service - Bluetooth service.
[  OK  ] Stopped polkit.service - Authorization Manager.
[  OK  ] Stopped gpio-manager.service - Centralized GPIO manager daemon.
[  OK  ] Stopped code-server@voodoo.service - code-server.
[  OK  ] Stopped unattended-upgrades.service - Unattended Upgrades Shutdown.
[  OK  ] Stopped serial-getty@ttyS2.service - Serial Getty on ttyS2.

(and waiting)

(3 minutes still locked up)

notes for future me..

If this reboots, its a systemd issue..

sudo reboot -f
append: console=ttyS2,115200n8 root=/dev/mmcblk1p2 ro rootfstype=ext4 fsck.repair=yes rootwait net.ifnames=0 systemd.log_level=debug systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on enforcing=0

now it keeps rebooting.. voodoo@BeagleY-AI:~$ uname -r 7.2.6-arm64-k3-r16 oh lets upgrade as i know this board failed to reboot a little bit ago..

bb-code-server/unknown 4.141.0-0bbbio0~trixie+20261008 arm64 [upgradable from: 4.136.2-0bbbio0~trixie+20260909]
bb-u-boot-beagleboneai64/unknown 2026.10.20261005.0-0~trixie+20261007 arm64 [upgradable from: 2026.07.20260706.0-0~t>
bbb.io-headers-7.2-k3/unknown,unknown 1.20261005.0-0~trixie+20261005 arm64 [upgradable from: 1.20260915.0-0~trixie+2>
bbb.io-kernel-7.2-k3/unknown,unknown 1.20261005.0-0~trixie+20261005 arm64 [upgradable from: 1.20260915.0-0~trixie+20>
cockpit-bridge/unknown,unknown 368-1~bpo13+1 all [upgradable from: 367-1~bpo13+1]
cockpit-packagekit/unknown,unknown 368-1~bpo13+1 all [upgradable from: 367-1~bpo13+1]
cockpit-system/unknown,unknown 368-1~bpo13+1 all [upgradable from: 367-1~bpo13+1]
cockpit-ws/unknown,unknown 368-1~bpo13+1 arm64 [upgradable from: 367-1~bpo13+1]
libcpupower1/stable-security 6.12.111-1 arm64 [upgradable from: 6.12.107-1]
liblzma5/stable-security 5.8.1-1+deb13u2 arm64 [upgradable from: 5.8.1-1+deb13u1]
libpcre2-8-0/stable-security 10.46-1~deb13u3 arm64 [upgradable from: 10.46-1~deb13u2]
libssl-dev/stable-security 3.5.7-1~deb13u3 arm64 [upgradable from: 3.5.7-1~deb13u2]
libssl3t64/stable-security 3.5.7-1~deb13u3 arm64 [upgradable from: 3.5.7-1~deb13u2]
linux-cpupower/stable-security 6.12.111-1 arm64 [upgradable from: 6.12.107-1]
linux-libc-dev/stable-security 6.12.111-1 all [upgradable from: 6.12.107-1]
openssl-provider-legacy/stable-security 3.5.7-1~deb13u3 arm64 [upgradable from: 3.5.7-1~deb13u2]
openssl/stable-security 3.5.7-1~deb13u3 arm64 [upgradable from: 3.5.7-1~deb13u2]
rsync/stable-security 3.5.0+ds1-0+deb13u1 arm64 [upgradable from: 3.4.1+ds1-5+deb13u4]
xz-utils/stable-security 5.8.1-1+deb13u2 arm64 [upgradable from: 5.8.1-1+deb13u1]

Regards,