Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - Question about devn-speedo patch (ID 685): (4 Items)
   
Question about devn-speedo patch (ID 685)  
We are experiencing occasional crashes of io-net and in the course of investigations found that the devn-speedo  we are 
using has a patch as part of patch ID 685 to address the following issues:  

devn-speedo.so

        * We've added a TX_FLUSH devctl() command to support the Liteweight L4 version of Qnet.
        * We corrected the initialization of the io-net endpoint.
        * If you specify the verbose option, the driver logs transmission errors to sloginfo.
        * This driver no longer delays for 10 milliseconds when io-net sends it a devctl() command. (Ref# 23331; Ticket 
ID 68013)
        * We've added a probe_phy option that lets you control periodic PHY probing with respect to packet loss under 
load. (Ref# 28648)

Since we don't (appear) to have any other network related issues, I'm not sure that any of these apply to use in general
, but I'm not sure what problems these actually cause?  The initialization of the endpoint appears interesting, but it 
may be "benign"..  

My question is it worth updating to this patch?  These are customer sites and it will require some effort that I'd 
rather not go though (as well as the associated risk) if there doesn't appear to be much benefit...

The systems in question are 6.3 SP3.

TIA!
Re: Question about devn-speedo patch (ID 685)  
The only way you will find out is to download the patch from our web site
and try it.


On 11-01-05 9:52 AM, "Jason Johnson" <community-noreply@qnx.com> wrote:

> We are experiencing occasional crashes of io-net and in the course of
> investigations found that the devn-speedo  we are using has a patch as part of
> patch ID 685 to address the following issues:
> 
> devn-speedo.so
> 
>         * We've added a TX_FLUSH devctl() command to support the Liteweight L4
> version of Qnet.
>         * We corrected the initialization of the io-net endpoint.
>         * If you specify the verbose option, the driver logs transmission
> errors to sloginfo.
>         * This driver no longer delays for 10 milliseconds when io-net sends
> it a devctl() command. (Ref# 23331; Ticket ID 68013)
>         * We've added a probe_phy option that lets you control periodic PHY
> probing with respect to packet loss under load. (Ref# 28648)
> 
> Since we don't (appear) to have any other network related issues, I'm not sure
> that any of these apply to use in general, but I'm not sure what problems
> these actually cause?  The initialization of the endpoint appears interesting,
> but it may be "benign"..
> 
> My question is it worth updating to this patch?  These are customer sites and
> it will require some effort that I'd rather not go though (as well as the
> associated risk) if there doesn't appear to be much benefit...
> 
> The systems in question are 6.3 SP3.
> 
> TIA!
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post81190
> 
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8
 


Re: Question about devn-speedo patch (ID 685)  
            
  " The only way you will find out is to download the patch from our web site
and try it."

Thanks for the reply Hugh, and I guess I assumed that from the beginning, but I am trying to weight the potential of 
reward against risk of disruption for our customer and effort of our engineering staff.  Can you tell me, iyo, is there 
anything in that patch that COULD cause this type of thing?  I understand the only way to know if it fixes our issue is 
to try it, but I don't want to try it if there really isn't anything in the patch that would cause it.  

Thanks!!!!
Re: Question about devn-speedo patch (ID 685)  
This is difficult to say, as the driver was updated 3 years ago! There were
also some changes made to acquire a mutex, so it might solve your problem.
The only way to find out is to try it out on one site where the problem is
occurring. If the problem still exists after trying the patch, then we will
have to take a look at the driver and see if we can reproduce and fix the
problem.


On 11-01-10 9:59 AM, "Jason Johnson" <community-noreply@qnx.com> wrote:

> 
> 
>            
>   " The only way you will find out is to download the patch from our web site
> and try it."
> 
> Thanks for the reply Hugh, and I guess I assumed that from the beginning, but
> I am trying to weight the potential of reward against risk of disruption for
> our customer and effort of our engineering staff.  Can you tell me, iyo, is
> there anything in that patch that COULD cause this type of thing?  I
> understand the only way to know if it fixes our issue is to try it, but I
> don't want to try it if there really isn't anything in the patch that would
> cause it. 
> 
> Thanks!!!!
> 
> 
> 
> _______________________________________________
> 
> Networking Drivers
> http://community.qnx.com/sf/go/post81689
> 
> 

-- 
Hugh Brown                      (613) 591-0931 ext. 2209 (voice)
QNX Software Systems Ltd.        (613) 591-3579           (fax)
175 Terence Matthews Cres.       email:  hsbrown@qnx.com
Kanata, Ontario, Canada.
K2M 1W8