Date: Sat, 14 Apr 2012 11:07:28 +0200 From: Jeremie Le Hen <jeremie@le-hen.org> To: Alexander Best <arundel@freebsd.org> Cc: freebsd-current@freebsd.org Subject: Re: howto debug a complete hard reset Message-ID: <20120414090728.GA8798@felucia.tataz.chchile.org> In-Reply-To: <20120413213644.GA92873@freebsd.org> References: <20120413213644.GA92873@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Alexander,
On Fri, Apr 13, 2012 at 09:36:44PM +0000, Alexander Best wrote:
>
> i'm running HEAD on amd64 and experienced some really annoying resets during
> the last couple of months.
>
> when i do 'sysctl -a' or 'sysctl -a|grep bla', my whole system does a hard
> reset. no core dump gets produced.
>
> isn't there a way to find out which sysctl variable is causing the reset?
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.
When your computer will be reset, the culprit will obviously not be
written to this file, but the previous one will. You can then look at
the output of sysctl -Na to see which one is causing the reboot.
Regards,
--
Jeremie Le Hen
Men are born free and equal. Later on, they're on their own.
Jean Yanne
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120414090728.GA8798>