Re: IOC crash when asyn traceflow turned on

[Eric Norum <norume@aps.anl.gov>]

Have a look at the interrupt handler code -- it should never call any  
of the asyn trace methods.  But it would appear that somehow this may  
be happening.

On Jul 31, 2009, at 11:30 AM, Shifu Xu wrote:

> Hi,
>
> I am trying to test an asyn based driver for the digitel multi-pump
> controller(MPC). The MPC is connected to MVME2100 through a bitbus
> controller VMOD-2 and a RS232 BUG(bitbus universal gateway). The  
> device
> support is part of sysApps package. The software module I also  
> loaded is
> asynSerialBUG, which is asyn support for the BUG.
>
> IOC(on vxWorks 5.5, base 3.14.10) works fine with asyn traceflow off.
> But it crashes when asyn traceflow turned on with the following info:
>
> 2009/07/30 16:53:14.088 PortA -1 exception 3 occurred calling
> exceptionUser
> 2009/07/30 16:53:14.088 PortA -1 exception 3 occurred calling
> exceptionUser
> 2009/07/30 16:53:14.088 xusf:asynRecord: exception 3
> 2009/07/30 16:53:15.872 PortA addr -1 queueRequest priority 0 not
> lockHolder
> 2009/07/30 16:53:15.872 PortA callback
>
> alignment
> alignment
>
> The console shows the following info after a VME crate reset.
>
> Exception at interrupt level:
>
> program
> Exception current instruction address: 0x0000b030
> Machine Status Register: 0x00089030
> Condition Register: 0x40000042
> Regs at 0x235760
> Link Register: 0x00104a3c
>
> Exception at interrupt level:
>
> data access
> Exception
>
> Has anybody experienced similar problem and how to fix it?
>
> Thanks,
> Shifu

--
Eric Norum <norume@aps.anl.gov>
Advanced Photon Source
Argonne National Laboratory
(630) 252-4793