Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Chris Maness
I have commented out the lines that load kernel modules for
virtualbox, and made sure they were gone with kldstat.  However I am
still getting VERY infrequent spontaneous reboots.  So it is not the
modules.  I am thinking hardware.  It has a temperature alarm that
sounds when it is hot, but since I have cleaned it out I have not had
any issues with heat.  I am thinking bad processor/ram.  It is
behaving the same way before/after the upgraded to the latest release.
 What do you guys think?

Regards,
Chris Maness
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread C. P. Ghost
On Tue, Aug 24, 2010 at 7:29 PM, Chris Maness ch...@chrismaness.com wrote:
 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat. However I am
 still getting VERY infrequent spontaneous reboots. So it is not the
 modules. I am thinking hardware. It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat. I am thinking bad processor/ram. It is
 behaving the same way before/after the upgraded to the latest release.
 What do you guys think?

Unless you're using ECC RAM, bad RAM should still be #1 on your
watchlist, closely followed by bad PSU. Even RAM that worked fine in
the past can start exhibiting bit errors a few years later (maybe due
to mechanical stress, i.e. vibrations or frequent temperature
differences?) and esp. el cheapo PSUs have the tendency to degrade
over time.

Of course, a software bug may always be possible. Have you tried to
get a core dump? If so, does the error always happen at the same place
(backtrace / bt is your friend)? If the error keeps occurring at
different locations, it's almost always dodgy hardware.

 Regards,
 Chris Maness

-cpghost.

-- 
Cordula's Web. http://www.cordula.ws/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Robert Bonomi
 From owner-freebsd-questi...@freebsd.org  Tue Aug 24 12:29:16 2010
 Date: Tue, 24 Aug 2010 10:29:27 -0700
 From: Chris Maness ch...@chrismaness.com
 To: freebsd-questions@freebsd.org
 Subject: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat. However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?

I think its 100% certain that it is hardware, or software.  *GRIN*

You can try randomly replacing things, which can be expensive, time-
consuming, and not necessarily effective -- how do you *KNOW* that the
parts you're putting _IN_ do not, themselves, have (as-yet undiscovered)
problems?

I'd try to make the box tell me something about *why* it crashed.

crank up the level of logging for 'kernel' events in syslog.con,
enable crash dumps, and make sure the boot process saves the dump 
Then you can get into the weird,wonderful, world of 'crash dump'
analysis.

With a few dumps in hand, you can begin to see if there is any consistency
in what the machine was doing -when- it crashed.

Happy hunting

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Chris Maness
On Tue, Aug 24, 2010 at 12:47 PM, Robert Bonomi
bon...@mail.r-bonomi.com wrote:
 From owner-freebsd-questi...@freebsd.org  Tue Aug 24 12:29:16 2010
 Date: Tue, 24 Aug 2010 10:29:27 -0700
 From: Chris Maness ch...@chrismaness.com
 To: freebsd-questions@freebsd.org
 Subject: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat. However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?

 I think its 100% certain that it is hardware, or software.  *GRIN*

 You can try randomly replacing things, which can be expensive, time-
 consuming, and not necessarily effective -- how do you *KNOW* that the
 parts you're putting _IN_ do not, themselves, have (as-yet undiscovered)
 problems?

 I'd try to make the box tell me something about *why* it crashed.

 crank up the level of logging for 'kernel' events in syslog.con,
 enable crash dumps, and make sure the boot process saves the dump
 Then you can get into the weird,wonderful, world of 'crash dump'
 analysis.

 With a few dumps in hand, you can begin to see if there is any consistency
 in what the machine was doing -when- it crashed.

 Happy hunting


When I looked at the regular level kernel log, it seemed  to be out of
the clear blue.  I am an experienced user, but I am not sure if I have
the programing skills to look at debug output to find a fault.  I
might need a bit of hand holding on this one.  I looked at backtrace
to.  I was thinking it was a command or something, but it looks like
some debugging procedure.

