On Wednesday 23 June 2010, Andrew Johnson wrote:
> Hi Ben,
>
> On Wednesday 23 June 2010 08:19:44 Benjamin Franksen wrote:
> > The question is: what does the CA server do after it outputs these
> > error messages? Could it be it does something to the socket that makes
> > vxWorks throw up hands and strike? Also, note the 10 second delay
> > between the CAS message and the vxWorks message.
>
> I agree with Larry,the "ei0: reset" message comes from the ei82596End
> driver for the network chip, and is printed when its internal watchdog
> timer goes off implying that the transmitter has locked up (according to
> the comments in the source code, target/src/drv/end/ei82596End.c if you
> have it). I have certainly known this to happen if the network gets too
> busy for the OS to handle all of the packets, which seems possible in
> your circumstances.
>
> I'm not sure there's much you can do about it, other than try to enhance
> the ei driver to improve the recovery code (if you have the source
> code).
Hm, in our sources under target/src/drv/end I find no ei82596End.c, only
ln7990End.c. It says "END style AMD 7990 LANCE Ethernet network interface
driver" in the header comment. Is this where I should look?
Cheers
Ben
- References:
- strange ioc hangup Benjamin Franksen
- Re: strange ioc hangup Andrew Johnson
- Navigate by Date:
- Prev:
Pfeiffer Turbo Pump device driver Andrew C. Starritt
- Next:
Re: strange ioc hangup Benjamin Franksen
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: strange ioc hangup Andrew Johnson
- Next:
RE: strange ioc hangup Jeff Hill
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
<2010>
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|