public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Warne <nick@linicks.net>
To: Ryan Richter <ryan@tau.solarneutrino.net>
Cc: Erik Mouw <erik@harddisk-recovery.com>, linux-kernel@vger.kernel.org
Subject: Re: Random reboots
Date: Tue, 14 Feb 2006 14:47:08 +0000	[thread overview]
Message-ID: <7c3341450602140647s6acad767k@mail.gmail.com> (raw)
In-Reply-To: <20060214132904.GI16566@tau.solarneutrino.net>

 > During the years I've had this machine, I've experienced at least 10-15
> strange kernel bugs that only happened on this machine.  Each and every
> time I was *convinced* that the hardware was at fault (and people on the
> mailing list suggested it) until either a kernel came out that fixed the
> problem or a kernel developer positively identified it as a kernel
> problem and eventually fixed it.  This machine just seems to be a magnet
> for kernel bugs.

OK, reference to the similar issues I have seen on 2 boxes here at
work (ukqip01 & 02), I have dug out an old mail I sent to colleague
after the 3 time it happened to me:



"In fact it has happened to both of them now.  UKQIP01 restarted once
(about 3 years) ago in the middle of the night, then about 6 months
later UKQIP02 did the same.  If you remember I then replaced memory
from 512 to 1024.

Now UKQIP02 has done it again.

I am not too concerned, as twice in 3 years is not really a problem
(yet), but I am more curious as to why because I want to fix it.

It also only happens in the dead twilight hours too.

I will look at running memtest, but as you know that takes hours and
the box will have to taken down for the duration.

I will keep you informed."



This was last September 2005 - the time it happened before that was
Janurary 2005.

Very strange.

Nick

  reply	other threads:[~2006-02-14 14:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 21:04 Random reboots Ryan Richter
2006-02-13 21:10 ` anders
2006-02-13 21:22   ` Ryan Richter
     [not found]     ` <7c3341450602131332x2fcd7d8co@mail.gmail.com>
2006-02-13 21:39       ` Ryan Richter
2006-02-13 21:49         ` Ryan Richter
2006-02-14  8:54           ` Erik Mouw
2006-02-14 13:29             ` Ryan Richter
2006-02-14 14:47               ` Nick Warne [this message]
2006-02-14 22:22               ` Jean Delvare
2006-02-15 14:28                 ` Ryan Richter
2006-02-15 15:11                   ` linux-os (Dick Johnson)
2006-02-15 15:13                     ` Ryan Richter
2006-02-15 15:41                   ` Jean Delvare
2006-02-15 16:00                     ` Ryan Richter
2006-02-15 16:20                       ` Jean Delvare
2006-02-15 16:30                         ` Ryan Richter
2006-02-15 18:46                         ` Ryan Richter
2006-02-27 20:35                         ` Ryan Richter
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24 16:18 random reboots Nathan Walp
2001-04-26  1:36 ` Petr Vandrovec
2001-04-26  1:52   ` Nathan Walp

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=7c3341450602140647s6acad767k@mail.gmail.com \
    --to=nick@linicks.net \
    --cc=erik@harddisk-recovery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@tau.solarneutrino.net \
    /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