What signal can QNX4.24 shutdown

Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24 shutdown
suddenly, first I’ll exclude the possibility of DDos and similar network
attack, can some physical signal cause it’s down?

And how can I protect my OS from ethernet?

Best regards.

Maa

2004-09-16

“Maa” <maa_vip@sina.com> wrote in message news:cibcip$hco$1@inn.qnx.com

Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24 shutdown
suddenly, first I’ll exclude the possibility of DDos and similar network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.

And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access, not
just shutdown?

Best regards.

Maa

2004-09-16

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online cable
user number near 500, CMTS would freeze sometime just like run out suddenly.
And the screen display normal information, but keyboard had not any response
when I beat it, and also I can’t change to any other console in QNX, so I
think it freeze. And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.

If exclude the possibility of the number of cable users, I just want to know
what’s wrong cause this happened, QNX OS? or the other things?

Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <nowheretobefound@8thdimension.com> дÈëÏûÏ¢
news:cibud0$2kf$1@inn.qnx.com

“Maa” <> maa_vip@sina.com> > wrote in message news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access, not
just shutdown?


Best regards.

Maa

2004-09-16
\

“Maa” <maa_vip@sina.com> wrote in message news:cidnb3$cpa$1@inn.qnx.com

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.



And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the screen
information changing? Are you using Photon, QWindows or are in text mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.


Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16


\

“Maa” <maa_vip@sina.com> wrote in message news:cidnb3$cpa$1@inn.qnx.com

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.



And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the screen
information changing? Are you using Photon, QWindows or are in text mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.


Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16


\

We use QNX 4.24 and develope our our boards for a system built upon 3U
cPCI. I’ve seen the QNX OS freeze, console, keyboard, everything as the
result of interrupts.

Our most recent occurrence arose when one of our boards was asserting
their interrupt request line and then holding it there. I supposed the
QNX ISR was taking 100% of the CPU to acknowledge the stuck interrupt
request. I too suspect the interrupt handler.

Charlie


Mario Charest wrote:

“Maa” <> maa_vip@sina.com> > wrote in message news:cidnb3$cpa$> 1@inn.qnx.com> …

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.



And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so I
think it freeze.


If you press NumLock does the light on the keyboard toggles. Is the screen
information changing? Are you using Photon, QWindows or are in text mode?


And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?


