From: Michael Stickel <michael@cubic.org>
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...
Date: Thu, 30 Jun 2005 08:25:42 +0200 [thread overview]
Message-ID: <42C39066.2060406@cubic.org> (raw)
In-Reply-To: <20050629.204246.102671266.imp@bsdimp.com>
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
next prev parent reply other threads:[~2005-06-30 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 21:53 Advice needed WRT very slow nfs in new port David Daney
2005-06-30 1:35 ` Problems with Intel e100 driver on new MIPS port, was: " David Daney
2005-06-30 1:57 ` M. Warner Losh
2005-06-30 2:33 ` David Daney
2005-06-30 2:42 ` M. Warner Losh
2005-06-30 6:25 ` Michael Stickel [this message]
2005-06-30 18:23 ` David Daney
-- strict thread matches above, loose matches on Subject: below --
2005-07-01 4:57 David Daney
2005-07-01 4:57 ` David Daney
2005-07-01 8:57 ` Maciej W. Rozycki
2005-07-01 9:00 ` Geert Uytterhoeven
2005-07-01 9:38 ` Maciej W. Rozycki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42C39066.2060406@cubic.org \
--to=michael@cubic.org \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox