From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Linux Networking Developer Mailing List <netdev@vger.kernel.org>,
openadsl-users@lists.sourceforge.net,
openadsl-devel@lists.sourceforge.net, support@traverse.com.au,
support@rocksolidelectronics.com, 660804@bugs.debian.org
Subject: Re: [Bug 42809] New: kernel panic when receiving an ipsec packet
Date: Thu, 23 Feb 2012 01:59:46 +0100 [thread overview]
Message-ID: <4F458F82.3060808@linuxsystems.it> (raw)
In-Reply-To: <4F4528CE.7080702@linuxsystems.it>
Hi,
The bug is still present in latest 3.2.7 vanilla kernel. I wasted the
whole day debugging that damn thing and I finally discovered the root cause.
The problem is with my Traverse Solos multi-port ADSL2+ PCI card[1]
(which has open source drivers included in the kernel) when using RFC
2684 routed.
I have two adsl lines, the first one connected using RFC 2684 routed,
the second one using PPPoA.
If I create a vpn toward the PPPoA line it works flawlessly, while if I
create a vpn toward the RFC 2684 routed line the whole system hangs in a
kernel panic (with both 2.6.32.54 and 3.2.7).
I really don't know how to fix it and I need to setup that damn ipsec vpn :(
This is the bug on bugzilla.kernel.org:
https://bugzilla.kernel.org/show_bug.cgi?id=42809
Niccolò
[1]http://www.traverse.com.au/productview.php?product_id=116
next prev parent reply other threads:[~2012-02-23 0:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-42809-100@https.bugzilla.kernel.org/>
2012-02-22 17:20 ` [Bug 42809] New: kernel panic when receiving an ipsec packet Stephen Hemminger
2012-02-22 17:41 ` Niccolò Belli
2012-02-23 0:59 ` Niccolò Belli [this message]
2012-02-23 1:38 ` Eric Dumazet
2012-02-23 1:46 ` [openadsl-users] " Jason White
2012-02-23 1:54 ` Eric Dumazet
2012-02-23 13:48 ` Bug#660804: " chas williams - CONTRACTOR
2012-02-23 1:55 ` Niccolò Belli
2012-02-23 2:02 ` Niccolò Belli
2012-02-23 2:06 ` Eric Dumazet
2012-02-23 2:12 ` Niccolò Belli
2012-02-23 13:45 ` Niccolò Belli
2012-02-23 14:36 ` Eric Dumazet
2012-02-23 14:39 ` Eric Dumazet
2012-02-23 19:08 ` Niccolò Belli
2012-02-23 20:11 ` David Miller
2012-02-23 20:17 ` Eric Dumazet
2012-02-23 20:23 ` David Miller
2012-02-23 20:28 ` Eric Dumazet
2012-02-23 20:55 ` [PATCH V2] ipsec: be careful of non existing mac headers Eric Dumazet
2012-02-23 21:53 ` David Miller
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=4F458F82.3060808@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=660804@bugs.debian.org \
--cc=netdev@vger.kernel.org \
--cc=openadsl-devel@lists.sourceforge.net \
--cc=openadsl-users@lists.sourceforge.net \
--cc=shemminger@vyatta.com \
--cc=support@rocksolidelectronics.com \
--cc=support@traverse.com.au \
/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.