Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754637AbdGNPQ0 (ORCPT ); Fri, 14 Jul 2017 11:16:26 -0400 Received: from mout.gmx.net ([212.227.17.22]:57580 "EHLO mout.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754051AbdGNPQZ (ORCPT ); Fri, 14 Jul 2017 11:16:25 -0400 Message-ID: <1500045346.5763.21.camel@gmx.de> Subject: Re: [Nouveau] [regression drm/noveau] suspend to ram -> BOOM: exception RIP: drm_calc_vbltimestamp_from_scanoutpos+335 From: Mike Galbraith To: Karol Herbst , Tobias Klausmann Cc: Ilia Mirkin , Peter Zijlstra , David Airlie , "nouveau@lists.freedesktop.org" , LKML , "dri-devel@lists.freedesktop.org" , Ben Skeggs Date: Fri, 14 Jul 2017 17:15:46 +0200 In-Reply-To: References: <1499794333.5315.8.camel@gmx.de> <1499796510.5315.27.camel@gmx.de> <1499853345.23742.8.camel@gmx.de> <1499858703.23742.25.camel@gmx.de> <1500039368.5763.12.camel@gmx.de> <1500039693.5763.15.camel@gmx.de> <6341f91f-1c56-2188-f55b-2f47d23262fc@mni.thm.de> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.20.5 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:A7ysDLoCOpF1MAKgMhCIMy6lvwarw6hnaHltRKQ+8BvWFA1Rkki yPjfPW0e6apTocsOFxY25Lnp24h5i9mOSpZKzKKbKVmyBZ47jaOcz+LdysqqGP3TKqT8Oxd hsKGCkwLlt9wAkfbFc1DC8alzhC4dngVJ6JFdZZ4tqt/F7YkhQmHRIFx71pMvi1F/3+f2Mu sNxqUOuCz6SHHEtUaUF1w== X-UI-Out-Filterresults: notjunk:1;V01:K0:hVqrrRL3gWo=:z8g71eDJfGTQDWImWZwhO3 g3DCOkwEpA6NwzLoFTiQMHPzJdykDTsZXl6hzAlzlNJOGim3ySiCabve/2bEKDKZlFq/R4kcR S6KXOar5whOF9hy90JFRlMdj4NFfPW4sWm6szJwYB8Rp5XWQN/KyWNjGlccAf9PS47QV7kSSu +mvEGTN7WAPq8voJEOPzh/773eSdxcTwKYjP38NUTyQfONdOdxNlLUXbO/dmfNuamKT71+m4t jNlxyMh5MvYuj/E0ZXklbQeTK5EkBeX2NNz+f/tB92Dcpo9dRTwRL9d22C8w1yDU4W25wkI8s Go0k7BPcjp3Ahac92ZQLHHjyhWoiTcTGNIeZAZ7OhzMrScvFUcBlysOz5w3+wBDxjRCbMl0NK 6Z/inC/Bw2U5lVrwqj8G+/icoXuf3I1WQrUPymgdKWf8zS7IuHXoz7rRQhdE7xcoQhPSoQGce 4SWJvxR0QKC9mc/4JQxau0yE3KAH+qGTzH8L326Spcn5C5ESRRfjjJMXZl9nJ+c/OcVYp/Gai H8r47kK5yWLA1ZV3Mmo95u6UzVBj/IB1g30NLLSJm+tbUEdjKIagVLN9MiLkq9jSe1KS0ks0w OFdokK9VTSy+8hiI+w2z91VmjnEoaQGVtFN8Wu443WaG5P3rY0q6yZFHdUqr5rHorGgoboKRO tqCBw8IpFFPNuDrjJPuPXx0MjfXHfkhcODn+Iv5GeXlhLYZ4WLKMwRxxmQiKgKAbIbrqJEPb7 8ecrpVX+A7JYVUKF1O1WuAkP6rwuw3DuaLSBZQmNgab/p14zr46MPnQ0YFMrrXOhpIWV1Ao/v nEt09tp/bzhzb4tRbKhZP8n5GgKoxSAS+ORzDJgy7HcVNHSt8s= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 230 Lines: 7 On Fri, 2017-07-14 at 17:10 +0200, Karol Herbst wrote: > Yeah, we shouldn't let the machine die. Are there more WARN_ON_ONCE > usage we could convert to WARN_ONCE? Shooting the messenger is generally considered uncool :) -Mike