From: Kurt Roeckx <Q@ping.be>
To: linux-kernel@vger.kernel.org
Subject: Dead loop on virutal device.
Date: Tue, 29 Jan 2002 17:12:47 +0100 [thread overview]
Message-ID: <20020129171247.A580@ping.be> (raw)
Since I'm using a 2.4.17 (upgrade from a 2.2.16), I get this
message:
Dead loop on virtual device tun1, fix it urgently!
Sometimes it's there a short time between them, other times a
long time.
I got no idea what's causing them.
I tried looking at the source and it says something about
recursion and something about SMP. This is not an SMP box.
The device in question is a tunnel device, it does ipv6 over
ipv4. Most traffic goes thru that one. It's the only one that
generates that message.
It says to fix it urgently, but I don't know how, and it seems to
work fine otherwise.
Do you know what is wrong and how I can fix this?
Kurt
reply other threads:[~2002-01-29 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020129171247.A580@ping.be \
--to=q@ping.be \
--cc=linux-kernel@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