mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Steven Pritchard <steve@silug.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3ware driver errors
Date: Mon, 24 Mar 2003 18:01:07 -0700	[thread overview]
Message-ID: <20030324180107.A14746@vger.timpanogas.org> (raw)
In-Reply-To: <20030324212813.GA6310@osiris.silug.org>; from steve@silug.org on Mon, Mar 24, 2003 at 03:28:13PM -0600



There is a firmware upgrade you need to obtain from WD if you are using their 
drives with a 3Ware controller.  The WD drives were optimized for desktop use
and they go into a "powersave" mode of sorts which will cause them to disappear
and reappear mysteriously with all sorts of strange errors.  WD is aware of 
this problem and so is 3Ware.

Jeff

On Mon, Mar 24, 2003 at 03:28:13PM -0600, Steven Pritchard wrote:
> (Apparently 3w-xxxx in the Subject gets caught as spam.  Somebody
> might want to adjust that regular expression.  :-)
> 
> I have a server that is locking up every day or two with a console
> full of this error:
> 
>     3w-xxxx: scsi0: Command failed: status = 0xcb, flags = 0x37, unit #0.
> 
> This is on a Dell PowerEdge 1400SC (dual PIII/1.13GHz, 1.1GB RAM),
> with a 3ware Escalade 7000-2 and two WD1600JB drives, running Red Hat
> 8.0 with kernel-smp 2.4.18-27.8.0.
> 
> I plan to report this to Red Hat's bugzilla, but I'm hoping for some
> ideas or big red flags to jump out at somebody here...  I use this box
> for a UML hosting server, so all this downtime is affecting *way* too
> many people.
> 
> This box has been having other stability problems, so I'm guessing
> this might not be directly related to the 3ware card/driver.  It did
> survive a memtest86 pass.
> 
> Steve
> -- 
> steve@silug.org           | Southern Illinois Linux Users Group
> (618)398-7360             | See web site for meeting details.
> Steven Pritchard          | http://www.silug.org/
> -
> 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-03-24 23:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 21:28 Steven Pritchard
2003-03-25  1:01 ` Jeff V. Merkey [this message]
2003-03-24 23:44   ` Larry McVoy
2003-03-25  0:07     ` Mark Hahn
2003-03-25  1:25     ` Jeff V. Merkey
2003-03-25  3:12       ` Steven Pritchard
2003-03-25  3:11         ` Kevin P. Fleming
2003-03-25 15:25         ` Ezra Nugroho
2003-03-25 15:26           ` Roy Sigurd Karlsbakk
2003-03-25 16:26             ` Ezra Nugroho
2003-03-27 16:02       ` ECC error in 2.5.64 + some patches Larry McVoy
2003-03-27 16:17         ` Tim Schmielau
2003-03-27 16:27           ` Larry McVoy
2003-03-27 16:39             ` Tim Schmielau
2003-03-27 16:22         ` Randy.Dunlap
2003-03-27 16:31           ` Larry McVoy
2003-03-28  0:10             ` Dave Jones
2003-03-27 16:31         ` Dave Jones
2003-03-27 17:00         ` Chris Wedgwood
2003-03-27 17:19           ` Dominik Kubla
2003-03-27 17:25             ` Chris Wedgwood
2003-04-15  4:34               ` Bill Davidsen
2003-04-15 13:24             ` Larry McVoy
2003-03-24 21:44 3ware driver errors Adam Radford
2003-03-25  1:02 ` Jeff V. Merkey

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=20030324180107.A14746@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@silug.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

Powered by JetHome