> > Is Chrome OS, changing the default timeout from 10s to something else? > > That would explain it as a script is executed late in the boot cycle and > > explain the quick restart. > > > > Correct, Chrome OS changes the timeout from 10 to 5 seconds. > > A little experiment suggests that the problem can be triggered by updating > /proc/sys/kernel/watchdog_thresh. hardlockup_detector_perf_enable() is > called while hardlockup_detector_perf_cleanup() is running.
Ok, that makes sense then. Though I thought I tested that before acking it. I will try to duplicate that on my end and see if various solutions could work. Cheers, Don
