> -----Message d'origine-----
> De : Sean Boudreau [mailto:community-noreply@qnx.com]
> Envoyé : 26 octobre 2010 14:13
> À : general-networking
> Objet : Re: stack_interrupt_remove
> 
> On Tue, Oct 26, 2010 at 01:20:46PM -0400, Mario Charest wrote:
> > we have a system at a customer site where io-pkt-v4 ( 6.5.0 )
> > terminate on its owm.  sloginfo buffer contains
> >
> > stack_interrupt_remove: unexpected context
> >
> > What could cause this?
> >
> 
> Calling it from an unexpected context :)  Probably while handling an
> interrupt.  Which driver is it?

Its e1000.  Hugh has given me a beta version to try it, but we are currently trying the original e1000 which is giving 
us grief as well (no detail for now)

We have instances were io-pkt-v4 just goes away , with no message in the slog

> 
> Regards,
> 
> -seanb
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post72487
> 

I have seen two sloginfo entries I've never seen before:

vtid_lookup() client_loopkup(-1) failed
inbound_signal() NetSignalKill(-1896480) failed from nd 5


> -----Message d'origine-----
> De : Sean Boudreau [mailto:community-noreply@qnx.com]
> Envoyé : 26 octobre 2010 14:13
> À : general-networking
> Objet : Re: stack_interrupt_remove
> 
> On Tue, Oct 26, 2010 at 01:20:46PM -0400, Mario Charest wrote:
> > we have a system at a customer site where io-pkt-v4 ( 6.5.0 )
> > terminate on its owm.  sloginfo buffer contains
> >
> > stack_interrupt_remove: unexpected context
> >
> > What could cause this?
> >
> 
> Calling it from an unexpected context :)  Probably while handling an
> interrupt.  Which driver is it?
> 
> Regards,
> 
> -seanb
> 
> 
> 
> _______________________________________________
> 
> General
> http://community.qnx.com/sf/go/post72487
>