No activity after 'pacman -Syu && sync && systemctl reboot'

[fionnbharr]

Howdy all;

Long-time Arch user on other systems; been using Arch on RPi for about 2 years.

Situation:
RPi3 B board, new install on SD card, using the reccomended 'RPi 2' install. Only change from stock is I've added "enable_uart=1" in /boot/config.txt, as I'm connecting via serial.

First boot works fine and I do a standard pacman -Syu to update the binaries. The board works fine with the updated binaries, until I power off with 'systemctl reboot' or 'systemctl poweroff'.

On restart, the board powers on (the Red LED glows), but there's no activity from the green LED. It's as if the board is dead; no activity at all, and no way to diagnose.

The sd card seems fine; no errors found using multiple low-level utilities.

I am unable to find any recent 'pacman fails!'-type topics on this forum relating to non-booting results (some video/audio problems, but no 'dead board' ones).

Help is appreciated.

[graysky]

Not sure how recent the image is but does your /boot/config.txt contain:
$this->bbcode_second_pass_code('', 'initramfs initramfs-linux.img followkernel')

[fionnbharr]

Yes, that line is present in /boot/config.txt ; the tar is freshly downloaded two days ago. (16 Mar 2017), and that line is included in the stock config.txt.

As I indicated, the only change I've made to any configuration is the single line "enable_uart=1" in config.txt

First time I run 'pacman -Syu' .... the board dies upon next boot.

[WarheadsSE]

"dies" .. does the serial console work, since you have it turned on?

[fionnbharr]

No; no activity from the board at all -- no output on serial, no green LED, no HDMI output, nothing. As I indicated in the OP, there's no way to diagnose, AFAIK.

Only the red LED is on.

[fionnbharr]

Updated information on OP:

Re-imaged the sd card with the standard RPi-2 image. Boots normally, and can runs as fine as I can tell using the initial binaries.

pacman -Syu completes dandy, and sync just to be sure everything is written. At this point, the board *feels* cool to the touch, and the green LED blinks with (I believe) read/writes to the sd card.

'systemctl reboot', and the board starts with a solid Red LED, the green LED blinks twice (2x) then goes off. The Broadcom chip now *feels* hot. Hot in a way that becomes uncomfortable to the touch, and was not like this before the pacman update.

Any suggestions?

[Kabbone]

The pacman.log after the upgrade and the output of mount would be a start, I think

[fionnbharr]

Not sure what you mean by wanting what's mounted -- as far as I can tell, there's no mounting of any part of the sd card. There's no I/O available to see what's mounted or not mounted. No tty, no serial, no HDMI output of any kind.

