From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] spontaneous reboots.. what to look for
Date: Sun, 15 Feb 2009 17:42:44 -0600 [thread overview]
Message-ID: <87wsbrs1vv.fsf@newsguy.com> (raw)
I've been experiencing spontaneous reboots on one gentoo machine
lately. Looking thru /var/log/messages... I see the restarts but
looking above that... I'm not seeing anything I recognize as being a
culprit.
Its been happening for a few weeks... but I've been busy and only now
digging into it ( The machine is no kind of server ).
It appears to only happen in X (I'm using xfce4) and I've only noticed
it since I started running 2.6.28 kernels. Although I couldn't say
that it seemed to be directly related.
I mean I didn't boot into 2.6.28 and suddenly notice spontaneous
rebooting.
It does not appear to be heat realated... but I am only now using
lm_sensors to keep an accurate record and see if there appears to be a
relationship.
I've had two today so either its happening more often or I'm just
spending more time on that machine.
It may also be on the first or second time its happened while I as
actually right at the keyboard.
I'm sorry to be so vague about it, but in truth, I've been pretty lazy
about it... since no real harm comes of an unexpected reboot on that
machine (so far anyway). But clearly something that has to be figured
out.
The only things I've checked so far...
1) browsing thru /var/log/messages (Having trouble recognizing any
thing that looks suspicious.
I have noticed what appears to be a time/date anomaly where the
progression of time is suddenly irregular. That is, an earlier
time shows up amongst some later times.
It appears to have been me sudoing to visudo. And apparently
having /etc/sudoers open long enough for the closing of it to be
earlier than other events taking place.
Again ... I'm not real sure exactly what happened there but it
does not appear to coincide with a reboot anyway.
2) checking how hot the cpu is getting (Doesn't appear to be a
problem) But now running a cron job recording temperatures every 10
minutes. So that may turn up something.
3) checking for overfilled disks. (none show in df -h)
next reply other threads:[~2009-02-15 23:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 23:42 Harry Putnam [this message]
2009-02-15 23:56 ` [gentoo-user] spontaneous reboots.. what to look for Mark Knecht
2009-02-16 0:26 ` [gentoo-user] " Harry Putnam
2009-02-16 1:01 ` Mark Knecht
2009-02-16 0:26 ` [gentoo-user] " Dale
2009-02-16 0:16 ` Volker Armin Hemmann
2009-02-16 0:22 ` Saphirus Sage
2009-02-16 17:30 ` [gentoo-user] " Harry Putnam
2009-02-16 17:55 ` Mark Knecht
2009-02-16 17:57 ` Volker Armin Hemmann
2009-02-16 17:59 ` Stroller
2009-02-16 17:59 ` Joseph Davis
2009-02-16 0:57 ` [gentoo-user] " Neil Bothwick
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=87wsbrs1vv.fsf@newsguy.com \
--to=reader@newsguy.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