Networking/Discussion/Networking Drivers/iopkt hangs after loading 2 differnet drivers/List of Posts
 
Forum Topic - iopkt hangs after loading 2 differnet drivers: (3 Items)
   
Update
Janani K
12/16/2009 11:58 PM
post43982
iopkt hangs after loading 2 differnet drivers   
Hi,

io-pkt hanged after loading 2 different drivers in QNX 6.4.1.
 
driver-1 (Resource Manager driver)
========
Here i m creating the resource manager and  network thread during io-pkt entry function.
I am handle the application messages in busy loop in my thread handler function.
 
Command for loading the driver
==============================
mount -T io-pkt devnp-driver1.so
 
driver-2 (network driver)
========
Its a network driver for handling the packets.
 
Command for loading the driver
===============================
mount -T io-pkt -oifname=tsec1-tsec2 devnp-driver2.so
 
I have a two different application to access those drivers.
application1 - for accessing resource manager driver.
application2 - for accessing the network driver
 
 
1.Loaded the driver1 successfully.
2.Run my application1  - its working successfully.
3.Loaded the driver2 successfuly.
4.Run my application2 - its hanged.
 
when i see the sloginfo ,i got the debug statements  "quiesce callout function".
This function is present in driver1(resource manager driver).
I dont know why the driver 1 quiesce callout function gets invoked while accessing the driver2.

Regards,
Janani
Andrew Boyd(deleted)
12/17/2009 8:32 AM
post44005
RE: iopkt hangs after loading 2 differnet drivers   
> io-pkt hanged  ...

This kind of problem is generally pretty easy to diagnose.

Run pidin, and get the pid of io-pkt.  Then run

  # dumper -p N

where N is the pid of io-pkt.  This will create a core
file, just as if io-pkt had faulted.

Then, using gdb, load the corefile and do a backtrace
of each of the threads.

--
aboyd
Sean Boudreau(deleted)
12/17/2009 8:49 AM
post44008
Re: iopkt hangs after loading 2 differnet drivers   
On Wed, Dec 16, 2009 at 11:58:53PM -0500, Janani K wrote:
> Hi,
> 
> io-pkt hanged after loading 2 different drivers in QNX 6.4.1.
>  

> when i see the sloginfo ,i got the debug statements  "quiesce callout function".
> This function is present in driver1(resource manager driver).
> I dont know why the driver 1 quiesce callout function gets invoked while accessing the driver2.
> 

Please check out this thread:

http://community.qnx.com/sf/discussion/do/listPosts/projects.networking/discussion.drivers.topc11227

You have to do more than spit out a debug message in your
quiesce_callout.

-seanb

Return