public inbox for linux-hams@vger.kernel.org
 help / color / mirror / Atom feed
From: Gordon JC Pearce <gordonjcp@gjcp.net>
To: linux-hams@vger.kernel.org
Subject: Re: Problems with system lockup
Date: Thu, 18 Nov 2010 19:13:24 +0000	[thread overview]
Message-ID: <1290107604.21069.17.camel@localhost.localdomain> (raw)
In-Reply-To: <4CE573AC.1010607@radagast.org>

On Thu, 2010-11-18 at 10:42 -0800, Dave Platt wrote:

> -  Hardware problems on the motherboard, pure and simple...
>    bad DRAM, for example, or an overheating CPU due to a
>    fan failure, or overly-aggressive overclocking.  It
>    wouldn't hurt to install, and then run the stand-alone
>    MEMTEST86+ check (let it run overnight, at least) to
>    see if there are DRAM or timing problems.

This ^^^.  It smells hardware-y.  I'd be really surprised if JNOS could
do anything to hard-lock the system - typically even if something is
poking really low-level drivers the worst it will do is cause a kernel
panic.  Okay, that *will* basically lock up your system, but it should
be more informative than "just plain catatonic".

Very nearly all "just locks up" problems I've run across have been down
to dying memory or overheating CPUs.  In the past I've found that the
latter has been quite good for causing segfaults when the CPU is driven
hard, like compiling code or rendering video.

Gordon MM0YEQ


  reply	other threads:[~2010-11-18 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 17:26 Problems with system lockup kd1zd
2010-11-18 18:42 ` Dave Platt
2010-11-18 19:13   ` Gordon JC Pearce [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-11-19 13:32 kd1zd
2010-11-19 14:50 ` Gordon JC Pearce

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=1290107604.21069.17.camel@localhost.localdomain \
    --to=gordonjcp@gjcp.net \
    --cc=linux-hams@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