From: Ingo Molnar <mingo@elte.hu>
To: Jiri Pirko <jpirko@redhat.com>
Cc: David Miller <davem@davemloft.net>,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [forcedeth bug] Re: [GIT] Networking
Date: Fri, 5 Aug 2011 12:29:03 +0200 [thread overview]
Message-ID: <20110805102903.GF2420@elte.hu> (raw)
In-Reply-To: <20110805102239.GB1928@minipsycho.orion>
* Jiri Pirko <jpirko@redhat.com> wrote:
> Thu, Aug 04, 2011 at 11:53:54PM CEST, mingo@elte.hu wrote:
> >
> >* Ingo Molnar <mingo@elte.hu> wrote:
> >
> >> 0891b0e08937: forcedeth: fix vlans
> >
> >Hm, forcedeth is still giving me trouble even on latest -git that has
> >the above fix included.
> >
> >The symptom is a stuck interface, no packets in. There's a frame
> >error RX packet:
> >
> > [root@mercury ~]# ifconfig eth0
> > eth0 Link encap:Ethernet HWaddr 00:13:D4:DC:41:12
> > inet addr:10.0.1.13 Bcast:10.0.1.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:1 dropped:0 overruns:0 frame:1
> > TX packets:531 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:1000
> > RX bytes:0 (0.0 b) TX bytes:34112 (33.3 KiB)
> > Interrupt:35
> >
> >Weirdly enough a defconfig x86 bootup works just fine - it's certain
> >.config combinations that trigger the bug. I've attached such a
> >config.
> >
> >Note that at least once i've observed a seemingly good kernel going
> >'bad' after a couple of minutes uptime. I've also observed
> >intermittent behavior - apparent lost packets and a laggy network.
> >
> >I have done 3 failed attempts to bisect it any further - i got to the
> >commit that got fixed by:
> >
> > 0891b0e08937: forcedeth: fix vlans
> >
> >... but that's something we already knew.
> >
> >Let me know if there's any data i can provide to help debug this
> >problem.
> >
> >Thanks,
> >
> > Ingo
>
> Interesting.
>
> Is DEV_HAS_VLAN set in id->driver_data (L5344) ?
How do i tell that without hacking the driver?
> If so, would you try to disable both rx an tx vlan accel using
> ethtool and see if it helps?
Should i do that when the device is in a stuck state and see whether
it recovers?
Also, please provide the exact ethtool command sequences i should
try, this makes it easier for me to test exactly what you want me to
test.
Thanks,
Ingo
next prev parent reply other threads:[~2011-08-05 10:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 14:33 [GIT] Networking David Miller
2011-08-01 15:13 ` Ingo Molnar
2011-08-04 21:53 ` [forcedeth bug] " Ingo Molnar
2011-08-05 10:16 ` [PATCH, REVERT] " Ingo Molnar
2011-08-05 10:19 ` David Miller
2011-08-05 10:26 ` Jiri Pirko
2011-08-05 10:22 ` Jiri Pirko
2011-08-05 10:29 ` Ingo Molnar [this message]
2011-08-05 11:12 ` Neil Horman
2011-08-05 11:44 ` Jiri Pirko
2011-08-05 11:25 ` Jiri Pirko
2011-08-05 12:18 ` Ingo Molnar
2011-08-05 12:31 ` Jiri Pirko
2011-08-05 14:37 ` Jiri Pirko
2011-08-09 13:13 ` Jiri Pirko
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=20110805102903.GF2420@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jpirko@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).