linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: James.Smart@Emulex.Com
Cc: linux-scsi@vger.kernel.org, olof@austin.ibm.com,
	benh@kernel.crashing.org
Subject: Re: bad error handling in lpfc in 2.6.13
Date: Fri, 7 Oct 2005 17:10:25 +0200	[thread overview]
Message-ID: <20051007151025.GA9969@suse.de> (raw)
In-Reply-To: <20051007120707.GB32661@suse.de>

 On Fri, Oct 07, Olaf Hering wrote:

> I will move the card to another box and see how it goes. I heard the
> p520 we have is pre-GA level.

I moved it into a p660 and SP3 works ok there.

-- 
short story of a lazy sysadmin:
 alias appserv=wotan

  reply	other threads:[~2005-10-07 15:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9BB4DECD4CFE6D43AA8EA8D768ED51C21D7AE0@xbl3.ma.emulex.com>
2005-10-07 12:07 ` bad error handling in lpfc in 2.6.13 Olaf Hering
2005-10-07 15:10   ` Olaf Hering [this message]
2005-10-06 22:24 Olaf Hering
2005-10-06 22:32 ` Benjamin Herrenschmidt

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=20051007151025.GA9969@suse.de \
    --to=olh@suse.de \
    --cc=James.Smart@Emulex.Com \
    --cc=benh@kernel.crashing.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=olof@austin.ibm.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 NNTP newsgroup(s).