public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Matthew Galgoci <mgalgoci@redhat.com>
To: overseers@sources.redhat.com
Subject: Re: mysterious reboots
Date: Thu, 08 Apr 2004 18:06:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0404081351360.447-100000@lacrosse.corp.redhat.com> (raw)
In-Reply-To: <20040408180316.7F2A4E3A67@foam.wonderslug.com>

On Thu, 8 Apr 2004, Angela Marie Thomas wrote:
> This is the second or third time in recent memory that the system
> has mysteriously rebooted with no one owning up to doing it.
> I'm very concerned about this.  Every time there's a mysterious
> reboot, I have to prepare for the potential for a complete system
> reload from backups or at the very least some kind of verification
> that the files are OK.

The system appears to have locked up just before 6am EDT. I power cycled
it remotely around 7:30am EDT. Frank was on the box just after it came
up and I assumed he would take a look at things.

Fwiw, I watched the raid array start up via remote serial console:

[snip]
Dell PowerEdge Expandable RAID Controller 3/Di, BIOS V2.7-0 [Build 3546]
(c) 1998-2001 Adaptec, Inc. All Rights Reserved.
                                                                                
    Press <Ctrl><A> for Configuration Utility!
Waiting for Array Controller #0 to start.... \
                                                                                
Array Controller started
Controller monitor V2.7-0, Build 3546
Controller kernel  V2.7-0, Build 3546
Controller POST operation successful
[end snip]

Note the lack of error messages concerning a failed disk or running in 
degraded mode.

I do know that there are open issues with the aacraid driver that manifest
as random hard locks, sometime occuring infrequently, other times the driver
doesn't last a week. It depends on the version of the aacraid hardware and
also the version of the aacraid firmware.

For more info: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=92129

Filtering out the crap, it looks like Adaptec has the problem fixed in the
latest version of the driver.

-- 
Matthew Galgoci
System Administrator and Sr. Manager of Ruminants
Red Hat, Inc
919.754.3700 x44155

  parent reply	other threads:[~2004-04-08 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08 17:46 Angela Marie Thomas
2004-04-08 17:54 ` Frank Ch. Eigler
2004-04-08 18:17   ` Angela Marie Thomas
2004-04-08 18:06 ` Matthew Galgoci [this message]
2004-04-08 18:19   ` Matthew Galgoci
2004-04-08 18:42   ` Jonathan Larmour
2004-04-08 18:47     ` Matthew Galgoci

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=Pine.LNX.4.44.0404081351360.447-100000@lacrosse.corp.redhat.com \
    --to=mgalgoci@redhat.com \
    --cc=overseers@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).