Jan Stary <h...@stare.cz> wrote: > On Jan 09 11:03:57, t...@tedunangst.com wrote: > > Jan Stary wrote: > > > Installing base66.tgz 100% |**************************| 99116 MB - > > > 07:12edT- > > > Installing comp66.tgz 83% |********************* | 45312 KB - > > > stalledT-syncing disks... done > > > rebooting... > > > > > > Why does it reboot here? The SD card is slow, and is being both read > > > and written at this point, but even if it stalled the installer horribly, > > > it would not reboot, right? > > > > there's a watchdog timeout that reboots. I believe there was a bug fixed > > after 6.6 to reset it if progress is being made. > > Thank you. > > https://marc.info/?l=openbsd-cvs&m=156889553923923&w=2 > Looking at install.sub, it seems that the watchdog timer (30 min) > is reset after installing every set. I don't see the watchdog being > reset whenever there is "progress" - did you mean the completion > of a set (as opposed to just not being -stalled-)? > > Also, the resets only happen with $UU, which is only set with -x > - where should that option be passed? (not in sysupgrade.) > > Grandpa's analog stopwatch on a chain says > that it indeed reboot around the 30 min mark.
This entire design is intentional. If a machine gets stuck doing an upgrade, we want it to abandon the upgrade and go back to the /bsd kernel (which hopefully has not been installed yet). Your machine is too slow. Can you scrounge up some nickels?
