From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7326 invoked by alias); 11 Jan 2002 16:40:31 -0000 Mailing-List: contact ecos-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@sources.redhat.com Received: (qmail 7247 invoked from network); 11 Jan 2002 16:40:27 -0000 Received: from unknown (HELO ascomax.hasler.ascom.ch) (139.79.135.1) by sources.redhat.com with SMTP; 11 Jan 2002 16:40:27 -0000 Received: from eiger.ma.tech.ascom.ch (eiger.ma.tech.ascom.ch [139.79.100.1]) by ascomax.hasler.ascom.ch (8.11.4/8.11.4) with ESMTP id g0BGeNv25383; Fri, 11 Jan 2002 17:40:23 +0100 (MET) Received: from biferten.ma.tech.ascom.ch ([139.79.100.27]) by eiger.ma.tech.ascom.ch with smtp (Exim 3.16 #1) id 16P4j7-0002uw-00; Fri, 11 Jan 2002 17:40:21 +0100 Received: by biferten.ma.tech.ascom.ch (SMI-8.6/SMI-SVR4) id RAA22947; Fri, 11 Jan 2002 17:40:18 +0100 Date: Fri, 11 Jan 2002 08:40:00 -0000 From: Andrew Lunn To: Andrea Acquaviva Cc: eCos Disuss Message-ID: <20020111174018.C22918@biferten.ma.tech.ascom.ch> Mail-Followup-To: Andrea Acquaviva , eCos Disuss References: <3C3F1275.D1CA436B@deis.unibo.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3C3F1275.D1CA436B@deis.unibo.it>; from aacquaviva@deis.unibo.it on Fri, Jan 11, 2002 at 05:27:33PM +0100 X-Filter-Version: 1.6 (ascomax) Subject: Re: [ECOS] network problem X-SW-Source: 2002-01/txt/msg00158.txt.bz2 On Fri, Jan 11, 2002 at 05:27:33PM +0100, Andrea Acquaviva wrote: > Hi, > > I found a problem while using the CF ethernet interface on assabet > board. > After the network initialization made by init_all_network_interfaces(), > I put the program in an idle state (while(1)) and I try to ping the > interface. The interface reply to the ping request for a certain amount > of time and then blocks. > The strange thing is that this amount of time increase if I add some > debugging output when the packet are received. > > Someone can suggest me an explanation? Remember that eCos is an RTOS. A high priority thread which is runnable will always be run instead of a low priority thread. The network stack is implemented as threads as well. So if your endless loop is running at a higher priority then the network stack, don't expect the network stack to work. Now the strange thing. You say it works for a while. That i don't understand. It should work, or it should not work. What are you actually pinging. The application stack or the redboot stack? The redboot stack may keep working under these conditions since its not thread based. The debug output would also help since it gives redboot more time to actually process network traffic for it. Also, some network drivers have a low priority tickle thread. This thread is used to recover from hardware errors in some ethernet devices. They lockup under some conditions and the tickle thread will bring them back to life. Maybe your endless loop is stopping this tickle thread and so you are seeing the hardware error. Andrew