netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: Re: Kernel panic eth2 mirred redirect to ifb0
Date: Sun, 19 Dec 2010 12:39:05 +0100	[thread overview]
Message-ID: <4D0DEED9.1060107@itcare.pl> (raw)
In-Reply-To: <4D0DEDF9.7020102@itcare.pl>

[-- Attachment #1: Type: text/plain, Size: 2162 bytes --]

W dniu 2010-12-19 12:35, Paweł Staszewski pisze:
> Hi all
>
> I have panic with kernel 2.6.37-rc6-git2 when use iproute2 
> mirred/redirect action
>
>
> host1 (kernel 2.6.36.2)
> netperf client -> eth3 (82598EB 10-Gigabit AT CX4) - directly 
> connected to eth2 of host2
> ethtool -k eth3
> Offload parameters for eth3:
> rx-checksumming: on
> tx-checksumming: on
> scatter-gather: on
> tcp-segmentation-offload: on
> udp-fragmentation-offload: off
> generic-segmentation-offload: on
> generic-receive-offload: on
> large-receive-offload: off
> rx-vlan-offload: off
> tx-vlan-offload: off
> ntuple-filters: off
> receive-hashing: off
>
> ethtool -i eth3
> driver: ixgbe
> version: 2.0.84-k2
> firmware-version: 1.12-2
> bus-info: 0000:03:00.1
>
>
> host2 (kernel-2.6.37-rc6-git2)
> netserver -> eth2 (82598EB 10-Gigabit AT CX4) - directly connected to 
> eth3 of host1
>
> ethtool -k eth2
> Offload parameters for eth2:
> rx-checksumming: on
> tx-checksumming: on
> scatter-gather: on
> tcp-segmentation-offload: on
> udp-fragmentation-offload: off
> generic-segmentation-offload: on
> generic-receive-offload: on
> large-receive-offload: off
> rx-vlan-offload: on
> tx-vlan-offload: on
> ntuple-filters: off
> receive-hashing: off
>
> ethtool -i eth2
> driver: ixgbe
> version: 2.0.84-k2
> firmware-version: 1.12-2
> bus-info: 0000:03:00.0
>
>
>
> Normally without ifb and redirect netperf show:
> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.0.2 
> (192.168.0.2) port 0 AF_INET
> Recv   Send    Send
> Socket Socket  Message  Elapsed
> Size   Size    Size     Time     Throughput
> bytes  bytes   bytes    secs.    10^6bits/sec
>
>  87380  16384  16384    10.00    9042.14
>
>
> Steps to reproduce panic:
> ip link set dev ifb0 up
>
> tc qdisc add dev eth2 ingress
>
> tc filter add dev eth2 parent ffff: protocol ip prio 10 u32 \
> match ip src 0.0.0.0/0 flowid 1:1 \
> action mirred egress redirect dev ifb0
>
>
> After this when i start netperf on host1 I have panic (screenshot in 
> attached image).
>
> Thanks
> Pawel
In next attached image is second screenshot (different - trace) - but 
with the same configuration


Regards
Pawel

[-- Attachment #2: ifb-eth2-mirred-redirect-panic-part2.JPG --]
[-- Type: image/jpeg, Size: 91665 bytes --]

  reply	other threads:[~2010-12-19 11:39 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-19 11:35 Kernel panic eth2 mirred redirect to ifb0 Paweł Staszewski
2010-12-19 11:39 ` Paweł Staszewski [this message]
2010-12-19 15:43 ` Eric Dumazet
2010-12-19 16:09   ` Paweł Staszewski
2010-12-19 16:22     ` Changli Gao
2010-12-19 20:34       ` Paweł Staszewski
2010-12-19 22:15         ` Jarek Poplawski
2010-12-19 22:21           ` Jarek Poplawski
2010-12-19 22:26             ` Jarek Poplawski
2010-12-20  8:01               ` Paweł Staszewski
2010-12-20  8:06                 ` Eric Dumazet
2010-12-20  9:13                   ` Paweł Staszewski
2010-12-20  8:56                 ` Changli Gao
2010-12-20  9:08                   ` Eric Dumazet
2010-12-20  9:11                     ` Changli Gao
2010-12-20  9:21                       ` Eric Dumazet
2010-12-20 10:32                         ` Jarek Poplawski
2010-12-20 10:41                           ` Eric Dumazet
2010-12-20 11:11                             ` Jarek Poplawski
2010-12-20 11:58                               ` Jarek Poplawski
2010-12-20 12:07                                 ` Paweł Staszewski
2010-12-20 12:22                                   ` Jarek Poplawski
2010-12-20 12:45                                     ` Eric Dumazet
2010-12-20 12:54                                       ` Eric Dumazet
2010-12-20 13:02                                         ` Jarek Poplawski
2010-12-20 14:05                                           ` Changli Gao
2010-12-20 14:25                                             ` [PATCH net-next-2.6] ifb: add performance flags to dev->features Eric Dumazet
2010-12-20 14:43                                               ` Changli Gao
2010-12-28 21:50                                               ` David Miller
2010-12-28 22:36                                                 ` Eric Dumazet
2010-12-28 23:07                                                   ` Jarek Poplawski
2011-01-02 20:24                                                     ` [PATCH v2 net-next-2.6] ifb: add performance flags Eric Dumazet
2011-01-03 19:37                                                       ` Jarek Poplawski
2011-01-03 19:40                                                         ` David Miller
2011-01-03 20:35                                                           ` Eric Dumazet
2011-01-03 20:40                                                             ` David Miller
2010-12-20 12:30                                   ` Kernel panic eth2 mirred redirect to ifb0 Changli Gao
2010-12-20 13:37                                     ` Jarek Poplawski

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=4D0DEED9.1060107@itcare.pl \
    --to=pstaszewski@itcare.pl \
    --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).