Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1751134AbdLaPzA convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Sun, 31 Dec 2017 10:55:00 -0500
Received: from mail.fireflyinternet.com ([109.228.58.192]:56166 "EHLO
        fireflyinternet.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org
        with ESMTP id S1750854AbdLaPy7 (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Sun, 31 Dec 2017 10:54:59 -0500
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=78.156.65.138;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
To: Alexandru Chirvasitu <achirvasub@gmail.com>,
        "Jani Nikula" <jani.nikula@linux.intel.com>,
        "Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
        "Rodrigo Vivi" <rodrigo.vivi@intel.com>
From: Chris Wilson <chris@chris-wilson.co.uk>
In-Reply-To: <20171230173132.GA2369@chirva-void>
Cc: intel-gfx@lists.freedesktop.org,
        "kernel list" <linux-kernel@vger.kernel.org>
References: <20171230173132.GA2369@chirva-void>
Message-ID: <151473569074.2051.18107105776550332791@mail.alporthouse.com>
User-Agent: alot/0.3.6
Subject: Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5
Date: Sun, 31 Dec 2017 15:54:50 +0000
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 1305
Lines: 26

Quoting Alexandru Chirvasitu (2017-12-30 17:31:32)
> Short description: I get freezes of my desktop completely eliminating
> mouse / keyboard functionality.
> 
> I’m on an UltraLap 5330, Processor: i7-7500U, Memory: 32 GB DDR4-2133
> Video Card: Intel HD (included). It's running Void linux 64 bit. That
> distro's latest kernel is 4.14.8, but I've been trying out the 4.15-rc
> kernels. This has happened with rc3, rc4 and currently rc5.
> 
> I can ssh into the frozen machine and roam around freely. Xorg shows
> as <defunct> when I do, and nothing I have tried on the command line
> has succeeded in restroing functionality (killing processes, changing
> runlevels, etc.; there's no visible response from the computer). Only
> reboots resolve the matter (button reboots or issued as commands
> through ssh).
> 
> While ssh-d in I can get the dmesg log, which is attached. The
> relevant portion is presumably the trace at the very end.

I can't find how this can happen, the lists here are serialized by
struct_mutex. (The poison would indicate that the elements p->dfs_link
points to are freed, not p itself.) If you could run with lockdep (to
verify that the locks are indeed held here) and kasan to find the
alloc/free of the struct being used-after-free, that would be extremely
valuable.
-Chris