From: Matthew Wilcox <matthew@wil.cx>
To: Tore Anderson <tore@linpro.no>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, James.Smart@Emulex.Com
Subject: Re: Linux 2.6.23-rc3
Date: Tue, 14 Aug 2007 05:24:30 -0600 [thread overview]
Message-ID: <20070814112429.GL16277@parisc-linux.org> (raw)
In-Reply-To: <46C1717E.3030908@linpro.no>
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
--
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-08-14 11:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 4:50 Linux 2.6.23-rc3 Linus Torvalds
2007-08-13 6:25 ` Michal Piotrowski
2007-08-13 12:23 ` Zilvinas Valinskas
2007-08-13 16:49 ` Michal Piotrowski
2007-08-14 10:14 ` Zilvinas Valinskas
2007-08-14 10:10 ` Zilvinas Valinskas
2007-08-14 9:10 ` Tore Anderson
2007-08-14 11:24 ` Matthew Wilcox [this message]
2007-08-14 13:04 ` James Smart
[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=20070814112429.GL16277@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Smart@Emulex.Com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.