From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Chubb Subject: Re: Can no longer shutdown after drm/radeon: Implement radeon_pci_shutdown Date: Thu, 12 Dec 2013 09:11:21 +1100 Message-ID: <84txefdomu.wl%peter.chubb@nicta.com.au> References: <84mwk86x5a.wl%peter.chubb@nicta.com.au> <20131211072658.GA273@x4> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from lemon.ertos.nicta.com.au (lemon.ertos.nicta.com.au [203.143.174.143]) by gabe.freedesktop.org (Postfix) with ESMTP id 9B457FA58D for ; Wed, 11 Dec 2013 14:11:47 -0800 (PST) In-Reply-To: <20131211072658.GA273@x4> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces@lists.freedesktop.org Errors-To: dri-devel-bounces@lists.freedesktop.org To: Markus Trippelsdorf Cc: alexander.deucher@amd.com, Peter Chubb , dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org >>>>> "Markus" == Markus Trippelsdorf writes: Markus> On 2013.12.11 at 11:37 +1100, Peter Chubb wrote: Markus> It would be interesting to know where exactly it hangs. Could Markus> you comment out the *_fini(rdev) calls in Markus> radeon_driver_unload_kms (drivers/gpu/drm/radeon/radeon_kms.c) Markus> one after the other to find out which one is responsible? It's radeon_device_fini() that is the problem. -- Dr Peter Chubb peter.chubb AT nicta.com.au http://www.ssrg.nicta.com.au Software Systems Research Group/NICTA