linux-kernel - Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5

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: <20171231165236.GA3774@arch-chirva.localdomain>
Date:   Sun, 31 Dec 2017 11:52:36 -0500
From:   Alexandru Chirvasitu <achirvasub@...il.com>
To:     Chris Wilson <chris@...is-wilson.co.uk>
Cc:     Jani Nikula <jani.nikula@...ux.intel.com>,
        Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        intel-gfx@...ts.freedesktop.org,
        kernel list <linux-kernel@...r.kernel.org>
Subject: Re: PROBLEM: i915 causes complete desktop freezes in 4.15-rc5

I see lockdep is configured (though I'm not familiar with the feature;
the config came with it, and I made oldconfig), but I'll need to
recompile for kasan.

I'll do that over the next few days, but once done, what would I get
back to you with? Again logs if / when the problem occurs? I'm still
unable to trigger it reliably.

---

For now, here's also the Xorg log from a boot that went astray (named
xlog); this was a differnt one, and the problem manifested
differently: still locked out of the system save for ssh, but Xorg
eating up 100% of CPU (and dmesg did *not* register the trace that
time).

The problem has occurred in both forms at different times: Xorg
quietly going <defunct> or eating up 100% CPU. 

---

Some additional info: n the Void system I mentioned I have Openbox. On
this same computer I also alternately boot Arch with i3 instead,
currently on 4.15-rc4. I have *not* encountered the issue here..

I'm attaching my current boot's journalctl (for the Arch system, not
showing the problem) as well as the output of `lspci -k` and the
config for *this* 4.15-rc4 kernel (again, different OS, same
computer).

As for Xorg, the currently running one:

X.Org X Server 1.19.6
Release Date: 2017-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.9.71-1-lts x86_64 
Current Operating System: Linux arch-chirva 4.15.0-rc4-sys #1 SMP PREEMPT Fri Dec 22 10:01:22 EST 2017 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-rc4-sys root=UUID=9e8b1d07-793c-4115-be2f-1974bfe92d61 rw crashkernel=256M quiet
Build Date: 25 December 2017  02:02:38PM
 
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.



On Sun, Dec 31, 2017 at 03:54:50PM +0000, Chris Wilson wrote:
> 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

View attachment "xlog" of type "text/plain" (35533 bytes)

View attachment "config-4.15.0-rc4-sys-arch" of type "text/plain" (196613 bytes)

View attachment "lspci" of type "text/plain" (3290 bytes)

View attachment "config-4.15.0-rc4-sys-arch" of type "text/plain" (196614 bytes)