From: tom arnall <kloro2006@gmail.com>
To: linux-newbie@vger.kernel.org
Subject: Re: system hangs momentarily every 4 mins 2 secs
Date: Sun, 27 Aug 2006 11:45:37 -0700 [thread overview]
Message-ID: <200608271145.37956.kloro2006@gmail.com> (raw)
In-Reply-To: <f68850780608262311s4e071ebpa431ca617bec9b8f@mail.gmail.com>
On Saturday 26 August 2006 23:11, Raseel Bhagat wrote:
> Hi,
>
> On 8/27/06, mike@kevino.org <mike@kevino.org> wrote:
> > On Sat, 26 Aug 2006 12:55:33 -0700
> >
> > tom arnall <kloro2006@gmail.com> wrote:
> > > My system hangs momentarily every 4 mins 2 secs. The event coincides
> > > with a 'top' entry in which 'events/0' grabs 50-95% of cpu capacity.
> > > How can I determine what is causing the event?
>
> This is a long-shot but the last time I had the same problem it turned
> out that there had developed a loose connection with the heat-sink and
> processor on the motherboard.
> As a result, the processor used to over-heat in about every 3 minutes
> or so, the watchdogs would come into picture and cause the machine to
> hang or reboot.... usually reboot.
>
> Just give a quick check on your hardware before probing into the software
> side.
how did you identify the problem with the heat sink?
is it likely that a hardware problem would cause the hanging phenomenon at
such a precise interval? i ran 'top' in batch mode to a file for ~.5 hour and
also wrote down the time whenever the hang occurred, then i compared the
output of top with the 'hang moments'. there was an exact coincidence
with 'top' entries in which 'events/0' was gobbling the cpu. and these events
occurred exactly 4 mins 2 secs from each other.
i also logged the content of /proc/interrupts at intervals of ~.2 sec's. in
this case, there was no change at the 'hang moments' except that i got only 1
sample for the second in which the hang occurred. in all other cases, of
course, i got 5 samples per second.
thanks in advance,
tom arnall
north spit, ca
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2006-08-27 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060817141403.10351.qmail@web81707.mail.mud.yahoo.com>
[not found] ` <a9d9d0c00608171240g4537142etebe10abfc512434b@mail.gmail.com>
[not found] ` <1155859868.6787.8.camel@localhost>
2006-08-26 19:55 ` system hangs momentarily every 4 mins 2 secs tom arnall
2006-08-27 1:22 ` mike
2006-08-27 6:11 ` Raseel Bhagat
2006-08-27 18:45 ` tom arnall [this message]
2006-08-27 19:26 ` Ray Olszewski
2006-08-29 18:31 ` another place where bootup messages are recorded? tom arnall
2006-08-29 21:16 ` Chuck Gelm
2006-08-29 23:35 ` Ray Olszewski
[not found] ` <20060829205333.GC1633@slug>
2006-08-30 0:40 ` tom arnall
2006-08-27 20:46 ` system hangs momentarily every 4 mins 2 secs tom arnall
[not found] ` <200608301435.12933.kloro2006@gmail.com>
[not found] ` <200608302150.k7ULo12C009621@isp2dial.com>
2006-09-03 18:38 ` tom arnall
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=200608271145.37956.kloro2006@gmail.com \
--to=kloro2006@gmail.com \
--cc=linux-newbie@vger.kernel.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