/var/log/pacman log:
$this->bbcode_second_pass_code('', '
[2017-03-20 13:44] [PACMAN] Running 'pacman -S vim'
[2017-03-20 13:44] [ALPM] transaction started
[2017-03-20 13:44] [ALPM] installed vim-runtime (8.0.0427-1)
[2017-03-20 13:44] [ALPM] installed gpm (1.20.7-7)
[2017-03-20 13:44] [ALPM] installed vim (8.0.0427-1)
[2017-03-20 13:44] [ALPM] transaction completed
[2017-03-20 13:44] [ALPM] running 'systemd-update.hook'...
[2017-03-20 19:14] [PACMAN] Running 'pacman -Syuw'
[2017-03-20 19:14] [PACMAN] synchronizing package lists
[2017-03-20 19:14] [PACMAN] starting full system upgrade
[2017-03-20 19:14] [PACMAN] Running 'pacman -Su'
[2017-03-20 19:14] [PACMAN] starting full system upgrade
[2017-03-20 19:15] [ALPM] transaction started
[2017-03-20 19:15] [ALPM] upgraded linux-api-headers (4.7-1 -> 4.10.1-1)
[2017-03-20 19:15] [ALPM] upgraded iana-etc (20161110-1 -> 20170303-1)
[2017-03-20 19:15] [ALPM] upgraded glibc (2.24-2 -> 2.25-1)
[2017-03-20 19:15] [ALPM-SCRIPTLET] Generating locales...
[2017-03-20 19:15] [ALPM-SCRIPTLET] en_US.UTF-8... done
[2017-03-20 19:15] [ALPM-SCRIPTLET] en_US.ISO-8859-1... done
[2017-03-20 19:15] [ALPM-SCRIPTLET] Generation complete.
[2017-03-20 19:15] [ALPM] upgraded p11-kit (0.23.2-1 -> 0.23.5-1)
[2017-03-20 19:15] [ALPM] upgraded gcc-libs (6.3.1-1 -> 6.3.1-2)
[2017-03-20 19:17] [ALPM] upgraded ca-certificates-utils (20160507-1 -> 20170307-1)
[2017-03-20 19:17] [ALPM] upgraded ca-certificates-mozilla (3.29.1-1 -> 3.29.3-2)
[2017-03-20 19:17] [ALPM] upgraded ca-certificates (20160507-1 -> 20170307-1)
[2017-03-20 19:17] [ALPM] upgraded libutil-linux (2.29.1-1 -> 2.29.2-1)
[2017-03-20 19:17] [ALPM] upgraded libseccomp (2.3.1-1 -> 2.3.2-1)
[2017-03-20 19:17] [ALPM] upgraded libgpg-error (1.26-1 -> 1.27-1)
[2017-03-20 19:17] [ALPM] upgraded keyutils (1.5.9-1 -> 1.5.10-1)
[2017-03-20 19:17] [ALPM] upgraded util-linux (2.29.1-1 -> 2.29.2-1)
[2017-03-20 19:17] [ALPM] upgraded cryptsetup (1.7.3-1 -> 1.7.4-1)
[2017-03-20 19:17] [ALPM] upgraded dnssec-anchors (20150403-1 -> 20170228-1)
[2017-03-20 19:17] [ALPM] upgraded gnutls (3.5.9-1 -> 3.5.10-1)
[2017-03-20 19:17] [ALPM] upgraded gpgme (1.7.1-2 -> 1.8.0-2)
[2017-03-20 19:20] [ALPM] upgraded linux-firmware (20170217.12987ca-2 -> 20170309.695f2d6-1)
[2017-03-20 19:21] [ALPM] upgraded mkinitcpio (22-1 -> 23-1.1)
[2017-03-20 19:21] [ALPM] upgraded linux-raspberrypi (4.9.13-3 -> 4.9.16-1)
[2017-03-20 19:21] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2017-03-20 19:22] [ALPM] upgraded man-pages (4.09-1 -> 4.10-2)
[2017-03-20 19:22] [ALPM] upgraded mdadm (3.4-1 -> 4.0-1)
[2017-03-20 19:22] [ALPM] upgraded openresolv (3.8.1-1 -> 3.9.0-1)
[2017-03-20 19:22] [ALPM] upgraded pciutils (3.5.2-1 -> 3.5.4-1)
[2017-03-20 19:22] [ALPM] upgraded raspberrypi-bootloader (20170303-1 -> 20170319-1)
[2017-03-20 19:22] [ALPM] upgraded raspberrypi-bootloader-x (20170303-1 -> 20170319-1)
[2017-03-20 19:22] [ALPM] upgraded raspberrypi-firmware (20170301-1 -> 20170319-1)
[2017-03-20 19:22] [ALPM] upgraded xfsprogs (4.9.0-1 -> 4.10.0-1)
[2017-03-20 19:22] [ALPM] transaction completed
[2017-03-20 19:22] [ALPM] running '99-linux-raspberrypi.hook'...
[2017-03-20 19:22] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux-raspberrypi.preset: 'default'
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> -k 4.9.16-1-ARCH -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2017-03-20 19:22] [ALPM-SCRIPTLET] ==> Starting build: 4.9.16-1-ARCH
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2017-03-20 19:22] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2017-03-20 19:22] [ALPM-SCRIPTLET] ==> WARNING: No modules were added to the image. This is probably not what you want.
[2017-03-20 19:22] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2017-03-20 19:22] [ALPM-SCRIPTLET] ==> Image generation successful
[2017-03-20 19:22] [ALPM] running 'systemd-tmpfiles.hook'...
[2017-03-20 19:22] [ALPM] running 'systemd-update.hook'...
[2017-03-20 19:22] [ALPM] running 'texinfo-install.hook'...
[2017-03-20 19:24] [ALPM] running 'update-ca-trust.hook'...
[2017-03-20 19:36] [PACMAN] Running 'pacman -S ed'
[2017-03-20 19:36] [ALPM] transaction started
[2017-03-20 19:36] [ALPM] installed ed (1.14.1-2)
[2017-03-20 19:36] [ALPM] transaction completed
[2017-03-20 19:36] [ALPM] running 'systemd-update.hook'...
[2017-03-20 19:36] [ALPM] running 'texinfo-install.hook'...

')

This is the entirety of the pacman.log file. I did add vim and ed to the mix for my own ease of use. Also, a six-hour gap because work.

[Kabbone]

My intention was if perhaps the boot partition is not mounted, but the standard image doesn't have an boot partition.
Do you use v4l module for the camera? If so, take a look here

[fionnbharr]

The standard image doesn't have a separate partition, but the instructions elsewhere on this Archlinuxarm.org website for installation onto RPi3 do, indeed, have the user divvy the sd card into a dedicated 'boot' and 'root' partition. This is my set-up, and it has worked in the past on RPi3 boards, but isn't working for me now.

...There's a camera? I don't recall mentioning a camera. I think a working board should come first before attaching a camera.

Currently the only connections to the board are the USB power (tested, and meets RPi3 reqs), a CAT5e cable into the network, and a serial cable to my laptop. No camera, no monitor, nor HDMI or audio.