public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Lloyd <dlloyd@exegy.com>
To: "Brett G. Durrett" <brett@imvu.com>
Cc: Sumant.Patro@lsil.com, Sreenivas.Bagalkote@lsil.com,
	lkml <linux-kernel@vger.kernel.org>,
	Berkley Shands <bshands@exegy.com>
Subject: Re: megaraid_sas waiting for command and then offline
Date: Wed, 06 Sep 2006 09:11:47 -0500	[thread overview]
Message-ID: <44FED723.5050107@exegy.com> (raw)
In-Reply-To: <44FE536C.8080000@imvu.com>

Brett G. Durrett wrote:
 >
 > I have the same or a similar issue running 2.6.17 SMP x86_64 - the
 > megaraid_sas driver hangs waiting for commands and then the filesystem
 > unmounts, leaving the machine in an unusable state until there is a hard
 > reboot (the machine is responsive but any access, shell or otherwise, is
 > impossible without the filesystem).  While I do not have much debugging
 > information available, this happens to me about once every 6-7 days in
 > my pool of seven machines, so I can probably get debugging info.  Since
 > the disk is offline and I can't get remote console, I don't have any
 > details except something similar to Dave Lloyd's post, below.
 >
 > The only thing that the machines with these failures seem to have in
 > common is the fact that they are almost exclusively writes - they are
 > slave database machines with large memory and pretty much just
 > replicate.  The read/write machines seem to have less failures.
 >
 > I am happy to help provide debugging information in any reasonable way.
 > In the mean time, if there are any known suggestions or workarounds for
 > the problem, I would be grateful for the guidance.
 >
 > Here are what details on the controller.  If you want additional info,
 > let me know exactly what you need and I will do what I can to get it to
 > you.:
 >
 > Product Name    : PERC 5/i Integrated
 > Serial No       : 12345
 > FW Package Build: 5.0.1-0030
 > FW Version      : 1.00.01-0088
 > BIOS Version    : MT23
 > Ctrl-R Version  :1.02-007
 >
 > B-

Which motherboard are you using?  We believe that this may be a
motherboard specific issue.  It appears to happen on a SuperMicro
motherboard but not a Tyan motherboard.

-- 
Dave Lloyd
Test Engineer, Exegy, Inc.
314.450.5342
dlloyd@exegy.com

  reply	other threads:[~2006-09-06 14:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06  4:49 megaraid_sas waiting for command and then offline Brett G. Durrett
2006-09-06 14:11 ` Dave Lloyd [this message]
2006-09-06 16:04   ` Brett G. Durrett
  -- strict thread matches above, loose matches on Subject: below --
2006-09-06 17:14 Patro, Sumant
2006-09-06 20:44 ` Brett G. Durrett
2006-10-25  8:46 David N. Welton
2006-10-25 22:48 ` Brett G. Durrett
2006-10-25 23:03   ` Alan Cox
2006-11-13 21:40   ` Brett G. Durrett

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=44FED723.5050107@exegy.com \
    --to=dlloyd@exegy.com \
    --cc=Sreenivas.Bagalkote@lsil.com \
    --cc=Sumant.Patro@lsil.com \
    --cc=brett@imvu.com \
    --cc=bshands@exegy.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