From mboxrd@z Thu Jan 1 00:00:00 1970 From: Denys Fedoryshchenko Subject: Re: Fw: [Bug 197099] New: Kernel panic in interrupt [l2tp_ppp] Date: Sat, 07 Oct 2017 19:38:48 +0300 Message-ID: References: <20171001102110.24184f1b@xeon-e3> <1506952566.8061.3.camel@edumazet-glaptop3.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Cc: James Chapman , netdev@vger.kernel.org, Guillaume Nault , netdev-owner@vger.kernel.org To: SviMik Return-path: Received: from nuclearcat.com ([144.76.183.226]:55252 "EHLO nuclearcat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751279AbdJGQiw (ORCPT ); Sat, 7 Oct 2017 12:38:52 -0400 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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