linux-kernel - Re: [bisected regression] Partial breakage of forcedeth driver

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Jul 2011 16:23:59 -0700
From:	john stultz <johnstul@...ibm.com>
To:	walt <w41ter@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jiri Pirko <jpirko@...hat.com>
Subject: Re: [bisected regression] Partial breakage of forcedeth driver

On Sun, Jul 24, 2011 at 4:10 PM, walt <w41ter@...il.com> wrote:
> commit 3326c784c9f492e988617d93f647ae0cfd4c8d09
> Author: Jiri Pirko <jpirko@>
> Date:   Wed Jul 20 04:54:38 2011 +0000
>
>    forcedeth: do vlan cleanup
>
>    - unify vlan and nonvlan rx path
>    - kill np->vlangrp and nv_vlan_rx_register
>    - allow to turn on/off rx vlan accel via ethtool (set_features)
>
>    Signed-off-by: Jiri Pirko <jpirko@>
>    Signed-off-by: David S. Miller <davem@>
>
> This commit causes networking trouble for my nForce-based motherboard.
> (Details happily supplied if needed.)
>
> I say 'partial' breakage because networking is not completely dead,
> just limping very slowly :)
>
> The simplest test is to ping any host (in my LAN or on the internet,
> makes no difference).  The replies to my ping come at very irregular
> intervals, ranging from normal to 5-10 seconds or so, seemingly at
> random AFAICT.

I'm seeing this too.  Ping responses phase in and out every 10 seconds or so.

Jiri, any thoughts?

thanks
-john
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/