howto debug a complete hard reset
Robert Huff
roberthuff at rcn.com
Sat Apr 14 13:00:14 UTC 2012
Jeremie Le Hen writes:
> This is probably a sysctl handler that is causing the reboot. You can
> run this one-liner to spot the culprit (use sh):
>
> for i in $(sysctl -Na); do sysctl $i >> ~/sysctl.out; sync; done
>
> Each sysctl will be called in turn and the output is appended to
> a file, but the file will forcibly written to the disk before the
> next occurence.
Um ... it is my understanding sync(8) does not guarantee
pending i/o will be written before it returns, but merely requests
this happen irrespective of when it would normally occur.
An I mistaken?
Robert Huff
More information about the freebsd-current
mailing list