2015-11-25, 07:47
(2015-11-24, 22:30)bagofcrap24 Wrote: OK build #1119 is the first build where I start having issues rebooting
Haven't had any similar problem here. I'll try a clean build for #1125 on Wednesday evening, see if that helps.
(2015-11-24, 22:30)bagofcrap24 Wrote: OK build #1119 is the first build where I start having issues rebooting
(2015-11-24, 22:05)effe.rnr Wrote: Do you already know when the ALSA-to-PulseAudio bridge will be implemented again? I am using built #1110 but I'd like to update again
(2015-11-24, 21:23)bagofcrap24 Wrote: another quick question.
Is this normal behaviour when transferring the update tar to the SD card
(2015-11-25, 13:58)zaRos Wrote: here is debug after updated to #1124
(2015-11-24, 22:05)effe.rnr Wrote: Do you already know when the ALSA-to-PulseAudio bridge will be implemented again? I am using built #1110 but I'd like to update again
(2015-11-24, 22:30)bagofcrap24 Wrote: OK build #1119 is the first build where I start having issues rebooting
(2015-11-25, 16:33)Milhouse Wrote:(2015-11-24, 22:30)bagofcrap24 Wrote: OK build #1119 is the first build where I start having issues rebooting
@bagofcrap24: Build #1124y is a new clean build, maybe see if that helps with the reboot issue.
(2015-11-25, 21:58)bagofcrap24 Wrote: Is there a way to see the console as it's shutting down to see where the process is failing? (I've tried booting into textmode via cmdline.txt which rebooting works fine)
# uname -a
Linux rpi512 4.3.0 #1 Thu Nov 26 03:20:12 GMT 2015 armv6l GNU/Linux
# vcgencmd version
Nov 25 2015 17:54:26
Copyright (c) 2012 Broadcom
version fda23007cfd89bf42af864b57701b39e1ac8c552 (clean) (release)
# lsb_release
OpenELEC (Milhouse) - Version: devel-20151126031923-#1125-g4e26348 [Build #1125]
# vcdbg log msg 2>&1 | grep DTOK
001694.198: Kernel trailer DTOK property says yes
# Kernel device tree status: Enabled
(2015-11-26, 05:46)Milhouse Wrote:(2015-11-25, 21:58)bagofcrap24 Wrote: Is there a way to see the console as it's shutting down to see where the process is failing? (I've tried booting into textmode via cmdline.txt which rebooting works fine)
Add "debugging" to the end of your line in /flash/cmdline.txt.
Reboot, then in ssh run "journalctl --no-pager --follow > /storage/journal.log" and leave it running.
Either from a second ssh session, or the GUI, reboot the device (whatever is your normal method).
You should capture the shutdown sequence (and hopefully the reason for it stalling) in /storage/journal.log.
I'm going to drop the connman-1.30 bump (ie. revert back to connman-1.23) in the next build (#1125, uploading). If #1125 reboots reliably, then capturing the shutdown logs from #1124y and #1125 then comparing the difference may help isolate the problem.