From: Stephen Hemminger <shemminger@osdl.org>
To: Moire <sec@shee.org>
Cc: "<bridge@osdl.org> <bridge@osdl.org>" <bridge@osdl.org>
Subject: Re: [Bridge] Dead loop on virtual device - how to interpret it ?
Date: Wed, 16 Aug 2006 11:09:31 -0700 [thread overview]
Message-ID: <20060816110931.731d166d@localhost.localdomain> (raw)
In-Reply-To: <2fe13191741861f3e39da4d79f9b7c42@shee.org>
On Wed, 16 Aug 2006 14:05:26 +0200
Moire <sec@shee.org> wrote:
> Dear List,
>
> i am not so familiar with the deep art of
> network internals more with the basics one.
> Therefore i have a problem to interpret this
> error message:
>
> Dead loop on virtual device br0, fix it urgently!
>
> In the corresponding kernel code i found this quote:
>
> /* It may be transient configuration error,
> when hard_start_xmit() recurses. We detect
> it by checking xmit owner and drop the
> packet when deadloop is detected.
> */
>
> but i still have no idea what could be wrong.
What are the devices you are putting in the bridge?
What kernel version?
What are the commands being used to put the devices into
the bridge.
It looks like a bridge ended up including itself some how.
>
> My setup is an bridge (two interfaces) and local
> interface. The bridge connects the dmz with the internet.
>
> How can i reproduce this error message - to find the cause.
>
> What does it mean (for a not so advanced admin;).
>
> Thanks in advance for any help.
>
> C. Moire
>
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> https://lists.osdl.org/mailman/listinfo/bridge
>
next prev parent reply other threads:[~2006-08-16 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 12:05 [Bridge] Dead loop on virtual device - how to interpret it ? Moire
2006-08-16 18:09 ` Stephen Hemminger [this message]
2006-08-18 16:03 ` Moire
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=20060816110931.731d166d@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=bridge@osdl.org \
--cc=sec@shee.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