From: Phil Dier <phil@icglink.com>
To: linux-kernel@vger.kernel.org
Cc: ziggy@icglink.com, scott@icglink.com, jack@icglink.com
Subject: Re: Dual 2.8ghz xeon, software raid, lvm, jfs
Date: Wed, 10 Aug 2005 10:36:40 -0500 [thread overview]
Message-ID: <20050810103640.105a2ea2.phil@icglink.com> (raw)
In-Reply-To: <20050809230530.GA22211@kevlar.burdell.org>
On Tue, 9 Aug 2005 19:05:30 -0400
Sonny Rao <sonny@burdell.org> wrote:
>
> Generally on lkml, you want to post at least the output of an oops or
> panic into your post.
Okay, I'll keep this in mind for future posts. Thanks.
> Now, try running 2.6.13-rc6 and see if it fixes your problem, IIRC
> there have been a number of changes to the MPT driver between those two
> kernel versions.
Thanks for the suggestion. I'll give it a try and see if it passes the
test.
--
Phil Dier (ICGLink.com -- 615 370-1530 x733)
/* vim:set noai nocindent ts=8 sw=8: */
prev parent reply other threads:[~2005-08-10 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 14:44 Phil Dier
2005-08-09 23:05 ` Sonny Rao
2005-08-10 15:36 ` Phil Dier [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=20050810103640.105a2ea2.phil@icglink.com \
--to=phil@icglink.com \
--cc=jack@icglink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=scott@icglink.com \
--cc=ziggy@icglink.com \
/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
Powered by JetHome