netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Pascal Terjan" <pterjan@gmail.com>
To: "Stephen Hemminger" <shemminger@linux-foundation.org>
Cc: "Jarek Poplawski" <jarkao2@o2.pl>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	netdev@vger.kernel.org,
	"bugme-daemon@kernel-bugs.osdl.org"
	<bugme-daemon@bugzilla.kernel.org>
Subject: Re: [Bugme-new] [Bug 7962] New: oops in port_carrier_check
Date: Fri, 9 Feb 2007 19:50:17 +0100	[thread overview]
Message-ID: <e8ca35370702091050naaa9669n2d19fec4b429c07f@mail.gmail.com> (raw)
In-Reply-To: <20070209095204.7f43a964@oldman>

2007/2/9, Stephen Hemminger <shemminger@linux-foundation.org>:
> The carrier_check is canceled by removal of port from bridge.
> Perhaps there is something broken in rcu assumptions under Qemu

If that can help:
I started /stopped qemu several times. Maybe I started /stopped qemu
several times as I was testing new PXE support in qemu with different
virtual nic. Each time, a tun device was created by qemu at startup
and added to the bridge, and destroyed on exit.

  reply	other threads:[~2007-02-09 18:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-07 20:52 Fw: [Bugme-new] [Bug 7962] New: oops in port_carrier_check Andrew Morton
2007-02-07 22:09 ` Stephen Hemminger
2007-02-09  7:42   ` Jarek Poplawski
2007-02-09 17:52     ` Stephen Hemminger
2007-02-09 18:50       ` Pascal Terjan [this message]
2007-02-12  6:44       ` Jarek Poplawski
2007-02-12 10:28         ` [PATCH][NET][BRIDGE] br_if: " Jarek Poplawski
2007-02-12 17:47           ` Stephen Hemminger
2007-02-13  6:26             ` Jarek Poplawski
2007-02-13 19:55               ` Stephen Hemminger
2007-02-13 20:35                 ` David Miller
2007-02-14  8:07                   ` 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=e8ca35370702091050naaa9669n2d19fec4b429c07f@mail.gmail.com \
    --to=pterjan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=jarkao2@o2.pl \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@linux-foundation.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).