vkernel's tap/bridge use causing panics on real kernel.

Matthew Dillon dillon at apollo.backplane.com
Sat May 17 20:11:42 PDT 2008


:On Sun, May 18, 2008 at 5:06 AM, Matthew Dillon
:<dillon at apollo.backplane.com> wrote:
:>     Whoop, something done to the network stack has blown up bridge/tap
:>     operation.
:>
:>     This will generate the 'mbuf ... was not tracked' messages, and
:>     eventually panics.
:>
:> kldload if_bridge.ko
:> kldload if_tap.ko
:> ifconfig bridge0 create
:> ifconfig bridge0 addm nfe0
:
:You got following message, even when vkernel is not started?

    Yes, sorry I wasn't clear about that.

    I started getting the messages the moment I added nfe0 to the bridge,
    I had not yet touched tap or anything else... it was just the adding
    of nfe0 to an empty bridge that did it.

    (i.e. there was incidental traffic on nfe0 at the time, it being on my
    fairly busy network, which I presume was flowing into the bridge and
    resulting in the messages).

						-Matt





More information about the Commits mailing list