|
Kevin Warkentin(deleted)
|
qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/01/2011 5:42 PM
post89814
|
qnx_osinfo call returns incorrect memory size
Hi:
I am testing Product Suite 2009 on a HPz210 CMT Workstation and have come across the following error:
We use the Watcom C compiler routine : qnx_osinfo to obtain the amount of available memory. We usually see 65MB but are
only seeing 22.7MB
We also see a memory error when starting io-usb. We get "device 1 descriptors -not enough memory.
We have not seen these errors on our HPz400 machine at all.
The Z210 has a processor type of: Inrel(R) Core (TM) i3-2100 CPU@3.10GHZ
SYSTEM BIOS J51 v01.19
Processor Speed: 3100MHZ
Memory Size 1024 MB DDR3/1333 MHZ
- Any thoughts?
-Thanks,
Kevin
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/04/2011 1:17 PM
post89883
|
Re: qnx_osinfo call returns incorrect memory size
Hi:
Just wanted add the fact that I did try loading Product Suite 2011 onto the HP Z210 CMT Workstation as well but still
got the same memory errors.
Any guidance would be appreciated. We would like to continue to use HP Workstations for our QNX based Process Control
Product and the Z210 Worstation is the next computer in line after the HP Z400 which is close to end of life cycle.
- Thanks,
Kevin
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/09/2011 2:44 PM
post89969
|
Re: qnx_osinfo call returns incorrect memory size
Hi:
We really need some guidance on this issue as it is becoming critical for our customer base.
Any help would be greatly appreciated as we can't proceed with testing until this issue is resolved.
- Thanks,
Kevin
|
|
|
|
|
|
Pavel Kozlov(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Pavel Kozlov(deleted)
11/10/2011 3:14 AM
post89987
|
Re: qnx_osinfo call returns incorrect memory size
Hi, Kevin
When this problem occurs? Immediately after booting, or after running a
particular application?
Please provide additional information about your system (output of the
following utilities when this problem occurs):
sin info
sin ar
sin mem
Regards,
Pavel
> Hi:
>
> We really need some guidance on this issue as it is becoming critical for our customer base.
> Any help would be greatly appreciated as we can't proceed with testing until this issue is resolved.
>
> - Thanks,
>
> Kevin
>
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post89969
>
>
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/15/2011 3:42 PM
post90109
|
Re: qnx_osinfo call returns incorrect memory size
Hi Pavel:
I believe the problem happens after a reboot. We have a script that we use to startup USB tasks for USB device access
and when this script runs we get memory errors as mentioned above.
We also run a program that calls the watcom C library routine qnx_osinfo which
returns the amount of memory that the OS thinks it has avaialble which is always 64MB but in this case it only sees 22.
7MB.
I've included the results of sin ar,sin mem, and sin in and also attached the usb script we are using although I think
that some of the commands the script uses just eat up enough memory to cause the "device 1 - descriptors - not enough
memory error" I mentioned earlier.
sin ar
PID USER NAME ARGUMENTS
1 System /boot/sys/Proc32 -l 1
2 System /boot/sys/Slib32
4 System /bin/Fsys -Hdisk160
5 System /bin/Fsys.atapi fsys -Ndsk0 -n0=hd0. -n5=cd0.
8 System Not available.
18 System /bin/Dev
21 System /bin/Dev.ansi -Q -n4
26 System /bin/Dev.pty -n16
27 System Iso9660fsys /cd0.0
30 System tinit -t /dev/con1 -T /dev/con2 /dev/con3 /dev/con4
31 root -sh
41 root sin ar
sin info
Node CPU Machine Speed Memory Ticksize Display Flags
1 686/687 PCI 65535 863M/1005M 10.0ms VGA Color -3P+----------8P
Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
0 0 23408 0 64 100 64 500 125 6 738M/ 1040M
Boot from *Hard at Nov 15 17:35 Locators:
sin mem
PROGRAM PID
/boot/sys/Proc32 1
0005 F0000000 122880 -B-3--------DC- 000D F0040000 268M -B-3--------D--
10A9 00039000 28672 -B--+--G-----C- 0009 FF801000 29056 ---3---G-------
0011 FF800000 2048 -------G------- 0049 0000A000 4096 -B-----G-------
/boot/sys/Slib32 2
0005 0002B000 53248 -BS3---------C- 000D 00038000 4096 -B-3-----------
10A1 0002B000 53248 -BS3+--G-----C-
/bin/Fsys 4
0005 00042000 81920 -B-3---------C- 000D 0024D000 143M -BS3-----------
0015 11411000 143M -BS3+---------- 001D 0005C000 90112 -BS3+--------C-
0025 0024D000 143M -BS3+----------
/bin/Fsys.atapi 5
0005 0005C000 90112 -BS3---------C- 000D 11411000 143M -BS3-----------
0025 0024D000 143M -BS3+----------
10D1 00086000 65536 -B-3---G-+-MD-- 10C9 00018000 65536 -B-3---G-+-MD--
10C1 00001000 8192 -B-3---G-+-MD--
idle 8
//1/bin/Dev32 18
0005 0000C000 32768 -BS3---------C- 000D 00226000 94208 -BS3-----------
0015 00003000 20480 -BS3+---------- 001D 00072000 40960 -BS3+--------C-
0025 00003000 20480 -BS3+---------- 002D 00072000 40960 -BS3+--------C-
0035 0007F000 16384 -BS3+---------- 003D 00014000 12288 -BS3+------M---
0045 00008000 4096 -BS3+------M--- 004D 00059000 12288 -BS3+--------C-
0055 0007F000 16384 -BS3+---------- 005D 00059000 12288 -BS3+--------C-
0065 00096000 20480 -BS3-------M--- 006D 0011F000 20480 -BS3-------M---
//1/bin/Dev32.ansi 21
0005 00072000 40960 -BS3---------C- 000D 00003000 20480 -BS3-----------
0015 000A0000 65536 -----------MD-- 001D 00226000 94208 -BS3+----------
0025 0000C000 32768 -BS3+--------C- 002D 00226000 94208 -BS3+----------
0035 0000C000 32768 -BS3+--------C- 003D 00014000 12288 -BS3-------M---
0045 00008000 4096 -BS3-------M--- 004D 00117000 32768 -B-3-------M---
//1/bin/Dev32.pty 26
0005 00059000 12288 -BS3---------C- 000D 0007F000 16384 -BS3-----------
0015 00226000 94208 -BS3+---------- 001D 0000C000 32768 -BS3+--------C-
0025 00226000 94208 -BS3+---------- 002D 0000C000 32768 -BS3+--------C-
0065 00096000 20480 -BS3+------M--- 006D 0011F000 20480 -BS3+------M---
//1/bin/Iso9660fsys 27
0005 08B31000 28672...
View Full Message
|
|
|
|
|
|
Pavel Kozlov(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Pavel Kozlov(deleted)
11/16/2011 4:10 AM
post90121
|
Re: qnx_osinfo call returns incorrect memory size
Hi Kevin,
New documentation for qnx_osinfo function recommends using _osinfo
structure member freemem instead of freememk to get correct value of
free memory in the system. Please check your program for this.
sin info shows that in your system has 863M free memory.
As for the io-usb. There is a known issue in new USB stack.
http://community.qnx.com/sf/discussion/do/listPosts/projects.qnx4/discussion.general.topc20904
May be you are faced with same problem. What version of io-usb you are
using?
Regards,
Pavel
> Hi Pavel:
>
> I believe the problem happens after a reboot. We have a script that we use to startup USB tasks for USB device access
and when this script runs we get memory errors as mentioned above.
> We also run a program that calls the watcom C library routine qnx_osinfo which
> returns the amount of memory that the OS thinks it has avaialble which is always 64MB but in this case it only sees 22
.7MB.
> I've included the results of sin ar,sin mem, and sin in and also attached the usb script we are using although I
think that some of the commands the script uses just eat up enough memory to cause the "device 1 - descriptors - not
enough memory error" I mentioned earlier.
>
> sin ar
> PID USER NAME ARGUMENTS
> 1 System /boot/sys/Proc32 -l 1
> 2 System /boot/sys/Slib32
> 4 System /bin/Fsys -Hdisk160
> 5 System /bin/Fsys.atapi fsys -Ndsk0 -n0=hd0. -n5=cd0.
> 8 System Not available.
> 18 System /bin/Dev
> 21 System /bin/Dev.ansi -Q -n4
> 26 System /bin/Dev.pty -n16
> 27 System Iso9660fsys /cd0.0
> 30 System tinit -t /dev/con1 -T /dev/con2 /dev/con3 /dev/con4
> 31 root -sh
> 41 root sin ar
>
> sin info
> Node CPU Machine Speed Memory Ticksize Display Flags
> 1 686/687 PCI 65535 863M/1005M 10.0ms VGA Color -3P+----------8P
>
> Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
> 0 0 23408 0 64 100 64 500 125 6 738M/ 1040M
>
> Boot from *Hard at Nov 15 17:35 Locators:
>
> sin mem
> PROGRAM PID
> /boot/sys/Proc32 1
> 0005 F0000000 122880 -B-3--------DC- 000D F0040000 268M -B-3--------D--
> 10A9 00039000 28672 -B--+--G-----C- 0009 FF801000 29056 ---3---G-------
> 0011 FF800000 2048 -------G------- 0049 0000A000 4096 -B-----G-------
> /boot/sys/Slib32 2
> 0005 0002B000 53248 -BS3---------C- 000D 00038000 4096 -B-3-----------
> 10A1 0002B000 53248 -BS3+--G-----C-
> /bin/Fsys 4
> 0005 00042000 81920 -B-3---------C- 000D 0024D000 143M -BS3-----------
> 0015 11411000 143M -BS3+---------- 001D 0005C000 90112 -BS3+--------C-
> 0025 0024D000 143M -BS3+----------
> /bin/Fsys.atapi 5
> 0005 0005C000 90112 -BS3---------C- 000D 11411000 143M -BS3-----------
> 0025 0024D000 143M -BS3+----------
> 10D1 00086000 65536 -B-3---G-+-MD-- 10C9 00018000 65536 -B-3---G-+-MD--
> 10C1 00001000 8192 -B-3---G-+-MD--
> idle 8
> //1/bin/Dev32 18
> 0005 0000C000 32768 -BS3---------C- 000D 00226000 94208 -BS3-----------
> 0015 00003000 20480 -BS3+---------- 001D 00072000 40960 -BS3+--------C-
> 0025 00003000 20480 -BS3+---------- 002D 00072000 40960 -BS3+--------C-
> 0035 0007F000 16384 -BS3+---------- 003D 00014000 12288 -BS3+------M---
> 0045 00008000 4096 -BS3+------M--- 004D 00059000 12288 -BS3+--------C-
> 0055 0007F000 16384 -BS3+---------- 005D 00059000 12288 -BS3+--------C-
> 0065 00096000 20480 -BS3-------M--- 006D 0011F000 20480 -BS3-------M---
>...
View Full Message
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/22/2011 5:46 PM
post90249
|
Re: qnx_osinfo call returns incorrect memory size
Hi Pavel:
I checked our code and we do not access freememk we look at totmemk
and are using watcom C 9.52 compiler.There is no freemem structure member just freememk. The structure def we have is:
#ifndef __OSINFO_H_INCLUDED
#ifndef __TYPES_H_INCLUDED
#include <sys/types.h>
#endif
#if __WATCOMC__ > 1000
#pragma pack(__push,1);
#else
#pragma pack(1);
#endif
#ifdef __cplusplus
extern "C" {
#endif
struct _osinfo {
short unsigned cpu_speed, /* A PC is around 960 */
num_procs,
tick_size,
version,
timesel,
totmemk,
freememk;
char primary_monitor,
secondary_monitor;
short unsigned machinesel;
unsigned short disksel; /* pointer to _diskinfo structure */
unsigned long diskoff;
unsigned long ssinfo_offset;
short unsigned ssinfo_sel,
microkernel_size;
char release,
zero2;
long sflags;
nid_t nodename;
long cpu,
fpu;
char machine[16],
bootsrc,
zero3[9];
short unsigned num_names,
num_timers,
num_sessions,
num_handlers,
reserve64k,
num_semaphores,
prefix_len,
zero4[4],
max_nodes,
proc_freemem,
cpu_loadmask,
fd_freemem,
ldt_freemem,
num_fds[3],
pidmask,
name_freemem;
long unsigned top_of_mem;
long unsigned freepmem;
long unsigned freevmem;
long unsigned totpmem;
long unsigned totvmem;
long unsigned cpu_features;
short unsigned zero5[13];
} ;
Here is the snippet of code we use:
#include <sys/osinfo.h>
void main(int argc, char **argv)
{
int opt;
Bool prompt = TRUE, quiet = FALSE;
float memory = 15.36, memAvail;
struct _osinfo osinfo;
if (qnx_osinfo(getnid(), &osinfo) == -1) {
DB_FUNC(<--- main);
bciAbortTask(EXIT_FAILURE, "qnx_osinfo():- failed, @e\n");
}
memAvail = (float)osinfo.totmemk / 1000.0;
if (!quiet) {
sprintf(buf, "There is a total of %3.1f Mbytes RAM available.\n", memAvail);
printf(buf);
bciError(buf);
}
Re io-usb:
we are using 1.00B July 18 2008
-Kevin
|
|
|
|
|
|
Pavel Kozlov(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Pavel Kozlov(deleted)
11/23/2011 6:23 AM
post90256
|
Re: qnx_osinfo call returns incorrect memory size
Hi Kevin,
Sorry for my misprint. Please take a look at _osinfo structure members
freepmem and totalpmem. Note that totalpmem and freepmem fields show
total memory and free memory in bytes.
> io-usb:
> we are using 1.00B July 18 2008
So assumption with io-usb was not confirmed.
Do you see "Not enough memory" error when you mount USB flash manually?
Do you use the same QNX configuration and components versions on HPz400
and HPz210. Please provide "sin ver" output from HPz400 machine and HPz210.
Regards,
Pavel
> Hi Pavel:
>
> I checked our code and we do not access freememk we look at totmemk
> and are using watcom C 9.52 compiler.There is no freemem structure member just freememk. The structure def we have is:
>
> #ifndef __OSINFO_H_INCLUDED
>
> #ifndef __TYPES_H_INCLUDED
> #include <sys/types.h>
> #endif
>
> #if __WATCOMC__ > 1000
> #pragma pack(__push,1);
> #else
> #pragma pack(1);
> #endif
> #ifdef __cplusplus
> extern "C" {
> #endif
> struct _osinfo {
> short unsigned cpu_speed, /* A PC is around 960 */
> num_procs,
> tick_size,
> version,
> timesel,
> totmemk,
> freememk;
> char primary_monitor,
> secondary_monitor;
> short unsigned machinesel;
> unsigned short disksel; /* pointer to _diskinfo structure */
> unsigned long diskoff;
> unsigned long ssinfo_offset;
> short unsigned ssinfo_sel,
> microkernel_size;
> char release,
> zero2;
> long sflags;
> nid_t nodename;
> long cpu,
> fpu;
> char machine[16],
> bootsrc,
> zero3[9];
> short unsigned num_names,
> num_timers,
> num_sessions,
> num_handlers,
> reserve64k,
> num_semaphores,
> prefix_len,
> zero4[4],
> max_nodes,
> proc_freemem,
> cpu_loadmask,
> fd_freemem,
> ldt_freemem,
> num_fds[3],
> pidmask,
> name_freemem;
> long unsigned top_of_mem;
> long unsigned freepmem;
> long unsigned freevmem;
> long unsigned totpmem;
> long unsigned totvmem;
> long unsigned cpu_features;
> short unsigned zero5[13];
> } ;
>
> Here is the snippet of code we use:
> #include <sys/osinfo.h>
> void main(int argc, char **argv)
> {
> int opt;
> Bool prompt = TRUE, quiet = FALSE;
> float memory = 15.36, memAvail;
> struct _osinfo osinfo;
>
> if (qnx_osinfo(getnid(), &osinfo) == -1) {
> DB_FUNC(<--- main);
> bciAbortTask(EXIT_FAILURE, "qnx_osinfo():- failed, @e\n");
> }
>
> memAvail = (float)osinfo.totmemk / 1000.0;
>
> if (!quiet) {
> sprintf(buf, "There is a total of %3.1f Mbytes RAM available.\n", memAvail);
> printf(buf);
> bciError(buf);
> }
>
> Re io-usb:
> we are using 1.00B July 18 2008
>
> -Kevin
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post90249
>
> .
>
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/23/2011 4:00 PM
post90268
|
Re: qnx_osinfo call returns incorrect memory size
Hi Pavel:
As mentioned we are using Watcom C 9.52 compiler. The _osinfo structure does not have totalpmem or freepmem fields.
I had to go to the 32 bit Watcom C 10.6 compiler to access those fields.
When I did, totalpmem returned the 1GB of memory I expected and freememk still returned 22.7MB.
The confusing part is that freememk returns 64MB on the HPZ400 computer and any other computer that we have used in the
past for QNX.
I'm starting to wonder if it is some issue re 16 bit vs 32 bit functionality for this HPZ210 computer.
My tests were just run in the alternate boot so it is just QNX running with the little program calling the qnx_osinfo
routine.
As mentioned the same routine returns the 64MB result I expected on the HPZ400.
Here are sin ver for the HPZ210 and HPZ400:
Z210:
PROGRAM NAME VERSION DATE
sys/Proc32 Proc 4.25Q Jul 18 2005
sys/Proc32 Slib16 4.23G Oct 04 1996
sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Z Jul 06 2009
/bin/Fsys.atapi atapi 4.25G Jul 06 2009
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
//1/bin/io-usb USB 1.00B Jul 18 2008
Z400:
PROGRAM NAME VERSION DATE
/boot/sys/Proc32 Proc 4.25Q Jul 18 2005
/boot/sys/Proc32 Slib16 4.23G Oct 04 1996
/boot/sys/Slib32 Slib32 4.24B Aug 12 1997
/bin/Fsys Fsys32 4.24Z Jul 06 2009
/bin/Fsys.atapi atapi 4.25G Jul 06 2009
//1/bin/Dev32 Dev32 4.23G Oct 04 1996
//1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
//1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
//1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
//1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
//1/bin/io-usb USB 1.00B Jul 18 2008
Here is the sin info for both computers:
Z210:
Node CPU Machine Speed Memory Ticksize Display Flags
1 686/687 PCI 65535 997M/1005M 10.0ms VGA Color -3P+----------8P
Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
0 0 3392 0 64 100 64 500 125 6 2711M/ 3783M
Boot from *Hard at Nov 23 17:53 Locators:
Z400:
Node CPU Machine Speed Memory Ticksize Display Flags
1 686/687 PCI 65535 1795M/2088M 10.0ms VGA Color -3P+----------8P
Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
0 0 23264 0 64 100 64 500 125 6 1246M/ 2147M
Boot from *Hard at Nov 23 15:37 Locators:
With respect to io-usb:
I tried using the suggestion of adding -S 500 500 ( global and local segments) to Proc32 but I still get the same "
device 1 -descriptors-Not enough memory error"
I then discovered that if I just boot into the alternate boot ( just bare bones QNX Product Suite 2009) run io-usb & and
then run usb , I get the "device 1 -descriptors-Not enough memory error"
System Information for the Z210 is as follows:
Z210 CMT Workstation
Processor Type: Intel(R) Core (TM) i3-2100 CPU @ 3.1 GHZ
Processor Speed: 3100MHZ
Cache Size(L1/L2/L3): 64KBx1/256KBx1/3072KBx1
Memory Size: 1024MB DDR3/1333 MHZ
System Bios: J51 v01.19
System Information for the Z400 is as follows:
Z400 Workstation
Processor Type: Intel(R) Xeon(R) CPU W3503 @ 2.4 GHZ
Processor Speed: 2400 MHZ
Cache Size(L1/L2/L3): 128KB/512KB/4MB
Memory Size: 2048MB DDR3/ECC/1066MHZ(2048MB)
System Bios: 786g3 v03.12
- Kevin
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/23/2011 4:22 PM
post90269
|
Re: qnx_osinfo call returns incorrect memory size
Hi Pavel:
One more thing I forgot to mention.
I can successfully mount a USB flash stick even with the memory error
however I found that if I tried to copy a file from the flash stick to the hard drive I could not do so. I had to free
up more memory by slaying some tasks and then I could do the copy.
So the OS is just not seeing the correct amount of memory.
|
|
|
|
|
|
Pavel Kozlov(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Pavel Kozlov(deleted)
11/24/2011 7:29 AM
post90276
|
Re: qnx_osinfo call returns incorrect memory size
Hi Kevin,
Thanks for detailed information.
Have you tried to use the USB 2.0 stack?
You can get USB stack (version 2.00J) by the following link:
http://community.qnx.com/sf/frs/do/downloadFile/projects.qnx4/frs.usb_stack.qnx4_usb_stack/frs35355?dl=1
Version 1.00B is quite old and on some modern boards can build USB
topology incorrectly and as a result you can see "device 1
-descriptors-Not enough memory error".
In attach simple program that try to allocate as much memory as
possible. Please run this program after booting , after running the
io-usb, and after running the Fsys.umass and provide output. It would be
interesting to see real amount of available memory.
I don't think that totalmemk value relate to your problem with memory.
totalmemk contains truncated totalpmem value ((totalpmem >> 10) & 0xFFFF).
On my system totalmemk returns 20540Kb.
Regards,
Pavel
> Hi Pavel:
>
> As mentioned we are using Watcom C 9.52 compiler. The _osinfo structure does not have totalpmem or freepmem fields.
> I had to go to the 32 bit Watcom C 10.6 compiler to access those fields.
> When I did, totalpmem returned the 1GB of memory I expected and freememk still returned 22.7MB.
> The confusing part is that freememk returns 64MB on the HPZ400 computer and any other computer that we have used in
the past for QNX.
> I'm starting to wonder if it is some issue re 16 bit vs 32 bit functionality for this HPZ210 computer.
> My tests were just run in the alternate boot so it is just QNX running with the little program calling the qnx_osinfo
routine.
> As mentioned the same routine returns the 64MB result I expected on the HPZ400.
> Here are sin ver for the HPZ210 and HPZ400:
>
> Z210:
> PROGRAM NAME VERSION DATE
> sys/Proc32 Proc 4.25Q Jul 18 2005
> sys/Proc32 Slib16 4.23G Oct 04 1996
> sys/Slib32 Slib32 4.24B Aug 12 1997
> /bin/Fsys Fsys32 4.24Z Jul 06 2009
> /bin/Fsys.atapi atapi 4.25G Jul 06 2009
> //1/bin/Dev32 Dev32 4.23G Oct 04 1996
> //1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
> //1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
> //1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
> //1/bin/io-usb USB 1.00B Jul 18 2008
>
> Z400:
> PROGRAM NAME VERSION DATE
> /boot/sys/Proc32 Proc 4.25Q Jul 18 2005
> /boot/sys/Proc32 Slib16 4.23G Oct 04 1996
> /boot/sys/Slib32 Slib32 4.24B Aug 12 1997
> /bin/Fsys Fsys32 4.24Z Jul 06 2009
> /bin/Fsys.atapi atapi 4.25G Jul 06 2009
> //1/bin/Dev32 Dev32 4.23G Oct 04 1996
> //1/bin/Dev32.ser Dev.ser 4.25A Feb 14 2003
> //1/bin/Dev32.ansi Dev32.ansi 4.23H Nov 21 1996
> //1/bin/Dev32.pty Dev32.pty 4.23G Oct 04 1996
> //1/bin/Iso9660fsys Iso9660fsys 4.23D Mar 20 2000
> //1/bin/io-usb USB 1.00B Jul 18 2008
>
> Here is the sin info for both computers:
> Z210:
> Node CPU Machine Speed Memory Ticksize Display Flags
> 1 686/687 PCI 65535 997M/1005M 10.0ms VGA Color -3P+----------8P
>
> Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
> 0 0 3392 0 64 100 64 500 125 6 2711M/ 3783M
>
> Boot from *Hard at Nov 23 17:53 Locators:
>
> Z400:
> Node CPU Machine Speed Memory Ticksize Display Flags
> 1 686/687 PCI 65535 1795M/2088M 10.0ms VGA Color -3P+----------8P
>
> Heapp Heapf Heapl Heapn Hands Names Sessions Procs Timers Nodes Virtual
> 0 0 23264 0 64 ...
View Full Message
|
|
|
|
|
|
Kevin Warkentin(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Kevin Warkentin(deleted)
11/24/2011 11:24 AM
post90283
|
Re: qnx_osinfo call returns incorrect memory size
Hi Pavel:
Good news. I tried the USB 2.0 stack and it eliminated the "not enough memory error".
I ran the qi program on both the Z210 and the Z400 and the results are as follows:
Z210: ( Note the physical amount of memory is 1GB. I had 2GB of memory installed initially and when I first discovered
the memory errors I removed 1GB of memory from the computer)
Total memory in the system is 982MB (1029857280)
Free memory in the system is 975MB (1023041536)
Total allocated 975MB (998400KB)
Total memory in the system is 982MB (1029857280)
Free memory in the system is 0MB (675840)
Z400: ( Note: There is a full 2GB of memory physically installed in this computer)
Total memory in the system is 2039MB (2138324992)
Free memory in the system is 1751MB (1836707840)
Total allocated 1023MB (1047552KB)
Total memory in the system is 2039MB (2138324992)
Free memory in the system is 728MB (764010496)
- Kevin
|
|
|
|
|
|
Pavel Kozlov(deleted)
|
Re: qnx_osinfo call returns incorrect memory size
|
|
Pavel Kozlov(deleted)
11/25/2011 6:26 AM
post90296
|
Re: qnx_osinfo call returns incorrect memory size
Hi Kevin,
It's really good news.
qi program also shows good results (Note: max data segment size for a
32bit program in QNX 4 is 1Gb).
I hope that now there is no barriers for using QNX4 on the HP Z210 machine.
Regards,
Pavel
> Hi Pavel:
>
> Good news. I tried the USB 2.0 stack and it eliminated the "not enough memory error".
>
> I ran the qi program on both the Z210 and the Z400 and the results are as follows:
>
> Z210: ( Note the physical amount of memory is 1GB. I had 2GB of memory installed initially and when I first discovered
the memory errors I removed 1GB of memory from the computer)
>
> Total memory in the system is 982MB (1029857280)
> Free memory in the system is 975MB (1023041536)
>
> Total allocated 975MB (998400KB)
>
> Total memory in the system is 982MB (1029857280)
> Free memory in the system is 0MB (675840)
>
> Z400: ( Note: There is a full 2GB of memory physically installed in this computer)
>
> Total memory in the system is 2039MB (2138324992)
> Free memory in the system is 1751MB (1836707840)
>
> Total allocated 1023MB (1047552KB)
>
> Total memory in the system is 2039MB (2138324992)
> Free memory in the system is 728MB (764010496)
>
> - Kevin
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post90283
>
>
|
|
|
|
|
|
