Hi.
I’m still trying to track down some performance issues on a QNX 4 node with
a Pentium III 800 MHz CPU and 512MB RAM.
I have Proc setup to run at priority 28.
When I copy several files, sac shows someone using up all the cpu at
priority 22 and priority 31 for small bursts of time (up to a second or so).
Who’s at priority 31?
This stops any Photon app from running at priority 10 and also affects the
mouse at priority 12.
What is Fsys and Proc doing that they are not giving up the CPU for other
process to run?
I have already tried to start Fsys with the ‘-c 32M’ option, but this has no
or little effect on this problem.
I also tried to take on of the RAM modules out and start QNX, but there were
problems with the boot. What do I need to do to get QNX working okay after
changing the RAM on a system?
Any other ideas? Please help.
If the copy is from another node, it seems to make the problem worse. I do
see the Net driver with sac taking up some time too.
I have another system with a similar CPU and RAM which does basically the
same. Not quite as long of a dead time (only 0.5-1s).
We also have a new DELL C800 Laptop with a Pentium III and 512MB RAM. There
is no problem with this system at the moment that I can see.
All the system are setup using the same version of the OS (latest for QNX4
and Photon 1.14). And have very similar settings for the BOOT file as well
as the sysinit file.
TIA
Augie
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9pf5mt$ap9$1@inn.qnx.com…
Hi.
I’m still trying to track down some performance issues on a QNX 4 node
with
a Pentium III 800 MHz CPU and 512MB RAM.
I have Proc setup to run at priority 28.
When I copy several files, sac shows someone using up all the cpu at
priority 22 and priority 31 for small bursts of time (up to a second or
so).
Who’s at priority 31?
Interrupts and Kernel.
This stops any Photon app from running at priority 10 and also affects the
mouse at priority 12.
What is Fsys and Proc doing that they are not giving up the CPU for other
process to run?
I have already tried to start Fsys with the ‘-c 32M’ option, but this has
no
or little effect on this problem.
I also tried to take on of the RAM modules out and start QNX, but there
were
problems with the boot. What do I need to do to get QNX working okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
Any other ideas? Please help.
If the copy is from another node, it seems to make the problem worse. I
do
see the Net driver with sac taking up some time too.
I have another system with a similar CPU and RAM which does basically the
same. Not quite as long of a dead time (only 0.5-1s).
We also have a new DELL C800 Laptop with a Pentium III and 512MB RAM.
There
is no problem with this system at the moment that I can see.
All the system are setup using the same version of the OS (latest for QNX4
and Photon 1.14). And have very similar settings for the BOOT file as
well
as the sysinit file.
I will make a very wild guess here: I remember reading that some Pentium
III motherboard
had problem with caching. That is for example memory above 256M would not
be cached properly.
It’s very strange that you can’t remove memory. Most of today memory module
don’t
have to work in pair.
TIA
Augie
Hi Mario.
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9pf5v7$aq8$1@inn.qnx.com…
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9pf5mt$ap9$> 1@inn.qnx.com> …
Hi.
I’m still trying to track down some performance issues on a QNX 4 node
with
a Pentium III 800 MHz CPU and 512MB RAM.
I have Proc setup to run at priority 28.
When I copy several files, sac shows someone using up all the cpu at
priority 22 and priority 31 for small bursts of time (up to a second or
so).
Who’s at priority 31?
Interrupts and Kernel.
This stops any Photon app from running at priority 10 and also affects
the
mouse at priority 12.
What is Fsys and Proc doing that they are not giving up the CPU for
other
process to run?
I have already tried to start Fsys with the ‘-c 32M’ option, but this
has
no
or little effect on this problem.
I also tried to take on of the RAM modules out and start QNX, but there
were
problems with the boot. What do I need to do to get QNX working okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
You don’t image have to rebuild the .BOOT file? If there are setting that
get set based on the amount of RAM, then they would be different.
But it should still boot? Sometimes it stops after it puts a few … other
times it reboots right after starting Proc.
Any other ideas? Please help.
If the copy is from another node, it seems to make the problem worse. I
do
see the Net driver with sac taking up some time too.
I have another system with a similar CPU and RAM which does basically
the
same. Not quite as long of a dead time (only 0.5-1s).
We also have a new DELL C800 Laptop with a Pentium III and 512MB RAM.
There
is no problem with this system at the moment that I can see.
All the system are setup using the same version of the OS (latest for
QNX4
and Photon 1.14). And have very similar settings for the BOOT file as
well
as the sysinit file.
I will make a very wild guess here: I remember reading that some Pentium
III motherboard
had problem with caching. That is for example memory above 256M would not
be cached properly.
What do I do here? Check the BIOS? Anyway to fix this?
It’s very strange that you can’t remove memory. Most of today memory
module
don’t
have to work in pair.
I can remove it. The QNX 4 system just doesn’t boot.
TIA
Augie
TIA
Augie
\
I also tried to take on of the RAM modules out and start QNX, but
there
were
problems with the boot. What do I need to do to get QNX working okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
You don’t image have to rebuild the .BOOT file?
No you don’t (unless there was option to Proc32 that force detection
of 512Meg).
Of course if you’ve specified 128M ram cache to Fsys and you only have
64Meg you may have a problem. But if you are using the default boot image
file there is nothing do to.
get set based on the amount of RAM, then they would be different.
But it should still boot? Sometimes it stops after it puts a few …
other
times it reboots right after starting Proc.
Very very very strange, I’ve never seem this.
I will make a very wild guess here: I remember reading that some
Pentium
III motherboard
had problem with caching. That is for example memory above 256M would
not
be cached properly.
What do I do here? Check the BIOS? Anyway to fix this?
From what I remember this was a limitation of the design and chipset.
It’s very strange that you can’t remove memory. Most of today memory
module don’t have to work in pair.
I can remove it. The QNX 4 system just doesn’t boot.
Have you check the manual. The system should be able to run with only
one memory module. What motherboard is this exaclty?
TIA
Augie
TIA
Augie
\
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9pfgl6$gua$1@inn.qnx.com…
I also tried to take on of the RAM modules out and start QNX, but
there
were
problems with the boot. What do I need to do to get QNX working
okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
You don’t image have to rebuild the .BOOT file?
No you don’t (unless there was option to Proc32 that force detection
of 512Meg).
Of course if you’ve specified 128M ram cache to Fsys and you only have
64Meg you may have a problem. But if you are using the default boot image
file there is nothing do to.
get set based on the amount of RAM, then they would be different.
But it should still boot? Sometimes it stops after it puts a few …
other
times it reboots right after starting Proc.
Very very very strange, I’ve never seem this.
I do. It start to boot and when it gets to Proc, it just reboots.
I will make a very wild guess here: I remember reading that some
Pentium
III motherboard
had problem with caching. That is for example memory above 256M would
not
be cached properly.
What do I do here? Check the BIOS? Anyway to fix this?
From what I remember this was a limitation of the design and chipset.
It’s very strange that you can’t remove memory. Most of today memory
module don’t have to work in pair.
I can remove it. The QNX 4 system just doesn’t boot.
Have you check the manual. The system should be able to run with only
one memory module. What motherboard is this exaclty?
This is a CyberResearch single board CPU. I have used these lots of times
in the past, without any problems.
I have reduced the amount of cache to Fsys to 8M and it is a little better.
You can still have dead spots when moving the mouse. This is a Pentium III
800 mhz system. You should not see any dead spots with the mouse when doing
a simple file copy.
TIA
Augie
TIA
Augie
TIA
Augie
\
“Augie Henriques” <augiehenriques@hotmail.com> wrote in message
news:9pfh5m$h0k$1@inn.qnx.com…
“Mario Charest” <> mcharest@clipzinformatic.com> > wrote in message
news:9pfgl6$gua$> 1@inn.qnx.com> …
I also tried to take on of the RAM modules out and start QNX, but
there
were
problems with the boot. What do I need to do to get QNX working
okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
You don’t image have to rebuild the .BOOT file?
No you don’t (unless there was option to Proc32 that force detection
of 512Meg).
Of course if you’ve specified 128M ram cache to Fsys and you only have
64Meg you may have a problem. But if you are using the default boot
image
file there is nothing do to.
get set based on the amount of RAM, then they would be different.
But it should still boot? Sometimes it stops after it puts a few …
other
times it reboots right after starting Proc.
Very very very strange, I’ve never seem this.
I do. It start to boot and when it gets to Proc, it just reboots.
I will make a very wild guess here: I remember reading that some
Pentium
III motherboard
had problem with caching. That is for example memory above 256M
would
not
be cached properly.
What do I do here? Check the BIOS? Anyway to fix this?
From what I remember this was a limitation of the design and chipset.
It’s very strange that you can’t remove memory. Most of today
memory
module don’t have to work in pair.
I can remove it. The QNX 4 system just doesn’t boot.
Have you check the manual. The system should be able to run with only
one memory module. What motherboard is this exaclty?
This is a CyberResearch single board CPU. I have used these lots of times
in the past, without any problems.
All with 512M ?
I have reduced the amount of cache to Fsys to 8M and it is a little
better.
You can still have dead spots when moving the mouse. This is a Pentium
III
800 mhz system. You should not see any dead spots with the mouse when
doing
a simple file copy.
Even with a 486 you shouldn’t 
TIA
Augie
TIA
Augie
TIA
Augie
\
“Mario Charest” <mcharest@clipzinformatic.com> wrote in message
news:9pfj79$i7a$1@inn.qnx.com…
“Augie Henriques” <> augiehenriques@hotmail.com> > wrote in message
news:9pfh5m$h0k$> 1@inn.qnx.com> …
“Mario Charest” <> mcharest@clipzinformatic.com> > wrote in message
news:9pfgl6$gua$> 1@inn.qnx.com> …
I also tried to take on of the RAM modules out and start QNX,
but
there
were
problems with the boot. What do I need to do to get QNX working
okay
after
changing the RAM on a system?
You shouldn’t have to change anything.
You don’t image have to rebuild the .BOOT file?
No you don’t (unless there was option to Proc32 that force detection
of 512Meg).
Of course if you’ve specified 128M ram cache to Fsys and you only have
64Meg you may have a problem. But if you are using the default boot
image
file there is nothing do to.
get set based on the amount of RAM, then they would be different.
But it should still boot? Sometimes it stops after it puts a few
…
other
times it reboots right after starting Proc.
Very very very strange, I’ve never seem this.
I do. It start to boot and when it gets to Proc, it just reboots.
I will make a very wild guess here: I remember reading that some
Pentium
III motherboard
had problem with caching. That is for example memory above 256M
would
not
be cached properly.
What do I do here? Check the BIOS? Anyway to fix this?
From what I remember this was a limitation of the design and chipset.
It’s very strange that you can’t remove memory. Most of today
memory
module don’t have to work in pair.
I can remove it. The QNX 4 system just doesn’t boot.
Have you check the manual. The system should be able to run with only
one memory module. What motherboard is this exaclty?
This is a CyberResearch single board CPU. I have used these lots of
times
in the past, without any problems.
All with 512M ?
This is the second with 512MB RAM. I have another one here setup as a
development/test node. It shows the problem, but not as bad as this one.
Augie
I have reduced the amount of cache to Fsys to 8M and it is a little
better.
You can still have dead spots when moving the mouse. This is a Pentium
III
800 mhz system. You should not see any dead spots with the mouse when
doing
a simple file copy.
Even with a 486 you shouldn’t >
TIA
Augie
TIA
Augie
TIA
Augie
\
This is a CyberResearch single board CPU. I have used these lots of
times
in the past, without any problems.
All with 512M ?
This is the second with 512MB RAM. I have another one here setup as a
development/test node. It shows the problem, but not as bad as this one.
I’m stumped. My guess is something is fishy with the hardware, but I have
no real clue what it is.
You say that if you remove some ram, the machines will hang when displaying
the … This is very odd since at this point QNX hasn’t started yet. It
is
the loader running in real mode. The loader is using the BIOS to load
the .boot file. Hence has from QNX loader code, very little has to do
with QNX itself. If there is already a problem at that point, it smells
like fishy hardware.