| To: | ddaney@avtrex.com |
|---|---|
| Subject: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port... |
| From: | "M. Warner Losh" <imp@bsdimp.com> |
| Date: | Wed, 29 Jun 2005 20:42:46 -0600 (MDT) |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <42C359F8.4060000@avtrex.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <42C34C4D.9020902@avtrex.com> <20050629.195743.48512936.imp@bsdimp.com> <42C359F8.4060000@avtrex.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
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.... Warner |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., David Daney |
|---|---|
| Next by Date: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., Michael Stickel |
| Previous by Thread: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., David Daney |
| Next by Thread: | Re: Problems with Intel e100 driver on new MIPS port, was: Advice needed WRT very slow nfs in new port..., Michael Stickel |
| Indexes: | [Date] [Thread] [Top] [All Lists] |