netdev - Fwd: [BUG] Bisected Gianfar not receiving any traffic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 9 Jun 2013 22:28:51 +0200
From:	Michael Guntsche <michael.guntsche@...loops.com>
To:	netdev@...r.kernel.org
Subject: Fwd: [BUG] Bisected Gianfar not receiving any traffic

Forwarded to the correct mailing list address.

---------- Forwarded message ----------
From: Michael Guntsche <michael.guntsche@...loops.com>
Date: Sun, Jun 9, 2013 at 10:26 PM
Subject: [BUG] Bisected Gianfar not receiving any traffic
To: linux-netdev@...r.kernel.org
Cc: Claudiu Manoil <claudiu.manoil@...escale.com>

Good evening,

While testing one of my powerpc based embedded ports I noticed that
with any 3.10-rc kernel ethernet traffic was dead on my two gianfar
NICs. The strange thing was that apparetnly outbound broadcasts seemed
to work since avahi correctly registered the name of the board. I
bisected it to the following commit.

6be5ed3fef568 gianfar: Poll only active Rx queues

Reverting this commit on 3.10-rc4 made both gianfar devices work
again. This is a rather old board so it could be that the register
that's used here is just plain wrong in my case. A few years ago I had
a similar issue where the implementation on the board here apparently
did not work correctly.

http://marc.info/?l=linux-netdev&m=131297524825104&w=2

In that case a flag was bogus as well.
If you need more information or want me to test a patch please add me
as CC since I am not subscribed to the list.

Kind regards,
Michael Guntsche
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html