From: Steffen Klassert <steffen.klassert@secunet.com>
To: Andre Valentin <avalentin@marcant.net>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<netdev@vger.kernel.org>
Subject: Re: Kernel Panic with vti Interfaces
Date: Fri, 27 Feb 2015 11:35:06 +0100 [thread overview]
Message-ID: <20150227103506.GD20631@secunet.com> (raw)
In-Reply-To: <54EFB312.8040309@marcant.net>
On Fri, Feb 27, 2015 at 12:58:10AM +0100, Andre Valentin wrote:
>
> >
> > I have never seen this, is the patch above the only locally
> > applied patch?
> No, the kernel is coming from the current openwrt 3.18 trunk.
> It's 3.18.7 with serveral patches coming from openwrt.
> I already checked the IPsec related patches but the error
> persisted.
>
> I will remove more patches to be sure and forward my results!
Please try with an unpatched kernel from kernel.org, thanks!
next prev parent reply other threads:[~2015-02-27 10:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54EC4C63.3050006@marcant.net>
2015-02-26 11:40 ` Kernel Panic with vti Interfaces Steffen Klassert
2015-02-26 23:58 ` Andre Valentin
2015-02-27 10:35 ` Steffen Klassert [this message]
2015-02-28 21:21 ` Andre Valentin
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=20150227103506.GD20631@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=avalentin@marcant.net \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.