From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1756179AbdESCDQ convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Thu, 18 May 2017 22:03:16 -0400
Received: from mout.gmx.net ([212.227.15.15]:52322 "EHLO mout.gmx.net"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1755259AbdESCC7 (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 18 May 2017 22:02:59 -0400
Message-ID: <1495159363.6762.1.camel@gmx.de>
Subject: Re: [drm:qxl] BUG: sleeping function called from invalid context -
 qxl_bo_kmap_atomic_page()...splat
From: Mike Galbraith <efault@gmx.de>
To: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
Cc: LKML <linux-kernel@vger.kernel.org>, Dave Airlie <airlied@redhat.com>,
        Gerd Hoffmann <kraxel@redhat.com>, dri-devel@lists.freedesktop.org
Date: Fri, 19 May 2017 04:02:43 +0200
In-Reply-To: <87inkxvqy4.fsf@dilma.collabora.co.uk>
References: <1494239599.11523.21.camel@gmx.de>
         <87mvan9ljx.fsf@dilma.collabora.co.uk> <1494297462.20252.9.camel@gmx.de>
         <87inkxvqy4.fsf@dilma.collabora.co.uk>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.20.5 
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
X-Provags-ID: V03:K0:jHsfe4OpS9UqWoUrmPFEhaISz7xDSKm/MC+n4L2zWnH/ma9UiNb
 I+7I5pQ5vBQh/isCYct0FbbbTnGtrHXVPVgqVJCnloxctvJdUbjDbqPoW4Q7R3qLRYeI7x0
 VoVFi4BR4fHzYGstpSOXmpQiIcHYGK5K7guNlARigWlslgy4k1KstCkCSAZaL9Bx/D2A6nv
 OhvMGmbBA3WtOOSI0jObQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:+arrv67w6Xc=:vFXSgTbzbiNrHvzYD5cYfG
 GQPbnZhwtO4M3yWmOXHdD33hW0dubkLdTxGdoGUlU8Z1nTxtqvNImw8KVzDEVt5El4gh+QmME
 +WNnS6rkvvb4CIN9U6TA/mgFvGVCXYohSa0mekwwZ8jAMK5WjqQe69NiOa8IvkihcfmRrrb1Z
 ShXv2yBQ68Z5A0q04lr4t1dzSkjLs/8krrG0wcsaxfHS6sFctVc4fcDBlSFYVER+KvoXSZvjR
 JDOhK7wCAYQS8DKbGdGAtGZqu0P3j0OVtn82gBWaRe17NjXWJ6nQzsNCDJkCW/tAakw1bNbSS
 RUod6/us9mET6C2q3ph0tBOVBjQqRz59q0cN22INHON52RAoJmExwgEQMtdjMSWB6hasQmP23
 knTVSuE20Q+3YP7Iiw5xrqJQ669IdsEitLoUOA0B8DFsUZ0m4PuebAyBOmfTYKXLos2QC1c5d
 7lho76eYZT0gFZ3ZdgqTFMGCo7esyOXegvSz88dT9tlTh8/6L+QN2bbb7NLK/Yo++MSPtBkXZ
 /Cmd/m6N7+Mn6/gruqxVnnBAm3UN5I9nrldA6JvbBPxe8Nx/eTojrE51RA9t2/C5v+luwBoYH
 NEh117XQgs9X/1FiKx6zHbFzuLq2icWS37OY6dyYiRfXGLru8kQ958l8jwsqCO01JIOLfUYfg
 1pH9o5Yr4mpbUdI2+3qLzd2u7+8zKrkNthm+5gb1m16Xu+zfdG6EIZ11Ny3muEvh6aa1tydaZ
 gX6h5bvr3DrwL11yknwLJjqqxLIYxAbIV7Kl9s3Wtw9gFcDitXQ6cbwwdy9c5RhmBscESt5vY
 VUBBY3O
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, 2017-05-18 at 17:40 -0300, Gabriel Krisman Bertazi wrote:
> > Mike Galbraith <efault@gmx.de> writes:
> 
> > 
> > On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote:
> > 
> > > 
> > > Thanks for reporting this.  Can you confirm the following patch prevents
> > > the issue?
> > 
> > Nope, it still gripes.
> 
> Oops... Thanks for checking.  The following patch fixes the issue for
> me.  Can you please test that one?

Yup, all better.

	-Mike