netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: David <david@unsolicited.net>
Cc: netdev@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Sky2 - problems with VLANs - kernel 2.6.36
Date: Fri, 31 Dec 2010 10:13:03 -0800	[thread overview]
Message-ID: <20101231101303.6caed8ab@s6510> (raw)
In-Reply-To: <4CD48DE6.7060906@unsolicited.net>

On Fri, 05 Nov 2010 23:06:14 +0000
David <david@unsolicited.net> wrote:

> I've just installed a Lycom dual port gigabit ethernet card, picked up
> as follows :-
> 
> 03:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8062 PCI-E
> IPMI Gigabit Ethernet Controller (rev 14)
>     Subsystem: Marvell Technology Group Ltd. Device 6222
>     Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
>     Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
>     Latency: 0, Cache Line Size: 64 bytes
>     Interrupt: pin A routed to IRQ 41
>     Region 0: Memory at fe8fc000 (64-bit, non-prefetchable) [size=16K]
>     Region 2: I/O ports at c800 [size=256]
>     Expansion ROM at fe8c0000 [disabled] [size=128K]
>     Capabilities: <access denied>
>     Kernel driver in use: sky2
>     Kernel modules: sky2
> 
> I'm having a problem with VLANs. Outgoing packets are tagged correctly
> and devices on the VLAN are responding. Unfortunately all of the
> response packets stay on the raw device and are not allocated to the VLAN.
> 
> I've done some investigation (printks etc.), and have found that neither
> of the following cases in sky2_status_intr() are being triggered...
> 
>                 case OP_RXVLAN:
>                         printk("RXVLAN, length=%u, status=%u\n", length,
> status);
>                         sky2->rx_tag = length;
>                         break;
> 
>                 case OP_RXCHKSVLAN:
>                         printk("RXCHKSVLAN, length=%u, status=%u\n",
> length, status);
>                         sky2->rx_tag = length;
>                         /* fall through */
> 
> ... however the status when calling sky2_skb_rx() does have GMR_FS_VLAN
> set, it's just we haven't been able to find out which VLAN the packet
> comes from (and sky2->rx_tag is zero). Does anyone have any suggestions
> as to how I proceed from here? I'm happy to test patches etc.

Did it work with older kernels? 

  reply	other threads:[~2010-12-31 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 23:06 Sky2 - problems with VLANs - kernel 2.6.36 David
2010-12-31 18:13 ` Stephen Hemminger [this message]
2010-12-31 21:42   ` David

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=20101231101303.6caed8ab@s6510 \
    --to=shemminger@vyatta.com \
    --cc=david@unsolicited.net \
    --cc=linux-kernel@vger.kernel.org \
    --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 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).