From: Eric Dumazet <eric.dumazet@gmail.com>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: b44: Reset due to FIFO overflow.
Date: Mon, 28 Jun 2010 11:13:14 +0200 [thread overview]
Message-ID: <1277716394.4235.235.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTinwnTw3Yqy3POghliZDRmRYUfJL6Gy67GNNLiYv@mail.gmail.com>
Le lundi 28 juin 2010 à 08:41 +0100, James Courtier-Dutton a écrit :
> Hi,
>
> Reference:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279102
>
> I can see this bug and can reproduce it 100% on demand.
> The problem seems to be that when the b44 has a incoming FIFO buffer
> overflow, it resets the entire card, dis-associates with the access
> point and therefore takes some time before it can pass traffic again.
> Can anyone point me to some code that would just recover the FIFO
> instead of reset the entire card?
>
> I am a kernel developer, but I don't have any data sheets on this card
> so was hoping someone with more knowledge of its workings, could help
> me.
>
> I can then test it, and see if it is a good fix or not.
>
Hi
Problem is we dont know if a Receive Fifo overflow is a minor or major
indication from b44 chip.
A minor indication would be : Chip tells us one or more frame were lost.
No special action needed from driver.
A major indication (as of current implemented in b44 driver) is :
I am completely out of order and need a reset. Please do it.
Patch to switch from major to minor indication is easy, but we dont know
if its valid or not.
diff --git a/drivers/net/b44.h b/drivers/net/b44.h
index e1905a4..514dc3a 100644
--- a/drivers/net/b44.h
+++ b/drivers/net/b44.h
@@ -42,7 +42,7 @@
#define ISTAT_EMAC 0x04000000 /* EMAC Interrupt */
#define ISTAT_MII_WRITE 0x08000000 /* MII Write Interrupt */
#define ISTAT_MII_READ 0x10000000 /* MII Read Interrupt */
-#define ISTAT_ERRORS (ISTAT_DSCE|ISTAT_DATAE|ISTAT_DPE|ISTAT_RDU|ISTAT_RFO|ISTAT_TFU)
+#define ISTAT_ERRORS (ISTAT_DSCE|ISTAT_DATAE|ISTAT_DPE|ISTAT_RDU|ISTAT_TFU)
#define B44_IMASK 0x0024UL /* Interrupt Mask */
#define IMASK_DEF (ISTAT_ERRORS | ISTAT_TO | ISTAT_RX | ISTAT_TX)
#define B44_GPTIMER 0x0028UL /* General Purpose Timer */
next prev parent reply other threads:[~2010-06-28 9:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 7:41 b44: Reset due to FIFO overflow James Courtier-Dutton
2010-06-28 9:13 ` Eric Dumazet [this message]
2010-06-28 9:33 ` Mitchell Erblich
2010-06-28 10:00 ` Eric Dumazet
2010-06-28 10:17 ` James Courtier-Dutton
2010-06-28 11:09 ` Eric Dumazet
2010-06-28 21:21 ` Mitchell Erblich
2010-06-29 5:17 ` Eric Dumazet
2010-06-30 19:35 ` James Courtier-Dutton
2010-06-30 20:22 ` David Miller
2010-06-30 22:20 ` James Courtier-Dutton
2010-06-28 10:24 ` James Courtier-Dutton
2010-06-28 11:11 ` Eric Dumazet
2010-06-28 21:37 ` James Courtier-Dutton
2010-06-29 8:42 ` James Courtier-Dutton
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=1277716394.4235.235.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=james.dutton@gmail.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox