From: Andrew Vasquez <praka@san.rr.com>
To: linux-kernel@vger.kernel.org
Cc: Michael Clark <michael@metaparadigm.com>,
J Sloan <joe@tmsusa.com>,
GrandMasterLee <masterlee@digitalroadkill.net>,
Simon Roscic <simon.roscic@chello.at>,
Arjan van de Ven <arjanv@redhat.com>
Subject: Re: [Kernel 2.5] Qlogic 2x00 driver
Date: Wed, 16 Oct 2002 18:59:03 -0700 [thread overview]
Message-ID: <20021017015903.GA20960@praka.local.home> (raw)
In-Reply-To: <20021016054035.GM15552@clusterfs.com>
On Tue, 15 Oct 2002, Andreas Dilger wrote:
> On Oct 16, 2002 13:28 +0800, Michael Clark wrote:
> > Every one i was getting oops when used with a combination
> > of ext3, LVM1 and qla2x00 driver.
> >
> > Since taking LVM1 out of the picture, my oopsing problem has
> > gone away. This could of course not be LVM1's fault but the
> > fact that qla driver is a stack hog or something - i don't have
> > enough information to draw any conclusions all at the moment
> > i'm too scared to try LVM again (plus the time it takes to
> > migrate a few hundred gigs of storage).
>
> Yes, we have seen that ext3 is a stack hog in some cases, and I
> know there were some fixes in later LVM versions to remove some
> huge stack allocations. Arjan also reported stack problems with
> qla2x00, so it is not a surprise that the combination causes
> problems.
>
The stack issues were a major problem in the 5.3x series driver. I
believe, I can check tomorrow, 5.38.9 (the driver Dell distributes)
contains fixes for the stack clobbering -- qla2x00-rh1-3 also contain
the fixes.
IAC, I believe the support tech working with MasterLee had asked
for additional information regarding the configuration as well as
some basic logs. Ideally we'd like to setup a similiar configuration
in house and see what's happening...
--
Andrew Vasquez | praka@san.rr.com |
DSS: 0x508316BB, FP: 79BD 4FAC 7E82 FF70 6C2B 7E8B 168F 5529 5083 16BB
next prev parent reply other threads:[~2002-10-17 1:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 19:20 Simon Roscic
2002-10-15 19:31 ` Arjan van de Ven
2002-10-15 19:53 ` Simon Roscic
2002-10-16 2:51 ` Michael Clark
2002-10-16 3:56 ` GrandMasterLee
2002-10-16 4:30 ` Michael Clark
2002-10-16 4:35 ` J Sloan
2002-10-16 4:43 ` GrandMasterLee
2002-10-16 6:03 ` Michael Clark
2002-10-16 6:31 ` GrandMasterLee
2002-10-16 6:40 ` Michael Clark
2002-10-16 6:48 ` GrandMasterLee
2002-10-16 6:59 ` Michael Clark
2002-10-16 4:58 ` GrandMasterLee
2002-10-16 5:28 ` Michael Clark
2002-10-16 5:40 ` Andreas Dilger
2002-10-17 1:59 ` Andrew Vasquez [this message]
2002-10-17 2:44 ` GrandMasterLee
2002-10-17 3:11 ` Andrew Vasquez
2002-10-17 3:42 ` GrandMasterLee
2002-10-17 9:40 ` Michael Clark
2002-10-18 6:45 ` GrandMasterLee
2002-10-16 16:28 ` Simon Roscic
2002-10-16 16:49 ` Michael Clark
2002-10-17 3:12 ` GrandMasterLee
2002-10-17 3:54 ` Michael Clark
2002-10-17 4:08 ` GrandMasterLee
2002-10-17 5:03 ` Michael Clark
2002-10-16 5:02 ` GrandMasterLee
2002-10-16 16:38 ` Simon Roscic
2002-10-17 3:08 ` GrandMasterLee
2002-10-17 17:47 ` Simon Roscic
2002-10-18 6:42 ` GrandMasterLee
2002-10-18 15:11 ` Simon Roscic
2002-10-19 2:17 rwhron
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=20021017015903.GA20960@praka.local.home \
--to=praka@san.rr.com \
--cc=arjanv@redhat.com \
--cc=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
--cc=michael@metaparadigm.com \
--cc=simon.roscic@chello.at \
/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
all inboxes | Powered by JetHome®