I wanted to check if the problem was pre existing or a result of a potentially bad merge on my part. It sounds like reboot wasn't a big concern for the raspberry Pi engineers. Wow, weird.
Thanks for the suggestion. I'll try it out when/if they ever have the zero available in Canada for a comparable price. Do you use the pi or pi2 kernel for zero? Chris On Sep 9, 2016, at 4:31 AM, Richard Miller <9f...@hamnavoe.com> wrote: >> Only weird problem is when I do fshalt -r. My pi2 goes unstable with panics >> on reboot. Cold reset brings it back to normal. > > Sorry, I have seen this failure too, but only on pi3. If you run with > *ncpu=1 the soft reboot seems to work reliably. But my scheme for > rebooting from multicore state is clearly not right. Unfortunately I > don't know of any way of forcing an arm reset after loading the new > kernel without also resetting the gpu back to the load-from-sdcard > point. I'll welcome any suggestions for a way to do this. I think > linux on the pi supports kexec, so it might be possible to reverse > engineer from that and find a way that works. On the other hand, if > you search the web for "raspbian kexec" most of the hits seem to be of > the "doesn't work" variety, so maybe not. > >> Does your latest code work on Pi zero? I don't yet have one to test it. > > Yes it does. If you boot different kernels from the same sdcard you need > to use [pi0] as a section header for the zero. (Discovered by trial and > error because this doesn't seem to be documented anywhere.) > >
