Problems with PCI-X cards and PAE

I have a Dell Power Edge 6650 with 8 GB of RAM (/PAE in my boot.ini).

I have started adding cards to the PCI-X bus and am having a great deal of
trouble running the apps for them unless I disable PAE. I get error
messages from the applications like:

"CDA_MemoryLock failed to lock DMA buffer into physical memory (returned
0xcd0e0000)"

I have tried running both Windows XP Pro and Server 2003, Enterprise Ed.
With the same result. With PAE I get the messages, without PAE, the apps
seem to run. Unfortunately, I need the extra memory and we were planning on
going from 8 GB to 32.

Any thought on what is going on? Can I ask the OS to put the cards in a
certain address range? Are the apps just not able to handle pointers to
the memory beyond 4 G?

I have the source for the apps, but I'd like to get a handle on what the
problems might be before I spend a significant amount of time blindly poking
around.

Thanks in advance,

Marc Reinig
UCO/Lick
Laboratory for Adaptive Optics

Alexander
Thu Sep 16 21:49:00 CDT 2004

Looks like your cards don't support DMA above 4GB. If the driver is written
properly, HAL will copy data to the bounce buffers for them.

The issue is not about address the cards occupy. It's the buffers they get
from applications. You can allocate a buffer below 4 GB in the driver and
copy your data there.

"Marc Reinig" <Marco@newsgroups.nospam> wrote in message
news:eikpXuDnEHA.4004@TK2MSFTNGP10.phx.gbl...
>I have a Dell Power Edge 6650 with 8 GB of RAM (/PAE in my boot.ini).
>
> I have started adding cards to the PCI-X bus and am having a great deal of
> trouble running the apps for them unless I disable PAE. I get error
> messages from the applications like:
>
> "CDA_MemoryLock failed to lock DMA buffer into physical memory (returned
> 0xcd0e0000)"
>
> I have tried running both Windows XP Pro and Server 2003, Enterprise Ed.
> With the same result. With PAE I get the messages, without PAE, the apps
> seem to run. Unfortunately, I need the extra memory and we were planning
> on going from 8 GB to 32.
>
> Any thought on what is going on? Can I ask the OS to put the cards in a
> certain address range? Are the apps just not able to handle pointers to
> the memory beyond 4 G?
>
> I have the source for the apps, but I'd like to get a handle on what the
> problems might be before I spend a significant amount of time blindly
> poking around.
>
> Thanks in advance,
>
> Marc Reinig
> UCO/Lick
> Laboratory for Adaptive Optics
>
>

Marc
Tue Sep 21 13:03:17 CDT 2004

The drivers turn out not to be written for PAE and I don't have the source.
I was hoping there was some way I could get the OS to keep everything below
4G for them. I'm not sure if that would help since they do DMA, but I
thought I'd check. As it is, I had to reduce the total installed memory to
4G to get them to work. Even setting MAXMEM=2048 and removing /PAE in the
BOOT.INI didn't work. I actually had to remove the memory.

Marc Reinig
UCO/Lick
Laboratory for Adaptive Optics

"Alexander Grigoriev" <alegr@earthlink.net> wrote in message
news:OzWSkDGnEHA.2140@TK2MSFTNGP11.phx.gbl...
> Looks like your cards don't support DMA above 4GB. If the driver is
> written properly, HAL will copy data to the bounce buffers for them.
>
> The issue is not about address the cards occupy. It's the buffers they get
> from applications. You can allocate a buffer below 4 GB in the driver and
> copy your data there.
>
> "Marc Reinig" <Marco@newsgroups.nospam> wrote in message
> news:eikpXuDnEHA.4004@TK2MSFTNGP10.phx.gbl...
>>I have a Dell Power Edge 6650 with 8 GB of RAM (/PAE in my boot.ini).
>>
>> I have started adding cards to the PCI-X bus and am having a great deal
>> of trouble running the apps for them unless I disable PAE. I get error
>> messages from the applications like:
>>
>> "CDA_MemoryLock failed to lock DMA buffer into physical memory (returned
>> 0xcd0e0000)"
>>
>> I have tried running both Windows XP Pro and Server 2003, Enterprise Ed.
>> With the same result. With PAE I get the messages, without PAE, the apps
>> seem to run. Unfortunately, I need the extra memory and we were planning
>> on going from 8 GB to 32.
>>
>> Any thought on what is going on? Can I ask the OS to put the cards in a
>> certain address range? Are the apps just not able to handle pointers to
>> the memory beyond 4 G?
>>
>> I have the source for the apps, but I'd like to get a handle on what the
>> problems might be before I spend a significant amount of time blindly
>> poking around.
>>
>> Thanks in advance,
>>
>> Marc Reinig
>> UCO/Lick
>> Laboratory for Adaptive Optics
>>
>>
>
>

