[11:01] <waveform> @pilot in
[14:10] <ahasenack> waveform: hi, pi4 question
[14:10] <ahasenack> waveform: I'm issuing a "reboot" remotely via ssh, but it's actually powering off. Have you seen that?
[14:11] <ahasenack> waveform: it's lunar, on 6.2.0-1012-raspi
[14:24] <waveform> ahasenack, no that's definitely odd -- let me try and reproduce here -- I assume we're talking about the server image and not desktop? (no idea why that would make a difference but just in case)
[14:24] <ahasenack> yes, server
[14:24] <ahasenack> I think it was dist-ugpraded ever since the first install
[14:25] <ahasenack> I also don't know what's happening in the console while it's "rebooting", maybe there is a clue
[14:30] <waveform> oh, and arm64?
[14:30] <ahasenack> yes
[14:30] <waveform> (good stuff, I had assumed but always good to check!)
[14:34] <teward> ddstreet: mapreri: email thread coming your way that will need your attention.  Not on the ML for reasons
[15:01] <waveform> @pilot out
[15:05] <waveform> ahasenack, seems to reboot happily for me (with "sudo reboot" over an SSH connection on a fully upgraded system running 6.2.0-1012-raspi), but interestingly it's failing to configure the ethernet after the reboot (or at least it's stuck in systemd-networkd-wait-online). Are you sure it's actually shutting down and it's not just rebooted but the networking has failed?
[15:06] <waveform> oh, but now it has managed to bring eth up ... I wonder what's going on. Oh, false alarm -- it's me being stupid (used the same Pi I was using for NBD tests and I'd configured the router to ignore it for DHCP purposes)
[15:08] <ahasenack> re being sure it's off: the power led is off
[15:08] <ahasenack> regarding systemd wait online, there was a bug filed this weekend about it being stuck
[15:09] <ahasenack> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358
[15:09] -ubottu:#ubuntu-devel- Launchpad bug 2036358 in systemd (Ubuntu) "systemd wait-online now times out after jammy and lunar upgrade" [Critical, New]
[15:09] <ahasenack> I guess I'll have to hook the hdmi out to the tv and see what's happening
[15:11] <waveform> the power LED is off? That's doubly weird; typically when the Pi is shutdown the red power LED remains lit (there's a series of flashes on the green ACT LED to indicate shutdown, but the power LED remains on because in fact it's just going into an "interrupted reboot" where the boot firmware's waiting for an indication on the GPIO that it's time to wake up again)
[15:15] <waveform> hmm, and thanks for the indication on the wait-online ticket -- just switched out the Pi for one which I hadn't messed with the DHCP config and I'm seeing that timeout as well so I guess the Pi images are affected too
[15:18] <vorlon> @pilot in
[16:04] <seb128> !dmb-ping
[16:12] <teward> i'm late sorry seb128