From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: Jan Kara <jack@suse.cz>
Cc: Guillaume Morin <guillaume@morinfr.org>,
stable@vger.kernel.org, decui@microsoft.com, jack@suse.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
mszeredi@redhat.com
Subject: Re: kernel panics with 4.14.X versions
Date: Wed, 18 Apr 2018 10:32:21 +0200 [thread overview]
Message-ID: <9cb08428-66ed-2306-d2f2-ae734863c68d@gmail.com> (raw)
In-Reply-To: <20180417121207.cs7eijrndovbplgz@quack2.suse.cz>
[-- Attachment #1.1: Type: text/plain, Size: 2299 bytes --]
On 17/04/2018 02:12 μμ, Jan Kara wrote:
> On Tue 17-04-18 01:31:24, Pavlos Parissis wrote:
>> On 16/04/2018 04:40 μμ, Jan Kara wrote:
>
> <snip>
>
>>> How easily can you hit this?
>>
>> Very easily, I only need to wait 1-2 days for a crash to occur.
>
> I wouldn't call that very easily but opinions may differ :). Anyway it's
> good (at least for debugging) that it's reproducible.
>
Unfortunately, I can't reproduce it, so waiting 1-2 days is the only option I have.
>>> Are you able to run debug kernels
>>
>> Well, I was under the impression I do as I have:
>> grep -E 'DEBUG_KERNEL|DEBUG_INFO' /boot/config-4.14.32-1.el7.x86_64
>> CONFIG_DEBUG_INFO=y
>> # CONFIG_DEBUG_INFO_REDUCED is not set
>> # CONFIG_DEBUG_INFO_SPLIT is not set
>> # CONFIG_DEBUG_INFO_DWARF4 is not set
>> CONFIG_DEBUG_KERNEL=y
>>
>> Do you think that my kernel doesn't produce a proper crash dump?
>> I have a production cluster where I can run any kernel we need, so if I need
>> to compile again with different settings I can certainly do that.
>
> OK, good. So please try running 4.16 as you mention below to verify whether
> this is just a -stable regression or also a problem in the current upstream
> kernel. Based on your results with 4.16 I'll prepare a debug patch for you to
> apply on top of 4.14.32 so that we can debug this further.
>
>>> / inspect
>>> crash dumps when the issue occurs?
>>
>> I can't do that as the server isn't responsive and I can only power cycle it.
>
> Well, kernel crash dumps work in that situation as well - when the kernel
> panics, it will kexec into a new kernel and dump memory of the old kernel
> to disk. It can then be investigated with the 'crash' utility. But
> obviously you don't have this set up and don't have experience with this so
> let's go via a standard 'debug patch' route.
>
>>> Also testing with the latest mainline
>>> kernel (4.16) would be welcome whether this isn't just an issue with the
>>> backport of fsnotify fixes from Miklos.
>>
>> I can try the kernel-ml-4.16.2 from elrepo (we use CentOS 7).
>
> Yes, that would be good.
>
I have production server running 4.16.2 and no kernel crash dumps yet.
Let's wait another day before we say anything.
Cheers,
Pavlos
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-18 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180416132550.d25jtdntdvpy55l3@bender.morinfr.org>
2018-04-16 14:40 ` kernel panics with 4.14.X versions Jan Kara
2018-04-16 16:06 ` Guillaume Morin
2018-04-16 21:10 ` Dexuan Cui
2018-04-17 10:33 ` Greg KH
2018-04-17 11:48 ` Amir Goldstein
2018-04-17 12:03 ` Jan Kara
2018-04-17 17:42 ` Dexuan Cui
2018-04-16 23:31 ` Pavlos Parissis
2018-04-17 11:18 ` Pavlos Parissis
2018-04-17 12:04 ` Jan Kara
2018-04-17 12:12 ` Jan Kara
2018-04-18 8:32 ` Pavlos Parissis [this message]
2018-04-19 20:23 ` Jan Kara
2018-04-19 21:16 ` Pavlos Parissis
2018-04-19 21:24 ` Robert Kolchmeyer
2018-04-19 21:37 ` Dexuan Cui
2018-04-20 10:21 ` Jan Kara
2018-04-20 17:43 ` Dexuan Cui
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=9cb08428-66ed-2306-d2f2-ae734863c68d@gmail.com \
--to=pavlos.parissis@gmail.com \
--cc=decui@microsoft.com \
--cc=guillaume@morinfr.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=stable@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).