* Realtek r8168C / r8169 driver VLAN TAG stripping
@ 2011-01-13 14:40 Anand Raj Manickam
2011-01-13 15:09 ` Anand Raj Manickam
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-13 14:40 UTC (permalink / raw)
To: netdev
Hi ,
I have a problem on Realtek 8168C chipset - r8169 Driver .
The VLAN tag on Tx & Rx gets stripped .
The 8021q module is loaded .
vconfig add eth0 50
ifconfig eth0.50 172.16.1.10 up
ping -I eth0.50 172.16.1.1 .
All packets on Tx & Rx have the VLAN tag stripped on Tx & Rx.
On debugging the Driver , we found that on Tx the VLAN tag is present.
static int rtl8169_start_xmit(struct sk_buff *skb, struct net_device *dev)
{
.
.
tp->tx_skb[entry].len = len;
txd->addr = cpu_to_le64(mapping);
txd->opts2 = cpu_to_le32(rtl8169_tx_vlan_tag(tp, skb));
printk("The Vlan tag %x \n",txd->opts2);
.
.
}
The Vlan tag 23200
In the above value 23200
2 - TxVlanTag
32 - Vlan tag (50).
>From the above we are clear that the Vlan tag reaches the driver .
Can someone shed some light on this issue ?
Any pointer are welcome.
Thanks,
Anand
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-13 14:40 Realtek r8168C / r8169 driver VLAN TAG stripping Anand Raj Manickam
@ 2011-01-13 15:09 ` Anand Raj Manickam
2011-01-16 19:20 ` Francois Romieu
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-13 15:09 UTC (permalink / raw)
To: netdev
Sorry,
This happens on a Linux 2.6.30.8 kernel .The driver is in-kernel.
On Thu, Jan 13, 2011 at 8:10 PM, Anand Raj Manickam <anandrm@gmail.com> wrote:
> Hi ,
> I have a problem on Realtek 8168C chipset - r8169 Driver .
> The VLAN tag on Tx & Rx gets stripped .
>
> The 8021q module is loaded .
> vconfig add eth0 50
> ifconfig eth0.50 172.16.1.10 up
>
> ping -I eth0.50 172.16.1.1 .
>
> All packets on Tx & Rx have the VLAN tag stripped on Tx & Rx.
>
> On debugging the Driver , we found that on Tx the VLAN tag is present.
>
> static int rtl8169_start_xmit(struct sk_buff *skb, struct net_device *dev)
> {
> .
> .
> tp->tx_skb[entry].len = len;
> txd->addr = cpu_to_le64(mapping);
> txd->opts2 = cpu_to_le32(rtl8169_tx_vlan_tag(tp, skb));
> printk("The Vlan tag %x \n",txd->opts2);
> .
> .
> }
>
> The Vlan tag 23200
>
> In the above value 23200
> 2 - TxVlanTag
> 32 - Vlan tag (50).
>
> From the above we are clear that the Vlan tag reaches the driver .
>
> Can someone shed some light on this issue ?
> Any pointers are welcome.
> Thanks,
> Anand
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-13 15:09 ` Anand Raj Manickam
@ 2011-01-16 19:20 ` Francois Romieu
[not found] ` <AANLkTi=uNKMj_gs_bKRQ1tQa0TMwdnyrtVcR5JPNpmJv@mail.gmail.com>
0 siblings, 1 reply; 17+ messages in thread
From: Francois Romieu @ 2011-01-16 19:20 UTC (permalink / raw)
To: Anand Raj Manickam; +Cc: netdev
Anand Raj Manickam <anandrm@gmail.com> :
[...]
> This happens on a Linux 2.6.30.8 kernel .The driver is in-kernel.
I do not notice it with my 8168c (XID 18000000) on a modular 2.6.37-git.
Can you send the XID of the r8169 that appears in the log of your kernel
and upgrade to a more recent kernel ?
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
[not found] ` <AANLkTi=uNKMj_gs_bKRQ1tQa0TMwdnyrtVcR5JPNpmJv@mail.gmail.com>
@ 2011-01-17 7:34 ` Anand Raj Manickam
2011-01-18 1:21 ` Francois Romieu
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-17 7:34 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev
On Mon, Jan 17, 2011 at 11:52 AM, Anand Raj Manickam <anandrm@gmail.com> wrote:
> Hi Romieu ,
> This is the dmesg for XID
>
> eth0: RTL8168c/8111c at 0xf9628000, 00:17:54:00:f6:62, XID 1c4000c0 IRQ 31
> r8169: mac_version = 0x16
> r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
>
> Unfortunately , i m not able to upgrade my kernel now . If there is a
> Fix for it , that would be great !!
>
> Thanks for your kind reply ,
> Anand
>
>
>
> On Mon, Jan 17, 2011 at 12:50 AM, Francois Romieu <romieu@fr.zoreil.com> wrote:
>> Anand Raj Manickam <anandrm@gmail.com> :
>> [...]
>>> This happens on a Linux 2.6.30.8 kernel .The driver is in-kernel.
>>
>> I do not notice it with my 8168c (XID 18000000) on a modular 2.6.37-git.
>>
>> Can you send the XID of the r8169 that appears in the log of your kernel
>> and upgrade to a more recent kernel ?
>>
>> --
>> Ueimor
>>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-17 7:34 ` Anand Raj Manickam
@ 2011-01-18 1:21 ` Francois Romieu
2011-01-27 10:35 ` Anand Raj Manickam
0 siblings, 1 reply; 17+ messages in thread
From: Francois Romieu @ 2011-01-18 1:21 UTC (permalink / raw)
To: Anand Raj Manickam; +Cc: netdev, Hayes
Anand Raj Manickam <anandrm@gmail.com> :
> On Mon, Jan 17, 2011 at 11:52 AM, Anand Raj Manickam <anandrm@gmail.com> wrote:
[...]
> > This is the dmesg for XID
> >
> > eth0: RTL8168c/8111c at 0xf9628000, 00:17:54:00:f6:62, XID 1c4000c0 IRQ 31
> > r8169: mac_version = 0x16
I do not have one of those (RTL_GIGA_MAC_VER_22) to check if it handles vlan
correctly yet.
> > r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
> >
> > Unfortunately , i m not able to upgrade my kernel now . If there is a
> > Fix for it , that would be great !!
I doubt there is a lot of glamour/fortune/fame in backporting the 89 r8169
patches between v2.6.30 and v2.6.37 but you may help yourself and give it
a try.
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-18 1:21 ` Francois Romieu
@ 2011-01-27 10:35 ` Anand Raj Manickam
2011-01-27 15:07 ` Francois Romieu
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-27 10:35 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev, Hayes
Hi ,
We upgraded to 2.6.36 kernel . The result is SAME.
The VLAN tag gets stripped ;-)
Do let me know if you need more info .
Thanks,
Anand
On Tue, Jan 18, 2011 at 6:51 AM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Anand Raj Manickam <anandrm@gmail.com> :
>> On Mon, Jan 17, 2011 at 11:52 AM, Anand Raj Manickam <anandrm@gmail.com> wrote:
> [...]
>> > This is the dmesg for XID
>> >
>> > eth0: RTL8168c/8111c at 0xf9628000, 00:17:54:00:f6:62, XID 1c4000c0 IRQ 31
>> > r8169: mac_version = 0x16
>
> I do not have one of those (RTL_GIGA_MAC_VER_22) to check if it handles vlan
> correctly yet.
>
>> > r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
>> >
>> > Unfortunately , i m not able to upgrade my kernel now . If there is a
>> > Fix for it , that would be great !!
>
> I doubt there is a lot of glamour/fortune/fame in backporting the 89 r8169
> patches between v2.6.30 and v2.6.37 but you may help yourself and give it
> a try.
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-27 10:35 ` Anand Raj Manickam
@ 2011-01-27 15:07 ` Francois Romieu
2011-01-27 15:31 ` Anand Raj Manickam
0 siblings, 1 reply; 17+ messages in thread
From: Francois Romieu @ 2011-01-27 15:07 UTC (permalink / raw)
To: Anand Raj Manickam; +Cc: netdev, Hayes
Anand Raj Manickam <anandrm@gmail.com> :
[...]
> We upgraded to 2.6.36 kernel . The result is SAME.
> The VLAN tag gets stripped ;-)
> Do let me know if you need more info .
- ip addr show
- ethtool -k eth0
I do not get the "VLAN tag gets stripped" concept, especially on Tx.
Does it mean "no packet" or "a packet whose content is wrong" ?
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-27 15:07 ` Francois Romieu
@ 2011-01-27 15:31 ` Anand Raj Manickam
2011-01-27 16:50 ` Francois Romieu
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-27 15:31 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev, Hayes
On Thu, Jan 27, 2011 at 8:37 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Anand Raj Manickam <anandrm@gmail.com> :
> [...]
>> We upgraded to 2.6.36 kernel . The result is SAME.
>> The VLAN tag gets stripped ;-)
>> Do let me know if you need more info .
>
> - ip addr show
3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
inet 172.16.1.1/16 brd 172.16.255.255 scope global eth0
inet6 fe80::217:54ff:fe00:f662/64 scope link
valid_lft forever preferred_lft forever
8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
inet6 fe80::217:54ff:fe00:f662/64 scope link
valid_lft forever preferred_lft forever
> - ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: off
scatter-gather: off
tcp segmentation offload: off
udp fragmentation offload: off
generic segmentation offload: off
> I do not get the "VLAN tag gets stripped" concept, especially on Tx.
> Does it mean "no packet" or "a packet whose content is wrong" ?
Sorry for not being clear ;-)
When we transmit a packet with VLAN TAG , the TAG get stripped when
transmitted through the device , the other end trunk port / sniffer
does NOT see a TAG.
Similarly , when a VLAN Tagged packet is sent from the other end , The
TAG gets stripped by the device , We DONOT see the tag .
I use tcpdump -i eth0 -n -nn -e vlan 50
to see if the packets are gettin tagged or NOT .
The same config works on forcedeth
Thanks,
Anand
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-27 15:31 ` Anand Raj Manickam
@ 2011-01-27 16:50 ` Francois Romieu
2011-01-28 1:40 ` Anand Raj Manickam
0 siblings, 1 reply; 17+ messages in thread
From: Francois Romieu @ 2011-01-27 16:50 UTC (permalink / raw)
To: Anand Raj Manickam; +Cc: netdev, Hayes
Anand Raj Manickam <anandrm@gmail.com> :
> On Thu, Jan 27, 2011 at 8:37 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> > Anand Raj Manickam <anandrm@gmail.com> :
[...]
> > - ip addr show
>
> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> inet 172.16.1.1/16 brd 172.16.255.255 scope global eth0
> inet6 fe80::217:54ff:fe00:f662/64 scope link
> valid_lft forever preferred_lft forever
>
> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
> inet6 fe80::217:54ff:fe00:f662/64 scope link
> valid_lft forever preferred_lft forever
Could you try again after issuing :
ip addr del 172.16.1.1/16 brd 172.16.255.255 dev eth0
then send the unabbreviated "ip addr show" and "ip route show all" if
things do not perform better.
(no iptables / ip rules wizardry, right ?)
[...]
> > - ethtool -k eth0
>
> Offload parameters for eth0:
> rx-checksumming: on
> tx-checksumming: off
> scatter-gather: off
> tcp segmentation offload: off
> udp fragmentation offload: off
> generic segmentation offload: off
Ok.
[...]
> > I do not get the "VLAN tag gets stripped" concept, especially on Tx.
> > Does it mean "no packet" or "a packet whose content is wrong" ?
>
> Sorry for not being clear ;-)
>
> When we transmit a packet with VLAN TAG , the TAG get stripped when
> transmitted through the device , the other end trunk port / sniffer
> does NOT see a TAG.
> Similarly , when a VLAN Tagged packet is sent from the other end , The
> TAG gets stripped by the device , We DONOT see the tag .
But the data flows in both directions, right ?
> I use tcpdump -i eth0 -n -nn -e vlan 50
> to see if the packets are gettin tagged or NOT .
>
> The same config works on forcedeth
What do you call "same config" ?
I am mildly convinced that your config is simple enough to isolate a
driver level vlan problem.
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-27 16:50 ` Francois Romieu
@ 2011-01-28 1:40 ` Anand Raj Manickam
2011-01-28 12:06 ` Francois Romieu
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-28 1:40 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev, Hayes
On Thu, Jan 27, 2011 at 10:20 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Anand Raj Manickam <anandrm@gmail.com> :
>> On Thu, Jan 27, 2011 at 8:37 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
>> > Anand Raj Manickam <anandrm@gmail.com> :
> [...]
>> > - ip addr show
>>
>> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> inet 172.16.1.1/16 brd 172.16.255.255 scope global eth0
>> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> valid_lft forever preferred_lft forever
>>
>> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
>> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> valid_lft forever preferred_lft forever
>
> Could you try again after issuing :
>
> ip addr del 172.16.1.1/16 brd 172.16.255.255 dev eth0
I did try this NO luck ;-(
>
> then send the unabbreviated "ip addr show" and "ip route show all" if
> things do not perform better.
>
ip addr show
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0: <NOARP> mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
inet6 fe80::217:54ff:fe00:f662/64 scope link
valid_lft forever preferred_lft forever
4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:54:00:f6:63 brd ff:ff:ff:ff:ff:ff
5: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:30:67:09:2c:b9 brd ff:ff:ff:ff:ff:ff
inet 10.1.1.2/24 brd 10.1.1.255 scope global eth2
inet6 fe80::230:67ff:fe09:2cb9/64 scope link
valid_lft forever preferred_lft forever
6: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:17:54:00:65:6b brd ff:ff:ff:ff:ff:ff
7: eth4: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:54:00:65:6a brd ff:ff:ff:ff:ff:ff
inet 192.168.138.155/24 brd 192.168.138.255 scope global eth4
inet6 fe80::217:54ff:fe00:656a/64 scope link
valid_lft forever preferred_lft forever
8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
inet6 fe80::217:54ff:fe00:f662/64 scope link
valid_lft forever preferred_lft forever
> (no iptables / ip rules wizardry, right ?)
>
> [...]
>> > - ethtool -k eth0
>>
>> Offload parameters for eth0:
>> rx-checksumming: on
>> tx-checksumming: off
>> scatter-gather: off
>> tcp segmentation offload: off
>> udp fragmentation offload: off
>> generic segmentation offload: off
>
> Ok.
>
> [...]
>> > I do not get the "VLAN tag gets stripped" concept, especially on Tx.
>> > Does it mean "no packet" or "a packet whose content is wrong" ?
>>
>> Sorry for not being clear ;-)
>>
>> When we transmit a packet with VLAN TAG , the TAG get stripped when
>> transmitted through the device , the other end trunk port / sniffer
>> does NOT see a TAG.
>> Similarly , when a VLAN Tagged packet is sent from the other end , The
>> TAG gets stripped by the device , We DONOT see the tag .
>
> But the data flows in both directions, right ?
>
>> I use tcpdump -i eth0 -n -nn -e vlan 50
>> to see if the packets are gettin tagged or NOT .
>>
>> The same config works on forcedeth
>
> What do you call "same config" ?
The Same setup below works on forcedeth driver
>
> I am mildly convinced that your config is simple enough to isolate a
> driver level vlan problem.
The reason why i m sure its on the Driver / Chipset is this ..
The 8021q module is loaded .
vconfig add eth0 50
ifconfig eth0.50 172.16.1.10 up
ping -I eth0.50 172.16.1.1 .
All packets on Tx & Rx have the VLAN tag stripped on Tx & Rx.
On debugging the Driver , we found that on Tx the VLAN tag is present.
static int rtl8169_start_xmit(struct sk_buff *skb, struct net_device *dev)
{
.
.
tp->tx_skb[entry].len = len;
txd->addr = cpu_to_le64(mapping);
txd->opts2 = cpu_to_le32(rtl8169_tx_vlan_tag(tp, skb));
printk("The Vlan tag %x \n",txd->opts2);
.
.
}
The Vlan tag 23200
In the above value 23200
2 - TxVlanTag
32 - Vlan tag (50).
From the above we are clear that the Vlan tag reaches the driver .
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-28 1:40 ` Anand Raj Manickam
@ 2011-01-28 12:06 ` Francois Romieu
2011-01-28 12:16 ` Anand Raj Manickam
` (2 more replies)
0 siblings, 3 replies; 17+ messages in thread
From: Francois Romieu @ 2011-01-28 12:06 UTC (permalink / raw)
To: Anand Raj Manickam; +Cc: netdev, Hayes, Ivan Vecera
Added Ivan to the Cc:. He has got a 8168c with XID 1c4000c0 and may tell if
hardware VLAN works for him or not.
Anand Raj Manickam <anandrm@gmail.com> :
> On Thu, Jan 27, 2011 at 10:20 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> > Anand Raj Manickam <anandrm@gmail.com> :
> >> On Thu, Jan 27, 2011 at 8:37 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> >> > Anand Raj Manickam <anandrm@gmail.com> :
> > [...]
> >> > - ip addr show
> >>
> >> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> >> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> >> inet 172.16.1.1/16 brd 172.16.255.255 scope global eth0
> >> inet6 fe80::217:54ff:fe00:f662/64 scope link
> >> valid_lft forever preferred_lft forever
> >>
> >> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
> >> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> >> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
> >> inet6 fe80::217:54ff:fe00:f662/64 scope link
> >> valid_lft forever preferred_lft forever
> >
> > Could you try again after issuing :
> >
> > ip addr del 172.16.1.1/16 brd 172.16.255.255 dev eth0
>
>
> I did try this NO luck ;-(
>
> > then send the unabbreviated "ip addr show" and "ip route show all" if
> > things do not perform better.
> >
>
> ip addr show
> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: sit0: <NOARP> mtu 1480 qdisc noop
> link/sit 0.0.0.0 brd 0.0.0.0
> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> inet6 fe80::217:54ff:fe00:f662/64 scope link
> valid_lft forever preferred_lft forever
> 4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:17:54:00:f6:63 brd ff:ff:ff:ff:ff:ff
> 5: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:30:67:09:2c:b9 brd ff:ff:ff:ff:ff:ff
> inet 10.1.1.2/24 brd 10.1.1.255 scope global eth2
> inet6 fe80::230:67ff:fe09:2cb9/64 scope link
> valid_lft forever preferred_lft forever
> 6: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
> link/ether 00:17:54:00:65:6b brd ff:ff:ff:ff:ff:ff
> 7: eth4: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
> link/ether 00:17:54:00:65:6a brd ff:ff:ff:ff:ff:ff
> inet 192.168.138.155/24 brd 192.168.138.255 scope global eth4
> inet6 fe80::217:54ff:fe00:656a/64 scope link
> valid_lft forever preferred_lft forever
> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
> inet6 fe80::217:54ff:fe00:f662/64 scope link
> valid_lft forever preferred_lft forever
(mostly sequential hardware mac adresses)
Which Arkino product is it ? Quad (+1) port switch / hub ? AK1140 ?
Forget the "ip route show all" for now.
[...]
> >> The same config works on forcedeth
> >
> > What do you call "same config" ?
>
> The Same setup below works on forcedeth driver
So you can remove any single 8168 adapter from eth[0134], replace it with
an external (non-LOM) forcedeth, keep the three remaining 8168s and it
works correctly ?
If your setup includes a card that contains several 8168 chipsets behind
some kind of bridge, it is not exactly the same setup as a single (LOM ?)
forcedeth network adapter.
[...]
> >
> > I am mildly convinced that your config is simple enough to isolate a
> > driver level vlan problem.
>
> The reason why i m sure its on the Driver / Chipset is this ..
[printk removed]
Ok. This is an evidence.
Reading my rev1.0 8168c datasheet from may 2007, when there is no tx
offload, no checksumming, the tx descriptor layout should be the same
as the perennial 8169 tx descriptor layout.
Either (1) the VLAN registers and descriptor layout is different for this
chipset or (2) something prevents the register / descriptor write (read ?)
to be completely effective or (3) there is something beyond the 8168 or
(4) there is a 8168 hardware bug.
1 : Hayes may answer. You can give Realtek's own driver a try btw.
2 : Seen before. It could be a software or a (non-8168) hardware one.
I have no idea if your hardware setup includes a single card with
four ports or four independent cards with their own 8168 or worse.
3 : See the hardware setup part of (2).
4 : I don't hope so. Hayes may answer as well.
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-28 12:06 ` Francois Romieu
@ 2011-01-28 12:16 ` Anand Raj Manickam
2011-01-31 5:45 ` hayeswang
2011-01-31 13:14 ` Ivan Vecera
2 siblings, 0 replies; 17+ messages in thread
From: Anand Raj Manickam @ 2011-01-28 12:16 UTC (permalink / raw)
To: Francois Romieu; +Cc: netdev, Hayes, Ivan Vecera
On Fri, Jan 28, 2011 at 5:36 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Added Ivan to the Cc:. He has got a 8168c with XID 1c4000c0 and may tell if
> hardware VLAN works for him or not.
Keeping my fingers crossed for Ivan's results :)
> Anand Raj Manickam <anandrm@gmail.com> :
>> On Thu, Jan 27, 2011 at 10:20 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
>> > Anand Raj Manickam <anandrm@gmail.com> :
>> >> On Thu, Jan 27, 2011 at 8:37 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
>> >> > Anand Raj Manickam <anandrm@gmail.com> :
>> > [...]
>> >> > - ip addr show
>> >>
>> >> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>> >> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> >> inet 172.16.1.1/16 brd 172.16.255.255 scope global eth0
>> >> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> >> valid_lft forever preferred_lft forever
>> >>
>> >> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>> >> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> >> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
>> >> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> >> valid_lft forever preferred_lft forever
>> >
>> > Could you try again after issuing :
>> >
>> > ip addr del 172.16.1.1/16 brd 172.16.255.255 dev eth0
>>
>>
>> I did try this NO luck ;-(
>>
>> > then send the unabbreviated "ip addr show" and "ip route show all" if
>> > things do not perform better.
>> >
>>
>> ip addr show
>> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>> inet 127.0.0.1/8 scope host lo
>> inet6 ::1/128 scope host
>> valid_lft forever preferred_lft forever
>> 2: sit0: <NOARP> mtu 1480 qdisc noop
>> link/sit 0.0.0.0 brd 0.0.0.0
>> 3: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> valid_lft forever preferred_lft forever
>> 4: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
>> link/ether 00:17:54:00:f6:63 brd ff:ff:ff:ff:ff:ff
>> 5: eth2: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>> link/ether 00:30:67:09:2c:b9 brd ff:ff:ff:ff:ff:ff
>> inet 10.1.1.2/24 brd 10.1.1.255 scope global eth2
>> inet6 fe80::230:67ff:fe09:2cb9/64 scope link
>> valid_lft forever preferred_lft forever
>> 6: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>> link/ether 00:17:54:00:65:6b brd ff:ff:ff:ff:ff:ff
>> 7: eth4: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>> link/ether 00:17:54:00:65:6a brd ff:ff:ff:ff:ff:ff
>> inet 192.168.138.155/24 brd 192.168.138.255 scope global eth4
>> inet6 fe80::217:54ff:fe00:656a/64 scope link
>> valid_lft forever preferred_lft forever
>> 8: eth0.50@eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue
>> link/ether 00:17:54:00:f6:62 brd ff:ff:ff:ff:ff:ff
>> inet 172.16.10.10/24 brd 172.16.10.255 scope global eth0.50
>> inet6 fe80::217:54ff:fe00:f662/64 scope link
>> valid_lft forever preferred_lft forever
>
> (mostly sequential hardware mac adresses)
>
> Which Arkino product is it ? Quad (+1) port switch / hub ? AK1140 ?
>
> Forget the "ip route show all" for now.
>
> [...]
>> >> The same config works on forcedeth
>> >
>> > What do you call "same config" ?
>>
>> The Same setup below works on forcedeth driver
>
> So you can remove any single 8168 adapter from eth[0134], replace it with
> an external (non-LOM) forcedeth, keep the three remaining 8168s and it
> works correctly ?
>
> If your setup includes a card that contains several 8168 chipsets behind
> some kind of bridge, it is not exactly the same setup as a single (LOM ?)
> forcedeth network adapter.
It is Onboard chipset , so cannot be replaced :-(
>
> [...]
>> >
>> > I am mildly convinced that your config is simple enough to isolate a
>> > driver level vlan problem.
>>
>> The reason why i m sure its on the Driver / Chipset is this ..
> [printk removed]
>
> Ok. This is an evidence.
>
> Reading my rev1.0 8168c datasheet from may 2007, when there is no tx
> offload, no checksumming, the tx descriptor layout should be the same
> as the perennial 8169 tx descriptor layout.
>
> Either (1) the VLAN registers and descriptor layout is different for this
> chipset or (2) something prevents the register / descriptor write (read ?)
> to be completely effective or (3) there is something beyond the 8168 or
> (4) there is a 8168 hardware bug.
>
> 1 : Hayes may answer. You can give Realtek's own driver a try btw.
> 2 : Seen before. It could be a software or a (non-8168) hardware one.
> I have no idea if your hardware setup includes a single card with
> four ports or four independent cards with their own 8168 or worse.
> 3 : See the hardware setup part of (2).
> 4 : I don't hope so. Hayes may answer as well.
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-28 12:06 ` Francois Romieu
2011-01-28 12:16 ` Anand Raj Manickam
@ 2011-01-31 5:45 ` hayeswang
2011-01-31 13:14 ` Ivan Vecera
2 siblings, 0 replies; 17+ messages in thread
From: hayeswang @ 2011-01-31 5:45 UTC (permalink / raw)
To: 'Francois Romieu', 'Anand Raj Manickam'
Cc: netdev, 'Ivan Vecera'
> Reading my rev1.0 8168c datasheet from may 2007, when there
> is no tx offload, no checksumming, the tx descriptor layout
> should be the same as the perennial 8169 tx descriptor layout.
>
> Either (1) the VLAN registers and descriptor layout is
> different for this chipset or (2) something prevents the
> register / descriptor write (read ?) to be completely
> effective or (3) there is something beyond the 8168 or
> (4) there is a 8168 hardware bug.
>
> 1 : Hayes may answer. You can give Realtek's own driver a try btw.
> 2 : Seen before. It could be a software or a (non-8168) hardware one.
> I have no idea if your hardware setup includes a single card with
> four ports or four independent cards with their own 8168 or worse.
> 3 : See the hardware setup part of (2).
> 4 : I don't hope so. Hayes may answer as well.
>
I find nothing wrong for the source code of kernel. I think it should work. Only
the tx descriptor need to be set for the tx. For the receiving, the register
0xe0 (CPlusCmd) bit 6 (RxVlan) should be set. That is all. And I don't get any
information about hardware bug, so I really don't know what's wrong. I will
check it after the vacation of Chinese New Year.
Best Regards,
Hayes
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-28 12:06 ` Francois Romieu
2011-01-28 12:16 ` Anand Raj Manickam
2011-01-31 5:45 ` hayeswang
@ 2011-01-31 13:14 ` Ivan Vecera
2011-02-01 10:12 ` Francois Romieu
2 siblings, 1 reply; 17+ messages in thread
From: Ivan Vecera @ 2011-01-31 13:14 UTC (permalink / raw)
To: Francois Romieu; +Cc: Anand Raj Manickam, netdev, Hayes
On Fri, 2011-01-28 at 13:06 +0100, Francois Romieu wrote:
> Added Ivan to the Cc:. He has got a 8168c with XID 1c4000c0 and may
> tell if
> hardware VLAN works for him or not.
>
Unfortunately I have no local access (it's placed in China) or remote
serial console to the system with this 8168c. The second problem is that
the system is connected to the switch that does not pass the packets
with VLAN tags -> it seems that at least Tx packets have the VLAN tag.
I'm sorry I'm not able to help more.
Ivan
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-01-31 13:14 ` Ivan Vecera
@ 2011-02-01 10:12 ` Francois Romieu
2011-02-01 10:38 ` Anand Raj Manickam
0 siblings, 1 reply; 17+ messages in thread
From: Francois Romieu @ 2011-02-01 10:12 UTC (permalink / raw)
To: Ivan Vecera; +Cc: Anand Raj Manickam, netdev, Hayes
Ivan Vecera <ivecera@redhat.com> :
[...]
> Unfortunately I have no local access (it's placed in China) or remote
> serial console to the system with this 8168c. The second problem is that
> the system is connected to the switch that does not pass the packets
> with VLAN tags -> it seems that at least Tx packets have the VLAN tag.
>
> I'm sorry I'm not able to help more.
Thanks a lot for the information, it is both welcome and helpful.
I'll freeze Anand's report for now as "8168c + unspecified glue hardware
bug with unknown product manufactured by Arkino on unidentified motherboard
with unknown number of processors".
--
Ueimor
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-02-01 10:12 ` Francois Romieu
@ 2011-02-01 10:38 ` Anand Raj Manickam
2011-02-09 9:51 ` hayeswang
0 siblings, 1 reply; 17+ messages in thread
From: Anand Raj Manickam @ 2011-02-01 10:38 UTC (permalink / raw)
To: Francois Romieu; +Cc: Ivan Vecera, netdev, Hayes
On Tue, Feb 1, 2011 at 3:42 PM, Francois Romieu <romieu@fr.zoreil.com> wrote:
> Ivan Vecera <ivecera@redhat.com> :
> [...]
>> Unfortunately I have no local access (it's placed in China) or remote
>> serial console to the system with this 8168c. The second problem is that
>> the system is connected to the switch that does not pass the packets
>> with VLAN tags -> it seems that at least Tx packets have the VLAN tag.
>>
>> I'm sorry I'm not able to help more.
>
> Thanks a lot for the information, it is both welcome and helpful.
>
> I'll freeze Anand's report for now as "8168c + unspecified glue hardware
> bug with unknown product manufactured by Arkino on unidentified motherboard
> with unknown number of processors".
cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 16
model : 6
model name : AMD Sempron(tm) 140 Processor
stepping : 2
cpu MHz : 2700.641
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 5
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb
rdtscp lm 3dnowext 3dnow constant_tsc up nonstop_tsc extd_apicid pni
monitor cx16 popcnt lahf_lm svm extapic cr8_legacy abm sse4a
misalignsse 3dnowprefetch osvw ibs skinit wdt npt lbrv svm_lock
nrip_save
bogomips : 5401.28
clflush size : 64
cache_alignment : 64
address sizes : 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate
>
> --
> Ueimor
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* RE: Realtek r8168C / r8169 driver VLAN TAG stripping
2011-02-01 10:38 ` Anand Raj Manickam
@ 2011-02-09 9:51 ` hayeswang
0 siblings, 0 replies; 17+ messages in thread
From: hayeswang @ 2011-02-09 9:51 UTC (permalink / raw)
To: 'Anand Raj Manickam', 'Francois Romieu'
Cc: 'Ivan Vecera', netdev
I have tested 8168C with RTL_GIGA_MAC_VER_22 . It seems fine with VLAN. My
platform is using Fedora 14. I connect my linux platform with windows one
directly because I don't have a switch supporting VLAN. I set VLAN both windows
side and Linux side and it works well. For the windows side, I use 8111D.
$ uname -a
Linux fc14.localdomain 2.6.35.10-74.fc14.i686 #1 SMP Thu Dec 23 16:17:40 UTC
2010 i686 i686 i386 GNU/Linux
$ ethtool -i eth4
driver: r8169
version: 2.3LK-NAPI
firmware-version:
bus-info: 0000:04:00.0
$ ifconfig eth4.10
eth4.10 Link encap:Ethernet HWaddr 00:E0:4C:68:00:1B
inet addr:192.168.123.112 Bcast:192.168.123.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fe68:1b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6060686 errors:0 dropped:0 overruns:0 frame:0
TX packets:7154774 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:162285185 (154.7 MiB) TX bytes:188567970 (179.8 MiB)
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.00GHz
stepping : 2
cpu MHz : 3000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pebs
bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips : 6018.47
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
processor : 1
vendor_id : GenuineIntel
cpu family : 15
model : 6
model name : Intel(R) Pentium(R) D CPU 3.00GHz
stepping : 2
cpu MHz : 3000.000
cache size : 2048 KB
physical id : 0
siblings : 2
core id : 1
cpu cores : 2
apicid : 1
initial apicid : 1
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 6
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat
pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc pebs
bts pni dtes64 monitor ds_cpl vmx cid cx16 xtpr pdcm lahf_lm tpr_shadow
bogomips : 6018.36
clflush size : 64
cache_alignment : 128
address sizes : 36 bits physical, 48 bits virtual
power management:
Best Regards,
Hayes
> -----Original Message-----
> From: Anand Raj Manickam [mailto:anandrm@gmail.com]
> Sent: Tuesday, February 01, 2011 6:38 PM
> To: Francois Romieu
> Cc: Ivan Vecera; netdev@vger.kernel.org; Hayeswang
> Subject: Re: Realtek r8168C / r8169 driver VLAN TAG stripping
>
> On Tue, Feb 1, 2011 at 3:42 PM, Francois Romieu
> <romieu@fr.zoreil.com> wrote:
> > Ivan Vecera <ivecera@redhat.com> :
> > [...]
> >> Unfortunately I have no local access (it's placed in
> China) or remote
> >> serial console to the system with this 8168c. The second
> problem is
> >> that the system is connected to the switch that does not pass the
> >> packets with VLAN tags -> it seems that at least Tx
> packets have the VLAN tag.
> >>
> >> I'm sorry I'm not able to help more.
> >
> > Thanks a lot for the information, it is both welcome and helpful.
> >
> > I'll freeze Anand's report for now as "8168c + unspecified glue
> > hardware bug with unknown product manufactured by Arkino on
> > unidentified motherboard with unknown number of processors".
>
> cat /proc/cpuinfo
> processor : 0
> vendor_id : AuthenticAMD
> cpu family : 16
> model : 6
> model name : AMD Sempron(tm) 140 Processor
> stepping : 2
> cpu MHz : 2700.641
> cache size : 1024 KB
> fdiv_bug : no
> hlt_bug : no
> f00f_bug : no
> coma_bug : no
> fpu : yes
> fpu_exception : yes
> cpuid level : 5
> wp : yes
> flags : fpu vme de pse tsc msr pae mce cx8 apic sep
> mtrr pge mca cmov
> pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext
> fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc up
> nonstop_tsc extd_apicid pni monitor cx16 popcnt lahf_lm svm
> extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw
> ibs skinit wdt npt lbrv svm_lock nrip_save
> bogomips : 5401.28
> clflush size : 64
> cache_alignment : 64
> address sizes : 48 bits physical, 48 bits virtual
> power management: ts ttp tm stc 100mhzsteps hwpstate
>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2011-02-09 9:52 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-13 14:40 Realtek r8168C / r8169 driver VLAN TAG stripping Anand Raj Manickam
2011-01-13 15:09 ` Anand Raj Manickam
2011-01-16 19:20 ` Francois Romieu
[not found] ` <AANLkTi=uNKMj_gs_bKRQ1tQa0TMwdnyrtVcR5JPNpmJv@mail.gmail.com>
2011-01-17 7:34 ` Anand Raj Manickam
2011-01-18 1:21 ` Francois Romieu
2011-01-27 10:35 ` Anand Raj Manickam
2011-01-27 15:07 ` Francois Romieu
2011-01-27 15:31 ` Anand Raj Manickam
2011-01-27 16:50 ` Francois Romieu
2011-01-28 1:40 ` Anand Raj Manickam
2011-01-28 12:06 ` Francois Romieu
2011-01-28 12:16 ` Anand Raj Manickam
2011-01-31 5:45 ` hayeswang
2011-01-31 13:14 ` Ivan Vecera
2011-02-01 10:12 ` Francois Romieu
2011-02-01 10:38 ` Anand Raj Manickam
2011-02-09 9:51 ` hayeswang
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.