From: James Smart <James.Smart@Emulex.Com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tore Anderson <tore@linpro.no>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, James Smart <James.Smart@Emulex.Com>
Subject: Re: Linux 2.6.23-rc3
Date: Tue, 14 Aug 2007 09:04:38 -0400 [thread overview]
Message-ID: <46C1A866.5090903@emulex.com> (raw)
In-Reply-To: <20070814112429.GL16277@parisc-linux.org>
A little more....
The -EEXIST matches http://marc.info/?l=linux-scsi&m=117699334422336&w=2
I had a bug fix at http://marc.info/?l=linux-scsi&m=117856436302690&w=2
Mathew's fix below superceeded my patch and supposedly also corrects it.
-- james s
PS: Emulex's testing has been with my fix. We haven't tested Mathew's yet.
Matthew Wilcox wrote:
> On Tue, Aug 14, 2007 at 11:10:22AM +0200, Tore Anderson wrote:
>> I gave it a spin, and got quite a few troubles that appears related to
>> the lpfc driver. I don't know if these problems happened due to the
>> recent update as the latest kernel I ran before was 2.6.20 (where I
>> never saw problems like these). First I see that something failed when
>> the volumes on the SAN (on a Sun StorageTek 6140 / Engenio 3994) is
>> registered, causing two errors errors such as:
>
> You didn't seem to include your .config, but I assume you're using async
> scanning. Could you try including this patch:
>
> http://marc.info/?l=linux-scsi&m=118289275414202&w=2
>
next prev parent reply other threads:[~2007-08-14 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.0.999.0708122143240.30176@woody.linux-foundation.org>
2007-08-14 9:10 ` Linux 2.6.23-rc3 Tore Anderson
2007-08-14 11:24 ` Matthew Wilcox
2007-08-14 13:04 ` James Smart [this message]
[not found] ` <1187186897.1457.57.camel@potomac.tworiverlabs.com>
2007-08-15 14:47 ` Matthew Wilcox
2007-08-14 18:31 ` Tore Anderson
2007-08-15 12:59 ` Tore Anderson
2007-08-14 12:25 ` James Smart
2007-08-14 13:07 ` Tore Anderson
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=46C1A866.5090903@emulex.com \
--to=james.smart@emulex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=tore@linpro.no \
--cc=torvalds@linux-foundation.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