From: Mike Auty <mike.auty@gmail.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 41152] New: kernel 3.0 and above fails to handle vlan id 0 (802.1p) packets properly without hardware acceleration
Date: Wed, 17 Aug 2011 23:48:41 +0100 [thread overview]
Message-ID: <4E4C4549.6020802@gmail.com> (raw)
In-Reply-To: <20110817105950.GA4259@minipsycho.brq.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1356 bytes --]
On 17/08/11 11:59, Jiri Pirko wrote:
>
> I just obtained very similar card (8086:422b). Going to look at it right
> away.
>
> One more thing. What do you use to generate vlan0 tagged packets? I'm
> using pktgen with "vlan_id 0". Would you please try that it behaves the
> same for you?
>
Sorry, I haven't been using pktgen. I've got an actual device (a
Samsung android phone) which seems to tag all normal outbound packets
with this type of vlan tag. I only discovered a month ago that I needed
the 8021q module to be able to talk to it, and then suddenly it stopped
working once I moved to the 3.0 kernel.
I might not have made it clear, but the packets are received (in so much
as the packet is definitely sent, and it's seen by tools such as
wireshark), but no reply is ever sent. I've attached packet logs from
the 3.0.1 kernel and the 2.6.39.3 kernel. Oddly the tagging only seems
to be used on the first SYN,ACK packet, but again I don't know enough
about the pipeline or what the Samsung kernel's doing to cause that.
I hope that's of some help? I may be able to get systemtap support
rolled into my kernel tomorrow at some point, but if not then it will
have to wait until the weekend. I don't know if that will provide
useful information for debugging this, but I am happy to run whatever
tests I can to figure this out...
Mike 5:)
[-- Attachment #2: vlan0-on-kernel-2.6.39.3.pcap --]
[-- Type: application/x-extension-pcap, Size: 687 bytes --]
[-- Attachment #3: vlan0-on-kernel-3.0.1.pcap --]
[-- Type: application/x-extension-pcap, Size: 786 bytes --]
next prev parent reply other threads:[~2011-08-17 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-41152-10286@https.bugzilla.kernel.org/>
2011-08-16 22:09 ` [Bugme-new] [Bug 41152] New: kernel 3.0 and above fails to handle vlan id 0 (802.1p) packets properly without hardware acceleration Andrew Morton
2011-08-17 5:37 ` Jiri Pirko
2011-08-17 6:36 ` Mike Auty
2011-08-17 10:59 ` Jiri Pirko
2011-08-17 17:50 ` Jiri Pirko
2011-08-17 22:48 ` Mike Auty [this message]
2011-08-18 16:37 ` Jiri Pirko
2011-08-18 19:39 ` Mike Auty
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=4E4C4549.6020802@gmail.com \
--to=mike.auty@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jpirko@redhat.com \
--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 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.