Well a kernel crash could cause a free (if the machine is in text mode you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …

Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24

shutdown

suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16




\

“Charlie” <cwilliamp@yahoo.com> wrote in message
news:ciemb5$724$1@inn.qnx.com

We use QNX 4.24 and develope our our boards for a system built upon 3U
cPCI. I’ve seen the QNX OS freeze, console, keyboard, everything as the
result of interrupts.

Our most recent occurrence arose when one of our boards was asserting
their interrupt request line and then holding it there. I supposed the QNX
ISR was taking 100% of the CPU to acknowledge the stuck interrupt request.
I too suspect the interrupt handler.

Most probably the ISQ line isn’t cleared and the ISR is called at a frantic
pace :wink:

Get as much code out of the ISR as possible (easier said then done). There
are nasty do debug. I like to user an IO card and trigger some IO’s that I
can monitor with a scope to tell me what the code is doing.


Charlie


Mario Charest wrote:
“Maa” <> maa_vip@sina.com> > wrote in message
news:cidnb3$cpa$> 1@inn.qnx.com> …

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.



And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so I
think it freeze.


If you press NumLock does the light on the keyboard toggles. Is the
screen
information changing? Are you using Photon, QWindows or are in text
mode?


And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?


Well a kernel crash could cause a free (if the machine is in text mode
you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …

Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24

shutdown

suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16





\

Mario, when the system freeze, there had not any response when I press
NumLock and CapsLock keys. And the screen information did not change, it
seems normally but stagnantly.

Our QNX4.24/4.25 system is in text mode.

Dear Mario, what does kernel crash means, it is interrupt crash just as
Charlie said, or another? And how can I check kernel crash info, please tell
me, okay?

But I still had a question, the system would freeze in PIII but restart in
PII mainboard, why?

And best regards to everyone!
Maa
2004-09-18

“Mario Charest” <nowheretobefound@8thdimension.com> дÈëÏûÏ¢
news:ciei2f$443$2@inn.qnx.com

“Maa” <> maa_vip@sina.com> > wrote in message news:cidnb3$cpa$> 1@inn.qnx.com> …
Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.


And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so
I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the screen
information changing? Are you using Photon, QWindows or are in text mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16





\

Dear Charlie, our system is similar to yours, QNX424 and cpci bus. And I
just want to know how can you check your interrupt handler when your system
had freezed, and thank you very much.

Maa
2004-09-18
“Charlie” <cwilliamp@yahoo.com> ??? news:ciemb5$724$1@inn.qnx.com

We use QNX 4.24 and develope our our boards for a system built upon 3U
cPCI. I’ve seen the QNX OS freeze, console, keyboard, everything as the
result of interrupts.

Our most recent occurrence arose when one of our boards was asserting
their interrupt request line and then holding it there. I supposed the
QNX ISR was taking 100% of the CPU to acknowledge the stuck interrupt
request. I too suspect the interrupt handler.

Charlie


Mario Charest wrote:
“Maa” <> maa_vip@sina.com> > wrote in message
news:cidnb3$cpa$> 1@inn.qnx.com> …

Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.



And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so
I
think it freeze.


If you press NumLock does the light on the keyboard toggles. Is the
screen
information changing? Are you using Photon, QWindows or are in text
mode?


And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?


Well a kernel crash could cause a free (if the machine is in text mode
you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …

Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24

shutdown

suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16





\

“Maa” <maa_vip@sina.com> wrote in message news:cifakj$m2a$1@inn.qnx.com

Mario, when the system freeze, there had not any response when I press
NumLock and CapsLock keys. And the screen information did not change, it
seems normally but stagnantly.

Our QNX4.24/4.25 system is in text mode.

Dear Mario, what does kernel crash means, it is interrupt crash just as
Charlie said, or another? And how can I check kernel crash info, please
tell
me, okay?

A kernel crash is in a nutshell a SIGSEGV done by the kernel. The screen
(if in text mode) would fill with info and message. If you see it you
figure it out easy.

But I still had a question, the system would freeze in PIII but restart in
PII mainboard, why?

The hardware may behave directly if an interrupt line is stuck for extensive
period of time (just a guest)

And best regards to everyone!
Maa
2004-09-18

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:ciei2f$443$> 2@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cidnb3$cpa$> 1@inn.qnx.com> …
Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me
describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS
and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.


And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX, so
I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the
screen
information changing? Are you using Photon, QWindows or are in text
mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode
you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all access,
not
just shutdown?


Best regards.

Maa

2004-09-16







\

“The screen (if in text mode) would fill with info and message.”

What does it means Mario?

Is the screen filled with info and message after a kernel crash? And what’s
the info?When our system freezed, the screen(text mode) would not other info
except normal print info.

By my experience, the signal SIGSEGV could only let process terminated, and
never lead system freeze, is this right?

When you encounter the system freeze, what did you do to solve the trouble?

Maa
2004-09-18
“Mario Charest” <nowheretobefound@8thdimension.com> дÈëÏûÏ¢
news:cifedo$oj7$1@inn.qnx.com

“Maa” <> maa_vip@sina.com> > wrote in message news:cifakj$m2a$> 1@inn.qnx.com> …
Mario, when the system freeze, there had not any response when I press
NumLock and CapsLock keys. And the screen information did not change, it
seems normally but stagnantly.

Our QNX4.24/4.25 system is in text mode.

Dear Mario, what does kernel crash means, it is interrupt crash just as
Charlie said, or another? And how can I check kernel crash info, please
tell
me, okay?

A kernel crash is in a nutshell a SIGSEGV done by the kernel. The screen
(if in text mode) would fill with info and message. If you see it you
figure it out easy.


But I still had a question, the system would freeze in PIII but restart
in
PII mainboard, why?

The hardware may behave directly if an interrupt line is stuck for
extensive
period of time (just a guest)


And best regards to everyone!
Maa
2004-09-18

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:ciei2f$443$> 2@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cidnb3$cpa$> 1@inn.qnx.com> …
Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me
describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS
and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.


And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX,
so
I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the
screen
information changing? Are you using Photon, QWindows or are in text
mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want
to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode
you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another
QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all
access,
not
just shutdown?


Best regards.

Maa

2004-09-16









\

“Maa” <maa_vip@sina.com> wrote in message news:cig9u1$e22$1@inn.qnx.com

“The screen (if in text mode) would fill with info and message.”

What does it means Mario?


Is the screen filled with info and message after a kernel crash? And
what’s
the info?When our system freezed, the screen(text mode) would not other
info
except normal print info.

It means the kernel will dump on the screen lots of information about
registers content, stack content etc. Fill about 3/4 of the screen and
overwrite anything that is there.

By my experience, the signal SIGSEGV could only let process terminated,
and
never lead system freeze, is this right?

Right. Well if dumper is running the system may appear to freeze for a
while because dumper is set to high priority. If the process used LOTS of
ram let say 120Meg and crashed. With an IDE device on QNX4 you are looking
at 3Meg per seconds which means the machine will appear to be unresponsive
for about 40 seconds (numlock will work though, i think)

When you encounter the system freeze, what did you do to solve the
trouble?

If it’s not hardware, the problem is usually interrupts. First I will look
at the code for
any possible endless loop, attempt to make the code handle any possibility
of having the hardware misbehave.

After that I will use some externel device, parallel port, io card,
Diagnotic post card. I insert in ISR code that will let me trace what the
ISR is doing and where it frooze.

ISR ()
{

outp( 0x80, 1);
do_this();
outp( 0x80, 2);
do_that();
for( ; test; )
{
outp( 0x80, 3);
do_something();
outp( 0x80, 4 )
}
do_nothing();
outp( 0x80, 5);
}


in this example, outp write to a Diagnostic Post Card, which is basicaly
just 2 7segment LED. The number outputed to 0x80 gets display on the card.
When the machine freeze I just have to look at the number on the LED to know
where the code frooze.

LED isn’t the best thing because if stuck in the for loop the LED content
will flicker at speed to fast for the eye to see.

I also use parallel port pin that I look at via a osciloscope.


















The screen

(if in text mode) would fill with info and message. If you see it you
figure it out easy.


But I still had a question, the system would freeze in PIII but restart
in
PII mainboard, why?

The hardware may behave directly if an interrupt line is stuck for
extensive
period of time (just a guest)


And best regards to everyone!
Maa
2004-09-18

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:ciei2f$443$> 2@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cidnb3$cpa$> 1@inn.qnx.com> …
Thank you very much, dear Mario.

Shutdown that I mean is freeze just as your said, please let me
describe
what had happened on our device.

Maybe you are familiar with our device(CMTS), it based on QNX4.24 OS
and
Broadcom’s project. One of our client say that after the CMTS online
cable
user number near 500, CMTS would freeze sometime just like run out
suddenly.


And the screen display normal information, but keyboard had not any
response
when I beat it, and also I can’t change to any other console in QNX,
so
I
think it freeze.

If you press NumLock does the light on the keyboard toggles. Is the
screen
information changing? Are you using Photon, QWindows or are in text
mode?

And it’s mainboard is PIII mainboard, made in China.

When I use a PII motolora mainboard(CPV5300) instead of the PIII
mainboard,
the CMTS would not freeze again, but sometimes it may be restart
automatically.


If exclude the possibility of the number of cable users, I just want
to
know
what’s wrong cause this happened, QNX OS? or the other things?

Well a kernel crash could cause a free (if the machine is in text mode
you
would
see kernel crash info, in graphic mode you don’t see it).

Problem with your own software could do it, mainly interrupt handler.



Best Regards to all of you
Maa
2004-09-17

“Mario Charest” <> nowheretobefound@8thdimension.com> > дÈëÏûÏ¢
news:cibud0$2kf$> 1@inn.qnx.com> …

“Maa” <> maa_vip@sina.com> > wrote in message
news:cibcip$hco$> 1@inn.qnx.com> …
Hello everyone,

I really want to know what signal from ethernet can cause QNX4.24
shutdown
suddenly, first I’ll exclude the possibility of DDos and similar
network
attack, can some physical signal cause it’s down?

A shutdown message to PROC would. It can only be sent by another
QNX
machine.
By shutdown do you mean “shutdown” or freeze.


And how can I protect my OS from ethernet?

There are option to prevent inbound access but it disables all
access,
not
just shutdown?


Best regards.

Maa

2004-09-16











\

Mario Charest <nowheretobefound@8thdimension.com> wrote:

MC > “Maa” <maa_vip@sina.com> wrote in message news:cig9u1$e22$1@inn.qnx.com

“The screen (if in text mode) would fill with info and message.”

What does it means Mario?


Is the screen filled with info and message after a kernel crash? And
what’s
the info?When our system freezed, the screen(text mode) would not other
info
except normal print info.

MC > It means the kernel will dump on the screen lots of information about
MC > registers content, stack content etc. Fill about 3/4 of the screen and
MC > overwrite anything that is there.

The fact that you don’t see this information indicates that you did not have
a kernel fault.


MC > After that I will use some externel device, parallel port, io card,
MC > Diagnotic post card. I insert in ISR code that will let me trace what the
MC > ISR is doing and where it frooze.

MC > ISR ()
MC > {

MC > outp( 0x80, 1);
MC > do_this();
MC > outp( 0x80, 2);
MC > do_that();
MC > for( ; test; )
MC > {
MC > outp( 0x80, 3);
MC > do_something();
MC > outp( 0x80, 4 )
MC > }
MC > do_nothing();
MC > outp( 0x80, 5);
MC > }


MC > in this example, outp write to a Diagnostic Post Card, which is basicaly
MC > just 2 7segment LED. The number outputed to 0x80 gets display on the card.
MC > When the machine freeze I just have to look at the number on the LED to know
MC > where the code frooze.

MC > LED isn’t the best thing because if stuck in the for loop the LED content
MC > will flicker at speed to fast for the eye to see.

MC > I also use parallel port pin that I look at via a osciloscope.

MicroScope 2000 (search the web) makes such a diagnostic device.
It is a fantastic device for debugging interrupt handlers. I have used as
many as three such devices to monitor internal staus of things in an
interrupt handler.

Thank you very much, Bill.

I’ll try it just like your said, actually I’m a new member in the newgroup
of QNX development, but so many friends are glad to help me to sovle my
problem, and I just want thank all of you again, Bill, David, Mario and the
others, thank you.

Good night everyone.
Maa
2004-09-20
“Bill Caroselli” <qtps@earthlink.net> дÈëÏûÏ¢
news:cimqs9$bet$1@inn.qnx.com

Mario Charest <> nowheretobefound@8thdimension.com> > wrote:

MC > “Maa” <> maa_vip@sina.com> > wrote in message
news:cig9u1$e22$> 1@inn.qnx.com> …
“The screen (if in text mode) would fill with info and message.”

What does it means Mario?


Is the screen filled with info and message after a kernel crash? And
what’s
the info?When our system freezed, the screen(text mode) would not other
info
except normal print info.

MC > It means the kernel will dump on the screen lots of information about
MC > registers content, stack content etc. Fill about 3/4 of the screen
and
MC > overwrite anything that is there.

The fact that you don’t see this information indicates that you did not
have
a kernel fault.


MC > After that I will use some externel device, parallel port, io card,
MC > Diagnotic post card. I insert in ISR code that will let me trace
what the
MC > ISR is doing and where it frooze.

MC > ISR ()
MC > {

MC > outp( 0x80, 1);
MC > do_this();
MC > outp( 0x80, 2);
MC > do_that();
MC > for( ; test; )
MC > {
MC > outp( 0x80, 3);
MC > do_something();
MC > outp( 0x80, 4 )
MC > }
MC > do_nothing();
MC > outp( 0x80, 5);
MC > }


MC > in this example, outp write to a Diagnostic Post Card, which is
basicaly
MC > just 2 7segment LED. The number outputed to 0x80 gets display on the
card.
MC > When the machine freeze I just have to look at the number on the LED
to know
MC > where the code frooze.

MC > LED isn’t the best thing because if stuck in the for loop the LED
content
MC > will flicker at speed to fast for the eye to see.

MC > I also use parallel port pin that I look at via a osciloscope.

MicroScope 2000 (search the web) makes such a diagnostic device.
It is a fantastic device for debugging interrupt handlers. I have used as
many as three such devices to monitor internal staus of things in an
interrupt handler.

Oh, Bill, I can not download any microscope2000 what you said, maybe it is
not a shared software.

How can I get it or it’s trial edition?

Maa
2004-09-20

“Bill Caroselli” <qtps@earthlink.net> дÈëÏûÏ¢
news:cimqs9$bet$1@inn.qnx.com

Mario Charest <> nowheretobefound@8thdimension.com> > wrote:

MC > “Maa” <> maa_vip@sina.com> > wrote in message
news:cig9u1$e22$> 1@inn.qnx.com> …
“The screen (if in text mode) would fill with info and message.”

What does it means Mario?


Is the screen filled with info and message after a kernel crash? And
what’s
the info?When our system freezed, the screen(text mode) would not other
info
except normal print info.

MC > It means the kernel will dump on the screen lots of information about
MC > registers content, stack content etc. Fill about 3/4 of the screen
and
MC > overwrite anything that is there.

The fact that you don’t see this information indicates that you did not
have
a kernel fault.


MC > After that I will use some externel device, parallel port, io card,
MC > Diagnotic post card. I insert in ISR code that will let me trace
what the
MC > ISR is doing and where it frooze.

MC > ISR ()
MC > {

MC > outp( 0x80, 1);
MC > do_this();
MC > outp( 0x80, 2);
MC > do_that();
MC > for( ; test; )
MC > {
MC > outp( 0x80, 3);
MC > do_something();
MC > outp( 0x80, 4 )
MC > }
MC > do_nothing();
MC > outp( 0x80, 5);
MC > }


MC > in this example, outp write to a Diagnostic Post Card, which is
basicaly
MC > just 2 7segment LED. The number outputed to 0x80 gets display on the
card.
MC > When the machine freeze I just have to look at the number on the LED
to know
MC > where the code frooze.

MC > LED isn’t the best thing because if stuck in the for loop the LED
content
MC > will flicker at speed to fast for the eye to see.

MC > I also use parallel port pin that I look at via a osciloscope.

MicroScope 2000 (search the web) makes such a diagnostic device.
It is a fantastic device for debugging interrupt handlers. I have used as
many as three such devices to monitor internal staus of things in an
interrupt handler.

“Maa” <maa@vip.sina.com> wrote in message news:cimvbu$fip$1@inn.qnx.com

Oh, Bill, I can not download any microscope2000 what you said, maybe it is
not a shared software.

It mostly hardware, unless there is a new technology that I don’t know
about, you can’t download it :wink:

http://www.m2k.co.uk/products/microscope/microscope.html


How can I get it or it’s trial edition?

Maa
2004-09-20

“Bill Caroselli” <> qtps@earthlink.net> > дÈëÏûÏ¢
news:cimqs9$bet$> 1@inn.qnx.com> …
Mario Charest <> nowheretobefound@8thdimension.com> > wrote:

MC > “Maa” <> maa_vip@sina.com> > wrote in message
news:cig9u1$e22$> 1@inn.qnx.com> …
“The screen (if in text mode) would fill with info and message.”

What does it means Mario?


Is the screen filled with info and message after a kernel crash? And
what’s
the info?When our system freezed, the screen(text mode) would not
other
info
except normal print info.

MC > It means the kernel will dump on the screen lots of information
about
MC > registers content, stack content etc. Fill about 3/4 of the screen
and
MC > overwrite anything that is there.

The fact that you don’t see this information indicates that you did not
have
a kernel fault.


MC > After that I will use some externel device, parallel port, io card,
MC > Diagnotic post card. I insert in ISR code that will let me trace
what the
MC > ISR is doing and where it frooze.

MC > ISR ()
MC > {

MC > outp( 0x80, 1);
MC > do_this();
MC > outp( 0x80, 2);
MC > do_that();
MC > for( ; test; )
MC > {
MC > outp( 0x80, 3);
MC > do_something();
MC > outp( 0x80, 4 )
MC > }
MC > do_nothing();
MC > outp( 0x80, 5);
MC > }


MC > in this example, outp write to a Diagnostic Post Card, which is
basicaly
MC > just 2 7segment LED. The number outputed to 0x80 gets display on
the
card.
MC > When the machine freeze I just have to look at the number on the LED
to know
MC > where the code frooze.

MC > LED isn’t the best thing because if stuck in the for loop the LED
content
MC > will flicker at speed to fast for the eye to see.

MC > I also use parallel port pin that I look at via a osciloscope.

MicroScope 2000 (search the web) makes such a diagnostic device.
It is a fantastic device for debugging interrupt handlers. I have used
as
many as three such devices to monitor internal staus of things in an
interrupt handler.

Maa <maa@vip.sina.com> wrote:
M > Oh, Bill, I can not download any microscope2000 what you said, maybe it is
M > not a shared software.

M > How can I get it or it’s trial edition?

M > Maa
M > 2004-09-20

The thing I was talking about isn’t software, it’s a hardware device.

Strangely enough I couldn’t find it with a Google search either. However,
here is their web site from their documentation.

http://www.micro2000.com

The device I was speaking of is at:
http://www.micro2000.com/postprobe/index.php

It will plug into either a PCI or ISA bus. You write to a register on the
card and that value shows up on the 2 seven segment LEDS.

It mostly hardware, unless there is a new technology that I don’t know
about, you can’t download it > :wink:

“Beam me down that new framus, Scotty.”