public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random reboots.  Where to start?
Date: Sat, 26 Feb 2011 08:28:33 -0600	[thread overview]
Message-ID: <4D690E11.90300@gmail.com> (raw)
In-Reply-To: <201102260927.31140.michaelkintzios@gmail.com>

Mick wrote:
>
> Before you start tweaking voltages and replacing PSUs you better test your
> *new* memory modules thoroughly, even if that means that you will be using
> your old machine for a day or so.
>
> Personally I usually remove all memory modules and then test one at a time
> overnight with memtest 86+.  If it gives any errors at all I would send it
> back to the shop.
>
> If they all pass, then voltage and PSU issues will need to be looked at.
>
> Good luck.
>    

This appears to be a corrupt file somewhere.  This is the current uptime:

root@fireball / # uptime
  08:22:57 up 16:02,  4 users,  load average: 0.12, 0.11, 0.13
root@fireball / #

It was rebooting after a couple hours or so before.  All I have done so 
far is basically the same as a emerge -e world.  I used the script thing 
tho.  I did the first few hundred packages from a USB stick.  Anyway, it 
appears to be working fine.  I'm hoping it stays that way too.  I don't 
want to be chasing down flakey hardware.  I like having hair.

That said, I'm going to reboot, by choice, just to make sure everything 
loaded is new.  If it lasts until tomorrow, maybe this is fixed.  I hope.

Thanks to all for the help.  Will post results tomorrow.

Dale

:-)  :-)



  reply	other threads:[~2011-02-26 15:05 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 15:33 [gentoo-user] Random reboots. Where to start? Dale
2011-02-25 16:56 ` Helmut Jarausch
2011-02-25 23:06   ` Dale
2011-02-26 15:33     ` Yohan Pereira
2011-02-26 15:46       ` Dale
2011-02-27 17:52         ` Jason Weisberger
2011-02-27 20:12           ` Dale
2011-02-27 23:32             ` Peter Humphrey
2011-02-28  1:38               ` Dale
2011-02-28  7:03           ` Dale
2011-03-01 23:25             ` Jason Weisberger
2011-03-02  0:53               ` Dale
2011-03-02 14:15                 ` Paul Hartman
2011-02-25 17:08 ` [gentoo-user] " Grant Edwards
2011-02-25 23:10   ` Dale
2011-02-26 22:20     ` walt
2011-02-26 22:40       ` Mark Knecht
2011-02-26 22:52         ` Dale
2011-02-25 17:14 ` [gentoo-user] " Mark Knecht
2011-02-25 18:03 ` Paul Hartman
2011-02-26  0:18   ` Dale
     [not found] ` <4d67fbde.83a0df0a.5870.3917@mx.google.com>
2011-02-26  0:24   ` Dale
2011-02-26  9:27     ` Mick
2011-02-26 14:28       ` Dale [this message]
2011-02-27 17:15         ` [gentoo-user] " Grant Edwards
2011-02-27 19:43           ` Mick
2011-02-27 20:23             ` Dale
2011-02-27 23:34             ` Peter Humphrey
2011-03-01 23:14               ` Mick
2011-03-01 23:51                 ` Peter Humphrey
2011-03-02 15:51                   ` Mick
2011-03-02 16:29                     ` Neil Bothwick
2011-03-02 16:37                       ` Mick
2011-03-02 16:51                         ` Neil Bothwick
2011-03-02 16:52                         ` Alex Schuster
2011-03-02 23:52                         ` Peter Humphrey
2011-02-26 16:18     ` [gentoo-user] " Volker Armin Hemmann
2011-02-27 10:02     ` Volker Armin Hemmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D690E11.90300@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox