Help with silent reboot of 10.3-stable system

[Bob Willcox]

Just to follow up on this. I updated the system to r314889 nearly a week ago
and it hasn't rebooted since. No real idea if this had anything to do with it
or not.

The other thing that I did is order new hardware and start building a
replacement system. Maybe that was it! :)

Bob

On Wed, Mar 08, 2017 at 08:05:55PM +0200, Andrii Stesin wrote:
> I bet for faulty RAM module
> 
> On Mar 8, 2017 19:47, "Rodney W. Grimes" <freebsd-rwg at pdx.rh.cn85.dnsmgr.net>
> wrote:
> 
> > > Is your system swapping to disk? Heavily?
> > >
> > > Might want to check the swap space on disk.
> > >
> > > I had spontaneous reboots some years ago because of bad swap space on
> > > disk. (Got a new disk, 'dd'-ed the old disk to the new disk, reboot on
> > > the new disk and everything was fine)
> > >
> > > Jan
> >
> > Good possibilty too, though usually this one causes console message
> > to be spewed out and evetually a swap pager panic.  Though no evidence
> > is left behind beccase the disk couldnt be used to indicate an issue.
> >
> > Your probably not around the console when this happens Bob?
> > It may be possible to hook up a serial console and capture
> > the panic if it is happening.
> >
> > There are other failue modes that leave no on disk trace as well,
> > but well spit out a panic to a serial console.
> >
> > > On 03/07/2017 20:56, Bob Willcox wrote:
> > > > Over the past month or so my network fileserver system (NFS support
> > for my
> > > > entire, small, network) has begun silently rebooting itself. Here is
> > the uname
> > > > -a output:
> > > >
> > > > FreeBSD vader.immure.com 10.3-STABLE FreeBSD 10.3-STABLE #15 r313997:
> > Mon Feb 20 14:40:00 CST 2017     bob at vader.immure.com:/usr/obj/usr/src/sys/GENERIC
> > amd64
> > > >
> > > > At first I suspected that it might be the power supply as it was a
> > couple of
> > > > years old so I replaced that. Unfortunately, it has begun doing it
> > again (had
> > > > a couple of weeks respite) so now my suspicions seem to have been
> > incorrect.
> > > >
> > > > I was hoping that someone might be able to give me some clues on what
> > I can do
> > > > to reveal the problem. Are there any general debug settings for the
> > kernel (or
> > > > elsewhere) that would maybe give an indication of why it is being
> > rebooted
> > > > (assuming it's a software problem)?
> > > >
> > > > Thanks for any suggestions you may have!
> > > >
> > > > Bob
> > > >
> > >
> > > _______________________________________________
> > > freebsd-hackers at freebsd.org mailing list
> > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@
> > freebsd.org"
> > >
> >
> > --
> > Rod Grimes
> > rgrimes at freebsd.org
> > _______________________________________________
> > freebsd-hackers at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"
> >
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"

-- 
Bob Willcox    | If a program is useful, it will be changed.
bob at immure.com |
Austin, TX     |