From: Stephen Hemminger <stephen@networkplumber.org>
To: James Chapman <jchapman@katalix.com>
Cc: netdev@vger.kernel.org
Subject: Fw: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp]
Date: Sun, 1 Oct 2017 10:21:10 -0700 [thread overview]
Message-ID: <20171001102110.24184f1b@xeon-e3> (raw)
Begin forwarded message:
Date: Sun, 01 Oct 2017 16:22:33 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp]
https://bugzilla.kernel.org/show_bug.cgi?id=197099
Bug ID: 197099
Summary: Kernel panic in interrupt [l2tp_ppp]
Product: Networking
Version: 2.5
Kernel Version: 4.8.13-1.el6.elrepo.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: svimik@gmail.com
Regression: No
Created attachment 258685
--> https://bugzilla.kernel.org/attachment.cgi?id=258685&action=edit
stacktrace screenshot
Hello!
Getting kernel panics on multiple servers. Since it mentions l2tp_core,
l2tp_ppp and ppp_generic, I decided to report it to Networking (correct me if
I'm wrong).
Unfortunately I'm still struggling with making kdump work, so the trace
screenshot is all I have at this moment. The only hope is that this stacktrace
means something to the guys that wrote the code.
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2017-10-01 17:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 17:21 Stephen Hemminger [this message]
2017-10-02 13:32 ` Fw: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp] James Chapman
2017-10-02 13:56 ` Eric Dumazet
2017-10-02 18:35 ` SviMik
2017-10-03 7:27 ` James Chapman
2017-10-04 7:49 ` James Chapman
2017-10-04 10:33 ` Guillaume Nault
2017-10-06 4:45 ` SviMik
2017-10-06 9:52 ` James Chapman
2017-10-07 12:09 ` SviMik
2017-10-07 16:38 ` Denys Fedoryshchenko
2017-10-09 17:15 ` Guillaume Nault
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=20171001102110.24184f1b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jchapman@katalix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).