linux-kernel - Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABXGCsPejOrb4yb3THfp6w+Od7ZAgQRpeCvYRhsTLZqJQdGYUQ@mail.gmail.com>
Date:   Sat, 10 Aug 2019 21:08:19 +0500
From:   Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To:     Alex Deucher <alexdeucher@...il.com>
Cc:     Michel Dänzer <michel@...nzer.net>,
        Hillf Danton <hdanton@...a.com>,
        Dave Airlie <airlied@...il.com>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
        amd-gfx list <amd-gfx@...ts.freedesktop.org>,
        Linux Memory Management List <linux-mm@...ck.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>,
        "Deucher, Alexander" <Alexander.Deucher@....com>,
        Harry Wentland <harry.wentland@....com>,
        "Koenig, Christian" <Christian.Koenig@....com>
Subject: Re: The issue with page allocation 5.3 rc1-rc2 (seems drm culprit here)

On Fri, 9 Aug 2019 at 23:55, Mikhail Gavrilov
<mikhail.v.gavrilov@...il.com> wrote:
> Finally initial problem "gnome-shell: page allocation failure:
> order:4, mode:0x40cc0(GFP_KERNEL|__GFP_COMP),
> nodemask=(null),cpuset=/,mems_allowed=0" did not happens anymore with
> latest version of the patch (I tested more than 23 hours)
>
> But I hit a new problem:
>
> [73808.088801] ------------[ cut here ]------------
> [73808.088806] DEBUG_LOCKS_WARN_ON(ww_ctx->contending_lock)
> [73808.088813] WARNING: CPU: 8 PID: 1348877 at
> kernel/locking/mutex.c:757 __ww_mutex_lock.constprop.0+0xb0f/0x10c0

[pruned]

> So I needed to report it separately (in another thread) or we continue here?

Today after reboot issue "DEBUG LOCKS
WARN_ON(ww_ctx->contending_lock)" happened again.

--
Best Regards,
Mike Gavrilov.

View attachment "dmesg2.txt" of type "text/plain" (5875 bytes)