From: "Michael Chan" <mchan@broadcom.com>
To: "Iain Paton" <selsinork@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.37 vlans on bnx2 not functional, panic with tcpdump
Date: Thu, 6 Jan 2011 15:52:21 -0800 [thread overview]
Message-ID: <1294357941.21580.2.camel@HP1> (raw)
In-Reply-To: <4D2634DE.2060907@gmail.com>
On Thu, 2011-01-06 at 13:32 -0800, Iain Paton wrote:
> Hi,
>
> vlans don't appear to be functional on my HP DL380G6 with onboard bnx2
> adapter using vanilla 2.6.37 kernel. No tagged vlan traffic
> is arriving at the vlan interface.
VLANs on net-next-2.6 kernel works for me on bnx2 devices. I'll try
2.6.37 next.
>
> To reproduce, use vanilla 2.6.37 built with the attached config
>
> ip link add link eth0 name v406 type vlan id 406
> ip link set up dev eth0
> ip link set up dev v406
> ip addr add 10.251.0.3/16 dev v406
>
> from another machine on the same vlan run a ping to 10.251.0.3, ping
> returns destination host unreachable.
>
> tcpdump -n -e -i v406 shows no traffic.
>
> If I then run
>
> tcpdump -n -e -i eth0
>
> while the ping is still running I get
>
> [ 112.190114] BUG: unable to handle kernel NULL pointer dereference
> at 0000000000000008
next prev parent reply other threads:[~2011-01-06 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 21:32 2.6.37 vlans on bnx2 not functional, panic with tcpdump Iain Paton
2011-01-06 23:52 ` Michael Chan [this message]
2011-01-07 0:46 ` Michael Chan
2011-01-07 9:03 ` selsinork
[not found] ` <AANLkTi=PGPVRbS3XViskpZ0GSS8ouBcgVZYYG9EoM-Nz@mail.gmail.com>
2011-01-07 17:50 ` Michael Chan
2011-01-07 18:01 ` Iain Paton
2011-01-08 18:41 ` Jarek Poplawski
2011-01-09 11:22 ` Iain Paton
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=1294357941.21580.2.camel@HP1 \
--to=mchan@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=selsinork@gmail.com \
/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).