netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zach Sadecki <zach@sadecki.net>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net
Subject: [PATCH] fec driver multicast (and IPv6) problem
Date: Thu, 26 May 2011 08:19:38 -0500	[thread overview]
Message-ID: <4DDE536A.30005@sadecki.net> (raw)

I noticed that sometimes I could not connect to my i.MX28 board over 
IPv6.  After some diagnosis I learned that it was not responding any NDP 
requests.  A simple "ip link set eth0 promisc off" would cause it to 
respond properly to those requests.  While that command didn't really do 
anything (it wasn't in promisc mode to begin with), it did trigger a 
call to set_multicast_list in the fec driver.  It turns out that the 
fec_restart function was zeroing out the multicast group hash registers 
which breaks IPv6 NDP (amongst other things dependent on multicast 
functionality).  Changing the zeroing functionality into a call to 
set_multicast_list fixed this problem for me.  Note that simply removing 
the calls that zero out the registers didn't work, as I believe the 
reset call a few lines above had already cleared them.  A patch is 
inline below.

Zach

diff -ru linux-2.6.39/drivers/net/fec.c 
linux-2.6.39-fecpatch/drivers/net/fec.c
--- linux-2.6.39/drivers/net/fec.c    2011-05-18 23:06:34.000000000 -0500
+++ linux-2.6.39-fecpatch/drivers/net/fec.c    2011-05-25 
15:17:12.294339147 -0500
@@ -361,8 +361,7 @@
      writel(0xffc00000, fep->hwp + FEC_IEVENT);

      /* Reset all multicast.    */
-    writel(0, fep->hwp + FEC_GRP_HASH_TABLE_HIGH);
-    writel(0, fep->hwp + FEC_GRP_HASH_TABLE_LOW);
+    set_multicast_list(dev);
  #ifndef CONFIG_M5272
      writel(0, fep->hwp + FEC_HASH_TABLE_HIGH);
      writel(0, fep->hwp + FEC_HASH_TABLE_LOW);


                 reply	other threads:[~2011-05-26 13:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4DDE536A.30005@sadecki.net \
    --to=zach@sadecki.net \
    --cc=davem@davemloft.net \
    --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;
as well as URLs for NNTP newsgroup(s).