Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030825AbdD0Iyn (ORCPT ); Thu, 27 Apr 2017 04:54:43 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:45928 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S968145AbdD0Iya (ORCPT ); Thu, 27 Apr 2017 04:54:30 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 9DA5660F69 Authentication-Results: pdx-caf-mail.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: pdx-caf-mail.web.codeaurora.org; spf=none smtp.mailfrom=sricharan@codeaurora.org Subject: Re: [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta To: Joerg Roedel , Ralph Sennhauser Cc: "Rafael J. Wysocki" , Bjorn Helgaas , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Thomas Petazzoni , netdev@vger.kernel.org References: <20170426181508.687b52af@gmail.com> <20170427084427.GV5077@suse.de> From: Sricharan R Message-ID: <28fbd821-c975-48e0-92bf-2d3938286cc5@codeaurora.org> Date: Thu, 27 Apr 2017 14:24:22 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1 MIME-Version: 1.0 In-Reply-To: <20170427084427.GV5077@suse.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 817 Lines: 28 Hi Joerg, On 4/27/2017 2:14 PM, Joerg Roedel wrote: > Sricharan, > > On Wed, Apr 26, 2017 at 06:15:08PM +0200, Ralph Sennhauser wrote: >> Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time >> for platform/amba/pci bus devices") causes a kernel panic as in the log >> below on an armada-385. Reverting the commit fixes the issue. > > Any insight here? I tend to revert the patch in my tree, or is there a > quick and easy fix? I am checking on this manually to see what could be going wrong in the driver. From logs i could not conclude directly. I will need some more testing help (i will ask for) to root cause this. Regards, Sricharan > > > > Joerg > -- "QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation