From: Ivan Vecera <ivecera@redhat.com>
To: netdev@vger.kernel.org
Cc: romieu@fr.zoreil.com
Subject: Re: [PATCH] r8169: use RxFIFO overflow workaround for 8168c chipset
Date: Thu, 27 Jan 2011 12:27:30 +0100 [thread overview]
Message-ID: <1296127650.8720.1.camel@ceranb.brq.redhat.com> (raw)
In-Reply-To: <1296127451-12640-1-git-send-email-ivecera@redhat.com>
On Thu, 2011-01-27 at 12:24 +0100, Ivan Vecera wrote:
> I found that one of the 8168c chipsets (concretely XID 1c4000c0) starts
> generating RxFIFO overflow errors. The result is an infinite loop in
> interrupt handler as the RxFIFOOver is handled only for ...MAC_VER_11.
> With the workaround everything goes fine.
...of course starts generating RxFIFO overflow errors under very high
load. :-)
Ivan
next prev parent reply other threads:[~2011-01-27 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 11:24 [PATCH] r8169: use RxFIFO overflow workaround for 8168c chipset Ivan Vecera
2011-01-27 11:27 ` Ivan Vecera [this message]
2011-01-27 14:32 ` Francois Romieu
2011-01-27 19:23 ` Ivan Vecera
[not found] ` <20110128172537.GA11064@electric-eye.fr.zoreil.com>
2011-01-28 17:28 ` Francois Romieu
2011-02-01 10:30 ` Ivan Vecera
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=1296127650.8720.1.camel@ceranb.brq.redhat.com \
--to=ivecera@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
/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