From: Jiri Pirko <jpirko@redhat.com>
To: john stultz <johnstul@us.ibm.com>
Cc: walt <w41ter@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [bisected regression] Partial breakage of forcedeth driver
Date: Tue, 26 Jul 2011 08:35:11 +0200 [thread overview]
Message-ID: <20110726063511.GC2073@minipsycho> (raw)
In-Reply-To: <CANcMJZAAfMV2=rTEi7AVg3Qu8uT1kMEpYpTQ+UwvosNPJ81GfA@mail.gmail.com>
Tue, Jul 26, 2011 at 01:23:59AM CEST, johnstul@us.ibm.com wrote:
>On Sun, Jul 24, 2011 at 4:10 PM, walt <w41ter@gmail.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?
Nothing so far. I plan to take a loot at this today. Will keep you guyes
posted.
Jirka
>
>thanks
>-john
next prev parent reply other threads:[~2011-07-26 6:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 23:10 [bisected regression] Partial breakage of forcedeth driver walt
2011-07-25 14:36 ` Jiri Pirko
2011-07-25 23:23 ` john stultz
2011-07-25 23:37 ` Mike Sampson
2011-07-26 6:35 ` Jiri Pirko [this message]
2011-07-26 15:31 ` Jiri Pirko
2011-07-28 13:41 ` Maciej Rutecki
2011-07-28 13:42 ` David Miller
2011-07-28 14:47 ` Maciej Rutecki
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=20110726063511.GC2073@minipsycho \
--to=jpirko@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w41ter@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.