martinbo
Fri Sep 24 13:36:19 CDT 2004

------=_NextPart_0001_FF21E0B8
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

>> The drivers turn out not to be written for PAE and I don't have the
source.
>> I was hoping there was some way I could get the OS to keep everything
below
>> 4G for them. I'm not sure if that would help since they do DMA, but I
>> thought I'd check. As it is, I had to reduce the total installed memory
to
>> 4G to get them to work. Even setting MAXMEM=2048 and removing /PAE in
the
>> BOOT.INI didn't work. I actually had to remove the memory.

Do you see this on both Windows XP and Windows Server 2003? On XP the
default is to enable PAE if memory above 4GB is found. You would need to
specify /NOPAE in BOOT.INI to disable it. On Server 2003 PAE has to be
explicitly enabled in BOOT.INI.


Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_FF21E0B8
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 >> The drivers turn out not to be written for PAE and I don't have the source.
\par >> I was hoping there was some way I could get the OS to keep everything below
\par >> 4G for them. I'm not sure if that would help since they do DMA, but I
\par >> thought I'd check. As it is, I had to reduce the total installed memory to
\par >> 4G to get them to work. Even setting MAXMEM=2048 and removing /PAE in the
\par >> BOOT.INI didn't work. I actually had to remove the memory.
\par
\par Do you see this on both Windows XP and Windows Server 2003? On XP the default is to enable PAE if memory above 4GB is found. You would need to specify /NOPAE in BOOT.INI to disable it. On Server 2003 PAE has to be explicitly enabled in BOOT.INI.
\par
\par
\par Thanks,
\par Martin Borve [MSFT]
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_FF21E0B8--

Marc
Mon Sep 27 12:15:27 CDT 2004


""Martin Borve [MSFT]"" <martinbo@online.microsoft.com> wrote in message
news:j8AITVmoEHA.2640@cpmsftngxa06.phx.gbl...
>>> The drivers turn out not to be written for PAE and I don't have the
>>> source.
>>> I was hoping there was some way I could get the OS to keep everything
>>> below 4G for them. I'm not sure if that would help since they do DMA,
>>> but I thought I'd check. As it is, I had to reduce the total installed
>>> to memory 4G to get them to work. Even setting MAXMEM=2048 and
>>> removing the /PAE in BOOT.INI didn't work. I actually had to remove the
>>> memory.

> Do you see this on both Windows XP and Windows Server 2003? On XP the
> default is to enable PAE if memory above 4GB is found. You would need to
> specify /NOPAE in BOOT.INI to disable it. On Server 2003 PAE has to be
> explicitly enabled in BOOT.INI.

Win2003 Server BOOT.INI Options with 8 GB RAM
/PAE - Doesn't work
/MAXMEM=4096 - Doesn't Work
(No Options) - Doesn't Work
/NOPAE - Havent tried. I'll let you know when I do

WinXP Pro BOOT.INI Options with 8 GB RAM
/PAE - Doesn't work
/MAXMEM=4096 - Doesn't Work
(No Options) - Doesn't Work
/NOPAE - Havent tried. I'll let you know when I do

Win2003 Server BOOT.INI Options with 4 GB RAM
/PAE - Works
/MAXMEM=4096 - Works
(No Options) - Works

WinXP Pro BOOT.INI Options with 4 GB RAM
/PAE - Works
/MAXMEM=4096 - Works
(No Options) - Works

Marco

martinbo
Mon Oct 04 15:35:25 CDT 2004

------=_NextPart_0001_098CD169
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

Have you had a chance to try /NOPAE yet?

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_098CD169
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 Have you had a chance to try /NOPAE yet?
\par
\par Thanks,
\par Martin Borve [MSFT]
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_098CD169--

Marc
Mon Oct 04 15:45:41 CDT 2004

It's scheduled for this week. I'm just not sure exactly when I can shut the
system down and add back the memory.

Marco

--
Marc Reinig
UCO/Lick
Laboratory for Adaptive Optics

""Martin Borve [MSFT]"" <martinbo@online.microsoft.com> wrote in message
news:iuCSyGlqEHA.2084@cpmsftngxa06.phx.gbl...
> Have you had a chance to try /NOPAE yet?
>
> Thanks,
> Martin Borve [MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.