From: Michael Clark <michael@metaparadigm.com>
To: J Sloan <joe@tmsusa.com>
Cc: GrandMasterLee <masterlee@digitalroadkill.net>,
Simon Roscic <simon.roscic@chello.at>,
Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Kernel 2.5] Qlogic 2x00 driver
Date: Wed, 16 Oct 2002 13:28:40 +0800 [thread overview]
Message-ID: <3DACF908.70207@metaparadigm.com> (raw)
In-Reply-To: 3DACEC85.3020208@tmsusa.com
LVM1 tried in numerous versions of 2.4.x both aa and rh version.
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).
~mc
On 10/16/02 12:35, J Sloan wrote:
> Just to make sure we are on the same page,
> was that LVM1, LVM2, or EVMS?
>
> Joe
>
> Michael Clark wrote:
>
>> I doubt it will make a difference. LVM and qlogic drivers seem
>> to be a bad mix. I've already tried the beta5 of 6.01
>> and same problem exists - ooops about every 5-8 days.
>> Removing LVM and solved the problem.
next prev parent reply other threads:[~2002-10-16 5:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 19:20 [Kernel 2.5] Qlogic 2x00 driver 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 [this message]
2002-10-16 5:40 ` Andreas Dilger
2002-10-17 1:59 ` Andrew Vasquez
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
-- strict thread matches above, loose matches on Subject: below --
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=3DACF908.70207@metaparadigm.com \
--to=michael@metaparadigm.com \
--cc=arjanv@redhat.com \
--cc=joe@tmsusa.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterlee@digitalroadkill.net \
--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