netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Denys Fedoryshchenko <nuclearcat@nuclearcat.com>
To: SviMik <svimik@gmail.com>
Cc: James Chapman <jchapman@katalix.com>,
	netdev@vger.kernel.org, Guillaume Nault <g.nault@alphalink.fr>,
	netdev-owner@vger.kernel.org
Subject: Re: Fw: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp]
Date: Sat, 07 Oct 2017 19:38:48 +0300	[thread overview]
Message-ID: <f74effad2ec9b6a1a1bdbf25d6bd3801@nuclearcat.com> (raw)
In-Reply-To: <CA++DawbMB8aFa3s-0jW2CC5pRTU2Ui4ec6GSRCkhMotGGj_Ytg@mail.gmail.com>

On 2017-10-07 15:09, SviMik wrote:
> 
> Unfortunately, netconsole has managed to send a kernel panic trace
> only once, and it's not related to this bug. Looks like something
> crashes really hard to make netconsole unusable.
In some cases i had luck with pstore, when netconsole failed me 
(especially networking bugs), it stores panic messages more reliably, 
especially on recent platforms who have ERST and EFI.
https://www.kernel.org/doc/Documentation/ABI/testing/pstore

  reply	other threads:[~2017-10-07 16:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-01 17:21 Fw: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp] Stephen Hemminger
2017-10-02 13:32 ` 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 [this message]
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=f74effad2ec9b6a1a1bdbf25d6bd3801@nuclearcat.com \
    --to=nuclearcat@nuclearcat.com \
    --cc=g.nault@alphalink.fr \
    --cc=jchapman@katalix.com \
    --cc=netdev-owner@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=svimik@gmail.com \
    /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).