Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932944AbcKDUi3 (ORCPT ); Fri, 4 Nov 2016 16:38:29 -0400 Received: from mail-oi0-f49.google.com ([209.85.218.49]:32796 "EHLO mail-oi0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752675AbcKDUi0 (ORCPT ); Fri, 4 Nov 2016 16:38:26 -0400 MIME-Version: 1.0 In-Reply-To: References: From: Linus Torvalds Date: Fri, 4 Nov 2016 13:38:25 -0700 X-Google-Sender-Auth: H5BYWhqmmQzwmxbr5FjQ_H56c3g Message-ID: Subject: Re: [git pull] drm fixes for 4.9-rc4 To: Dave Airlie Cc: LKML , dri-devel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 888 Lines: 21 On Wed, Nov 2, 2016 at 5:31 PM, Dave Airlie wrote: > > There are a set of fixes for an oops we've been seeing around MST > display unplug, Side note: I heard from a couple of people at the KS that said that they had had problems with suspend/resume after plugging in to a 4k display (but _only_ a 4k display - apparently normal FHD displays didn't show this). I think at least one was USB3/Thunderbolt. Ted with a Lenovo laptop (intel GPU) was one, I forget who else mentioned this. I wonder if MST may have been involved. That would explain the "only happens for 4k" issue - I assume pretty much all MST displays are 4k. suspend/resume might obviously fall very much under that "unplug" issue and maybe this pull request thus already fixes it, but there might be something that is specific to _just_ suspend/resume too. Mind taking a look? Linus