linux-mips
[Top] [All Lists]

Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed

To: linux-mips@linux-mips.org
Subject: Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port...
From: Michael Stickel <michael@cubic.org>
Date: Thu, 30 Jun 2005 08:25:42 +0200
In-reply-to: <20050629.204246.102671266.imp@bsdimp.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <42C34C4D.9020902@avtrex.com> <20050629.195743.48512936.imp@bsdimp.com> <42C359F8.4060000@avtrex.com> <20050629.204246.102671266.imp@bsdimp.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
M. Warner Losh wrote:

In message: <42C359F8.4060000@avtrex.com>
           David Daney <ddaney@avtrex.com> writes:
: M. Warner Losh wrote:
: > In message: <42C34C4D.9020902@avtrex.com>
: >             David Daney <ddaney@avtrex.com> writes:
: > : Does anyone have any idea what would cause 1000mS delay?
: > : > That's remarkably close to 1s. This often indicates that the transmit
: > of your next packet is causing the receive buffer to empty.  This is
: > usually due to blocked interrupts, or a failure to enable interrupts.
: > : : But I observe ever increasing counts for the device in /proc/interrupts. : So the interrupts are working somewhat.

Are you sure that you've routed the interrupts correctly?  Maybe those
interrupts are 'really' for a different device....
Add some debugging to the interrupt routine of the e100 and see what happens.

Michael


<Prev in Thread] Current Thread [Next in Thread>