io-net shutdown -> system is hang

QNX Newsgroups (Archives) qdn.public.ddk.network
1

Hi,

if io-net gone to shutdown by reason of some error –
then OS qnx6.1 is hanged (dead) !!!

why is it ?

vasa

2

If, in the shutdown callbacks of the driver, the card is not properly shutdown
it can keep DMAing data into memory that has since been given to other
processes. This is bad. Are you using a driver you have written or one of
ours?

chris


vasa <vv40in@rambler.ru> wrote:

Hi,

if io-net gone to shutdown by reason of some error –
then OS qnx6.1 is hanged (dead) !!!

why is it ?

vasa

\

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

3

If, in the shutdown callbacks of the driver, the card is not properly
shutdown
it can keep DMAing data into memory that has since been given to other
processes. This is bad. Are you using a driver you have written or one
of
ours?

yes.
devn-el900.so
it was started automatically (I do not correct it load params manually)

the netcard (single on mather):
3com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)

Example of fault situation – if my intermediate driver allocates too big
stack.

vasa

4

Yes, I belive this has already been fixed. I think it was a change in
io-net and should probably show-up in 6.1.1.

chris


vasa <vv40in@rambler.ru> wrote:

If, in the shutdown callbacks of the driver, the card is not properly
shutdown
it can keep DMAing data into memory that has since been given to other
processes. This is bad. Are you using a driver you have written or one
of
ours?

yes.
devn-el900.so
it was started automatically (I do not correct it load params manually)

the netcard (single on mather):
3com EtherLink XL 10/100 PCI TX NIC (3C905B-TX)

Example of fault situation – if my intermediate driver allocates too big
stack.

vasa







\

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

5

Yes, I belive this has already been fixed. I think it was a change in
io-net and should probably show-up in 6.1.1.

sorry, what is it – 6.1.1 ?
may be qnx6.1 patchA ?

vasa

6

vasa <vv40in@rambler.ru> wrote:

Yes, I belive this has already been fixed. I think it was a change in
io-net and should probably show-up in 6.1.1.

sorry, what is it – 6.1.1 ?
may be qnx6.1 patchA ?

I am not sure if the fix made it into 6.1.0A but I know it will be in
place for 6.1.1 (next release).

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

7

I am not sure if the fix made it into 6.1.0A but I know it will be in
place for 6.1.1 (next release).

when will it (qnx6.1.1) be ready ?

vasa

8

vasa <vv40in@rambler.ru> wrote:

I am not sure if the fix made it into 6.1.0A but I know it will be in
place for 6.1.1 (next release).

when will it (qnx6.1.1) be ready ?

Dunno.

chris

–

cdm@qnx.com > “The faster I go, the behinder I get.”

Chris McKillop – Lewis Carroll –
Software Engineer, QSSL
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<