Jorge <jalonso@ain.es> wrote:
Quote:
Hello,
I have just intalled QNX 6.3.0 SP3 in a machine, and I have 2 problems
that I can't solve.
My first and important problem has to do with a ramdomly freeze of the
operating system. I start QNX, I can work properly (there is no problem
or I can't see any problem at least). But some time later (a ramdom
time), QNX is frozen. I don't know what happen because I can't use
keyboard, mouse, .... I suppose that two things can produce the problem
(100 % of CPU time is busy):
- a hardware interrupt that is constantly ask for time
- a high priority thread that runs without control.
How can I identify the problem? and how can I solve this problem? Is
there any bug in this QNX version? I don't think so, but...
You can try the "hogs" utility. It loops and lists the processes that
are using the CPU. For example, run this in an extra window:
hogs -n -%5
The -n option says to disply the process name, and the -% option specifies
the minimum CPU usage to display (which lets you omit processes that are
idle or using small amounts of CPUtime).
Quote:
The second problem is about qnet. I have installed in other machine QNX
6.2.1A, and I can't see it from my new QNX 6.3.0 SP3. Is there qnet
compatibility from QNX 6.2.1A to 6.3.0 SP3? or Do I need to indicate to
qnet that I want to see other QNX version with some param?
As someone else mentioned, you need to use npm-qnet_compat.so (make
npm-qnet.so a symlink to it).
------------------------------------------
Steve Reid stever@qnx.com
Technical Editor
QNX Software Systems
------------------------------------------ |
FAQ
Search
Register
Log in to check your private messages
Log in
