From: Jeff Garzik <jgarzik@pobox.com>
To: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: eth0: Too much work in interrupt, status e401
Date: Sun, 11 May 2003 20:47:52 -0400 [thread overview]
Message-ID: <3EBEEF38.1070008@pobox.com> (raw)
In-Reply-To: <1052699512.662.3.camel@teapot.felipe-alfaro.com>
Felipe Alfaro Solana wrote:
> Hi!
>
> I'm having severe hardlocks with 2.5.69-mm3 when mounting an NFS volume
> from one of my NFS servers. I think this is related to iptables, but
> while investigating, I found the following messages on my dmesg ring:
>
> spurious 8259A interrupt: IRQ7.
> eth0: Setting full-duplex based on MII #0 link partner capability of
> 01e1.
> eth0: Transmit error, Tx status register 90.
Check out REPORTING-BUGS file in the kernel source code. It describes
the information we find useful in bug reports. In particularly, you did
not give us any information on your network hardware (network card, and
what it is connected to) or what drivers you have loaded.
Jeff
next prev parent reply other threads:[~2003-05-12 0:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 0:31 eth0: Too much work in interrupt, status e401 Felipe Alfaro Solana
2003-05-12 0:47 ` Jeff Garzik [this message]
2003-05-12 9:18 ` Felipe Alfaro Solana
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=3EBEEF38.1070008@pobox.com \
--to=jgarzik@pobox.com \
--cc=felipe_alfaro@linuxmail.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.