linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: akpm@linux-foundation.org, James.Bottomley@HansenPartnership.com,
	linux-scsi@vger.kernel.org, James.Bottomley@SteelEye.com, "Patro,
	Sumant" <Sumant.Patro@lsi.com>
Subject: Re: [patch 02/17] Dell CERC support for megaraid_mbox
Date: Mon, 07 Apr 2008 14:44:40 +0200	[thread overview]
Message-ID: <47FA1738.4020909@suse.de> (raw)
In-Reply-To: <9738BCBE884FDB42801FAD8A7769C26502085504@NAMAIL1.ad.lsil.com>

Yang, Bo wrote:
> Hannes,
> 
> We can not find out why need to disable the random deletion of the
> logical drive for the FW version>=6.62?  Where is the 6.62 come from?
> 
From the bug reports we had. Dell machines with a fw rev < 6.61 work
with this driver, whereas newer rev (the said 6.62) don't.
As to the details: No idea. This is just what I found by comparing
the older megaraid driver (which worked, but is unsupported) and the
newer megaraid_mbox driver.
The noticeable difference was just the random deletion feature.
As I don't have any details about the driver I certainly can't
tell you any details. This is a workaround.
But as Dell (or LSI, for that matter) refuse to update the
BIOS on these drivers we're stuck with it.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2008-04-07 12:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-28 21:48 [patch 02/17] Dell CERC support for megaraid_mbox akpm
2008-03-30 17:13 ` James Bottomley
2008-03-31 14:33   ` Yang, Bo
2008-04-02 21:48 ` Yang, Bo
2008-04-07 12:44   ` Hannes Reinecke [this message]
2008-04-14 15:56     ` Yang, Bo

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=47FA1738.4020909@suse.de \
    --to=hare@suse.de \
    --cc=Bo.Yang@lsi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Sumant.Patro@lsi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).