public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Johnson <andy@asjohnson.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Megaraid crash (Blocked mailbox......!!) with 2.4.19-aa and 2.4.20-aa
Date: Fri, 10 Jan 2003 00:13:38 -0600	[thread overview]
Message-ID: <3E1E6492.3020300@asjohnson.com> (raw)
In-Reply-To: <fa.i7lhfnc.1ulm3ac@ifi.uio.no>

Pasi Kärkkäinen wrote:
> Hello!
> 
> I've seen this at least 5 times now in one month.. One of our boxes die
> when postgresql maintenance script AND backup cron jobs are ran at the =
> same
> time (by mistake - normally they are not ran at the same time)..
> 
> So it seems to be related to high disk i/o. The adapter is 
> HP NetRAID 1M with latest firmware. There is one RAID5 array with 3 dis=
> ks
> configured to it.
> 
> Usually this crash happens 1 to 2 times a week.. always when cron start=
> s to
> run the stuff at the night. The console will be flooded with "Blocked
> mailbox......!!" text (which surprisingly means that the megaraid firmw=
> are
> has stopped responding.. according to google)
> 
> This box doesn't have high disk i/o at the daytime, only at the night w=
> hen
> cron starts to do things..
> 
> When the cron jobs are not ran at the same time, the box is stable.
> 
> 
> Other box using the same kind of adapter, but RAID1 array instead, havi=
> ng
> high disk i/o all the time doesn't have any problems.. (with the same k=
> ernels).
> 
> 
> Kernels are compiled with gcc 2.95.4 (Debian 3.0).
> 
> 
> Any thoughts?

I saw this on one of our boxes running RH 6.2 with the 2.2.16 kernel
a few times in one month.  Software doesn't get old and break, usually,
so I turned the box off, reseated all the drives, and after I turned it
back on, we never had that problem again.  I think this is one of those
intermittent hardware problems.  The kind that are the most "fun" to
solve.

Good Luck,

Andy Johnson

> 
> 
> -- Pasi Kärkkäinen
>        
>                                    ^
>                                 .     .
>                                  Linux
>                               /    -    \
>                              Choice.of.the
>                            .Next.Generation.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
>  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.tux.org/lkml/



       reply	other threads:[~2003-01-10  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.i7lhfnc.1ulm3ac@ifi.uio.no>
2003-01-10  6:13 ` Andy Johnson [this message]
2003-01-21 12:21   ` Megaraid crash (Blocked mailbox......!!) with 2.4.19-aa and 2.4.20-aa Pasi Kärkkäinen
2003-01-09 14:25 Pasi Kärkkäinen

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=3E1E6492.3020300@asjohnson.com \
    --to=andy@asjohnson.com \
    --cc=linux-kernel@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