Regards,
Chris Maness
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Manolis Kiagias
On 24/08/2010 10:58 μ.μ., Chris Maness wrote:
 On Tue, Aug 24, 2010 at 12:47 PM, Robert Bonomi
 bon...@mail.r-bonomi.com wrote:
   
 From owner-freebsd-questi...@freebsd.org  Tue Aug 24 12:29:16 2010
 Date: Tue, 24 Aug 2010 10:29:27 -0700
 From: Chris Maness ch...@chrismaness.com
 To: freebsd-questions@freebsd.org
 Subject: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat. However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?
   
 I think its 100% certain that it is hardware, or software.  *GRIN*

 You can try randomly replacing things, which can be expensive, time-
 consuming, and not necessarily effective -- how do you *KNOW* that the
 parts you're putting _IN_ do not, themselves, have (as-yet undiscovered)
 problems?

 I'd try to make the box tell me something about *why* it crashed.

 crank up the level of logging for 'kernel' events in syslog.con,
 enable crash dumps, and make sure the boot process saves the dump
 Then you can get into the weird,wonderful, world of 'crash dump'
 analysis.

 With a few dumps in hand, you can begin to see if there is any consistency
 in what the machine was doing -when- it crashed.

 Happy hunting

 
 When I looked at the regular level kernel log, it seemed  to be out of
 the clear blue.  I am an experienced user, but I am not sure if I have
 the programing skills to look at debug output to find a fault.  I
 might need a bit of hand holding on this one.  I looked at backtrace
 to.  I was thinking it was a command or something, but it looks like
 some debugging procedure.

 Regards,
 Chris Maness
   

If the reboot is so abrupt and sudden that nothing is logged (like
someone pressing the reset button), it is most probably hardware.
As others have said the most usual culprits are RAM and power supply. If
you have any spare parts at hand, it may be worth the effort to try with
an other power supply.
If the reboot happens when the system is stressed (lots of disk activity
and/or high power consumption by the CPU, like when portupgrading) the
power supply is even more suspect.
Bad RAM usually causes error messages and dumps to appear rather than
out of the blue reboots. Since it is unlikely that the same program will
always be in the faulty area of memory each time, the dumps will not be
consistent - will seem to be caused by entirely different apps. It is
still worthy to at least take out the RAM modules and clean the contacts
before reinstalling. Use rubbing alcohol (a pen eraser is also good for
gold plated contacts). Many RAM problems on older systems are definitely
caused by dust and corrosion on these contacts.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Reko Turja
When I looked at the regular level kernel log, it seemed  to be out 
of

the clear blue.


I've seen once behaviour like this on FreeBSD and it was caused by 
faulty ECC memory comb. Incorrectable CRC error just caused a 
diagnosis beep sequence and then machine shut down immediately after.


-Reko 


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Frank Shute
On Tue, Aug 24, 2010 at 10:29:27AM -0700, Chris Maness wrote:

 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat.  However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?
 
 Regards,
 Chris Maness

Sounds to me like power supply. Is the machine on a UPS? Have you
checked out the power leads are properly seated? Have these reboots
started to happen after you cleaned it out?


Regards,

-- 

 Frank

 Contact info: http://www.shute.org.uk/misc/contact.html


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Ryan Coleman
I was thinking that, maybe, it's the PSU itself.  Does the fan work? Do you 
have the ability to get temperatures inside your computer? Get those to poll 
every minute or so and write to a flat file?

--
Ryan

On Aug 24, 2010, at 4:02 PM, Frank Shute wrote:

 On Tue, Aug 24, 2010 at 10:29:27AM -0700, Chris Maness wrote:
 
 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat.  However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?
 
 Regards,
 Chris Maness
 
 Sounds to me like power supply. Is the machine on a UPS? Have you
 checked out the power leads are properly seated? Have these reboots
 started to happen after you cleaned it out?
 
 
 Regards,
 
 -- 
 
 Frank
 
 Contact info: http://www.shute.org.uk/misc/contact.html
 
 
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Spontaneous Reboots (I thought it was Virtualbox Kernel Modules)

2010-08-24 Thread Mark Atkinson
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 08/24/10 10:29, Chris Maness wrote:
 I have commented out the lines that load kernel modules for
 virtualbox, and made sure they were gone with kldstat.  However I am
 still getting VERY infrequent spontaneous reboots.  So it is not the
 modules.  I am thinking hardware.  It has a temperature alarm that
 sounds when it is hot, but since I have cleaned it out I have not had
 any issues with heat.  I am thinking bad processor/ram.  It is
 behaving the same way before/after the upgraded to the latest release.
  What do you guys think?

You can try the following ( I believe this is in 8-STABLE )

echo 'hw.mca.enabled=1'  /boot/loader.conf

and reboot.   If it's hardware supported machine check exception, then
you may see which component has an issue on the console in the machine
check output.

- -Mark
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkx0N74ACgkQrDN5kXnx8yZfSgCeIrd2qXmatERuOhPwW2W6cqY0
FtEAnj3154huE/8aVl5W3zA22YjNw2UL
=p002
-END PGP SIGNATURE-

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org