From: Stephen Hemminger <shemminger@vyatta.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: lkml@Think-Future.de,
Linux Kernel-Liste <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, bridge@lists.linux-foundation.org
Subject: Re: PROBLEM: oops w/ bridge in 2.6.32.7
Date: Mon, 8 Feb 2010 15:47:35 -0800 [thread overview]
Message-ID: <20100208154735.1d60f43c@nehalam> (raw)
In-Reply-To: <20100208142044.6be97024.akpm@linux-foundation.org>
On Mon, 8 Feb 2010 14:20:44 -0800
Andrew Morton <akpm@linux-foundation.org> wrote:
> > virtualbox-ose 3.1.2-dfsg-1+b1
> > virtualbox-ose-source 3.1.2-dfsg-1
> >
Sorry, since virtualbox is not part of standard mainline kernel,
I suspect the problem is there.
Please reproduce with standard 2.6.32.X distribution.
next prev parent reply other threads:[~2010-02-08 23:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100206165351.GA9411@localhost>
2010-02-08 22:20 ` PROBLEM: oops w/ bridge in 2.6.32.7 Andrew Morton
2010-02-08 23:47 ` Stephen Hemminger [this message]
2010-02-18 13:34 ` lkml
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=20100208154735.1d60f43c@nehalam \
--to=shemminger@vyatta.com \
--cc=akpm@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@Think-Future.de \
--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).