From: Tore Anderson <tore@linpro.no>
To: James.Smart@Emulex.Com
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org
Subject: Re: Linux 2.6.23-rc3
Date: Tue, 14 Aug 2007 15:07:18 +0200 [thread overview]
Message-ID: <46C1A906.9050402@linpro.no> (raw)
In-Reply-To: <46C19F57.3070801@emulex.com>
* James Smart
> I've seen these before (and they haven't been specific to the LLDD).
You're probably right. I saw trouble happening when lpfc was in
action and thought it might have something to do with it, but then
again I'm not very intimate with the inner workings of the kernel.
> If you believe these are related to the -rc3 lpfc mods, I recommend
> retesting on an -rc2 or 2.6.22 to see how similar they are.
I have no opinion if this is something that appeared in -rc3 or not as
I upgraded to it directly from 2.6.20 (which never gave me similar
problems). I'm compiling a new kernel with Matthew Wilcox' patch now,
and will try a few more reboots to see how that helped. I'll post
about my findings tomorrow.
Regards
--
Tore Anderson
prev parent reply other threads:[~2007-08-14 13:07 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
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 [this message]
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=46C1A906.9050402@linpro.no \
--to=tore@linpro.no \
--cc=James.Smart@Emulex.Com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).