public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Robert Nagy" <robert.nagy@gmail.com>
To: "Jesse Barnes" <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel RAID Controller SRCU42X in SGI Altix 350
Date: Thu, 29 Jun 2006 21:12:40 +0200	[thread overview]
Message-ID: <39f633820606291212v40b0016cl@mail.gmail.com> (raw)
In-Reply-To: <200606291132.51866.jbarnes@virtuousgeek.org>

I've tried the diff but there is no difference.
I've also tried to use the EFI driver from Intel, but that did not work either.

2006/6/29, Jesse Barnes <jbarnes@virtuousgeek.org>:
> On Thursday, June 29, 2006 8:18 am, Robert Nagy wrote:
> > Hi,
> >
> > Distribution: Debian testing/unstable
> > Hardware Environment: SGI Altix 350, 2xItanium 2, EFI (read dmesg)
> > http://bsd.hu/~robert/altix.dmesg
> > http://bsd.hu/~robert/altix.kconf
> >
> > Problem Description: I've installed an Intel(r) RAID Controller
> > SRCU42X (PCI-X) controller to this machine.
> > http://www.intel.com/design/servers/raid/srcu42x/index.htm
> > I've never used such a controller so if someone has any idea about
> > this please tell me. The dmesg will show everyhing, but:
> >
> > megaraid cmm: 2.20.2.6 (Release Date: Mon Mar 7 00:01:03 EST 2005)
> > megaraid: 2.20.4.8 (Release Date: Mon Apr 11 12:27:22 EST 2006)
> > megaraid: probe new device 0x1000:0x0407:0x8086:0x0532: bus 2:slot
> > 0:func 0 megaraid: out of memory, megaraid_alloc_cmd_packets 965
> > megaraid: maibox adapter did not initialize
>
> IIRC some Altix boxes don't support 32 bit DMA for PCI-X devices.  Based
> on the initialization code I looked at (just a quick scan), it looks
> like the command packet initialization is done before the switch to a 64
> bit DMA mask, which might cause the failure you see here.  You can try
> this patch out (totally untested).  It's not fully correct, it should
> probably try 64 bit first then fall back to 32 bit if that fails then
> give up, and the other 64 bit DMA mask call should probably be removed.
>
> Anyway, good luck.  If this one doesn't work you'll have to talk with one
> of the SGI guys and get some more debug info about the allocation
> failure for the command packets.
>
> Jesse
>
>
>

  reply	other threads:[~2006-06-29 19:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 15:18 Intel RAID Controller SRCU42X in SGI Altix 350 Robert Nagy
2006-06-29 18:32 ` Jesse Barnes
2006-06-29 19:12   ` Robert Nagy [this message]
2006-06-29 19:16     ` Jesse Barnes
2006-06-30  8:44       ` Robert Nagy
2006-06-30 16:07         ` Jesse Barnes
2006-06-29 20:42     ` Jesse Barnes
2006-06-30 12:07       ` Robert Nagy
2006-06-30 16:06         ` Jesse Barnes
2006-06-30 16:14           ` Robert Nagy
2006-06-30 16:21             ` Jesse Barnes

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=39f633820606291212v40b0016cl@mail.gmail.com \
    --to=robert.nagy@gmail.com \
    --cc=jbarnes@virtuousgeek.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