public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jord Tanner <jord@indygecko.com>
To: linux-kernel@vger.kernel.org
Cc: brad_mssw@gentoo.org, Atulm@lsil.com
Subject: Re: [PATCH 2.6.0] megaraid 64bit fix/cleanup (AMD64)
Date: Fri, 16 Apr 2004 06:56:38 -0700	[thread overview]
Message-ID: <1082123798.11604.69.camel@gecko> (raw)


On Tue Dec 30 2003 - 16:11:40 EST Brad House wrote:

        Ok, I just ported the 2.00.9 driver to 2.6.0.
        It still has these warnings during compilation as I did not
        attempt to apply my 64bit fixes from before as I've been told
        they are just plain wrong :/
        
        But, I suppose this should work fine in 32bit mode, I would
        greatly appreciate any help in porting it for 64bit platforms.
        
        The patch can be downloaded here :
        http://dev.gentoo.org/~brad_mssw/kernel_patches/megaraid/megaraid-v2.00.9-linux2.6.patch
        And only applies to the source from ftp.lsil.com, it's not a
        kernel-patch
        per-se, but copying the result over to the drivers/scsi will
        compile inplace
        of the current versions.
        
        Please CC me on any replies!
        -Brad House <brad_mssw@xxxxxxxxxx>



This thread has been inactive for a while, but I've not found anything
more relevant to my situation. 

I'm running 2.6.3-gentoo (and 2.6.5-gentoo) with a LSILogic SATA
Megaraid 150-6 raid controller on a dual Opteron system. The entire
system is compiled in 64bit. We are seeing random database corruption
when access very large Postgres tables (more than 10 million rows).
Other than that, the system runs beautifully.

As far as I can tell, no amd64 specific patches have been applied to the
megaraid driver in 2.6.3 (version 2.00.3). Brad House has posted a 2.6
patch for megaraid 2.00.9, but his previous amd64 patches were removed.
LSI tech support has suggested I upgrade to 2.00.9, but the LSI source
is for 2.4.

So my questions are:

        - Could the 2.00.3 driver be responsible for random data
        corruption when running on 2.6.3 in 64bit?
        - Is it safe to run Brad House's 2.6 megaraid 2.00.9 patches in
        64 bit mode on amd64?
        - Are there any patches for megaraid 2.00.9 (or higher, I see
        2.00.10-3 has just been released) that combine patches for 2.6
        and amd64?
        
TIA,


-- 
Jord Tanner <jord@indygecko.com>


             reply	other threads:[~2004-04-16 13:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 13:56 Jord Tanner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-16 19:24 [PATCH 2.6.0] megaraid 64bit fix/cleanup (AMD64) Mukker, Atul
2004-04-16 16:35 Mukker, Atul
2004-04-16 19:21 ` Jord Tanner
     [not found]   ` <A1E28594-9478-11D8-B5AA-000A95CD704C@wagland.net>
2004-04-22 18:22     ` Jord Tanner
2004-04-22 18:37       ` Christoph Hellwig
     [not found] <18kst-5Av-1@gated-at.bofh.it>
2003-12-30  5:26 ` Andi Kleen
2004-01-01 14:08   ` Brad House
2003-12-30  5:10 Brad House
2003-12-30  5:20 ` Jeff Garzik
2003-12-30  6:26   ` Brad House
2003-12-30  6:35     ` Jeff Garzik
2003-12-30 19:43       ` Samuel Flory
2003-12-30 19:49         ` Brad House
2003-12-30 19:54           ` Samuel Flory
2003-12-30 21:09             ` Brad House
2003-12-30 23:11             ` Matt Domsch

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=1082123798.11604.69.camel@gecko \
    --to=jord@indygecko.com \
    --cc=Atulm@lsil.com \
    --cc=brad_mssw@gentoo.org \
    --cc=linux-kernel@vger.kernel.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