atom feed7 messages in org.freebsd.freebsd-currentRe: howto debug a complete hard reset
FromSent OnAttachments
Alexander BestApr 13, 2012 2:36 pm 
O. HartmannApr 13, 2012 3:40 pm 
Jeremie Le HenApr 14, 2012 2:07 am 
Alexander BestApr 14, 2012 3:23 am.Other, .Other
Robert HuffApr 14, 2012 5:59 am 
Jeremie Le HenApr 14, 2012 8:02 am 
Alexander BestApr 14, 2012 11:11 am 
Subject:Re: howto debug a complete hard reset
From:Jeremie Le Hen (jere@le-hen.org)
Date:Apr 14, 2012 8:02:30 am
List:org.freebsd.freebsd-current

On Sat, Apr 14, 2012 at 08:59:42AM -0400, Robert Huff wrote:

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?

Honestly I don't know, but I have do admit that the small paragraph in the BUGS section of the sync(2) manpage is a little bit shivering:

BUGS The sync() system call may return before the buffers are completely flushed.

Can any enlightened person answer this?

Men are born free and equal. Later on, they're on their own. Jean Yanne