From: Andrew Morton <akpm@linux-foundation.org>
To: Jay Vosburgh <fubar@us.ibm.com>, Ben Greear <greearb@candelatech.com>
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org,
amartins@crefidis.fr
Subject: Re: [Bugme-new] [Bug 10283] New: Ooops when bonding and vlan on the same device
Date: Wed, 19 Mar 2008 14:00:56 -0700 [thread overview]
Message-ID: <20080319140056.4eff6571.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-10283-10286@http.bugzilla.kernel.org/>
(switching to email - please respond via emailed reply-to-all, not via the
bugzilla web interface)
On Wed, 19 Mar 2008 05:19:34 -0700 (PDT)
bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10283
>
> Summary: Ooops when bonding and vlan on the same device
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.18
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: low
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: amartins@crefidis.fr
>
>
> Latest working kernel version: ?
> Earliest failing kernel version: 2.6.18-6
> Distribution: Debian
> Hardware Environment: x86-686
> Software Environment: stable release of Debian ETCH
> Problem Description:
>
> Ooops when adding a vlan on a device that is in slave mode of a bond device
> (Sory for my english :)
>
> Steps to reproduce:
>
> modprobe bonding mode=1 miimon=100
> ifconfig eth0 promisc up
> ifenslave bond0 eth0
> ifconfig bond0 up
> vconfig add eth0 2 => Ooops
>
Is a copy of the oops output available?
Is there any possibility of testing a more up-to-date kernel?
Thanks.
next parent reply other threads:[~2008-03-19 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10283-10286@http.bugzilla.kernel.org/>
2008-03-19 21:00 ` Andrew Morton [this message]
2008-03-20 0:10 ` [Bugme-new] [Bug 10283] New: Ooops when bonding and vlan on the same device Jay Vosburgh
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=20080319140056.4eff6571.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=amartins@crefidis.fr \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=fubar@us.ibm.com \
--cc=greearb@candelatech.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.