Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423918AbdD1GTi (ORCPT ); Fri, 28 Apr 2017 02:19:38 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:36265 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1163951AbdD1GT3 (ORCPT ); Fri, 28 Apr 2017 02:19:29 -0400 Date: Fri, 28 Apr 2017 08:19:19 +0200 From: Ralph Sennhauser To: Sricharan R Cc: "Rafael J. Wysocki" , Joerg Roedel , Bjorn Helgaas , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org, Thomas Petazzoni , netdev@vger.kernel.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 Message-ID: <20170428081919.21bb569d@gmail.com> In-Reply-To: <524b7fc8-1eca-a7d8-7bc7-6743be17c208@codeaurora.org> References: <20170426181508.687b52af@gmail.com> <2fb57b9b-3944-d9cc-1fac-8dcccaa0c37a@codeaurora.org> <20170427164014.422a124c@gmail.com> <524b7fc8-1eca-a7d8-7bc7-6743be17c208@codeaurora.org> Organization: none X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2356 Lines: 71 On Fri, 28 Apr 2017 11:13:33 +0530 Sricharan R wrote: > Hi Ralph, > > On 4/27/2017 8:10 PM, Ralph Sennhauser wrote: > > On Thu, 27 Apr 2017 19:05:09 +0530 > > Sricharan R wrote: > > > >> Hi, > >> > >> On 4/26/2017 9:45 PM, Ralph Sennhauser wrote: > >>> Hi Sricharan R, > >>> > >>> 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. > >>> > >>> Regards > >>> Ralph > >> > >> Somehow not getting a obvious clue on whats going wrong with the > >> logs below. From the log and looking in to dts, the drivers seems > >> to the one for "marvell,armada-370-neta". > > > > Correct. > > > >> Issue looks the data from the dma > >> has gone bad and subsequently referring the wrong data has resulted > >> in the crash. Looks like the dma_masks is the one going wrong. > >> Can i get some logs from mvneta_probe, about dev->dma_mask, > >> dev->coherent_dma_mask and dev->dma_ops with and without the patch > >> to see whats the difference ? > > > > Not sure I understood what exactly you are after. Might be faster to > > just send me a patch with all debug print statements you like to > > see. > > Attached the patch with debug prints. > > Regards, > Sricharan > Hi Sricharan With commit 09515ef5ddad [ 1.288962] mvneta f1070000.ethernet: dev->dma_mask 0xffffffff [ 1.294827] mvneta f1070000.ethernet: dev->coherent_dma_mask 0xffffffff [ 1.301472] mvneta f1070000.ethernet: dev->dma_ops 0x40b00c0601460 [ 1.322047] mvneta f1034000.ethernet: dev->dma_mask 0xffffffff [ 1.327904] mvneta f1034000.ethernet: dev->coherent_dma_mask 0xffffffff [ 1.334549] mvneta f1034000.ethernet: dev->dma_ops 0x40b00c0601460 With the patch reverted, the build that works [ 1.289001] mvneta f1070000.ethernet: dev->dma_mask 0xffffffff [ 1.294866] mvneta f1070000.ethernet: dev->coherent_dma_mask 0xffffffff [ 1.301511] mvneta f1070000.ethernet: dev->dma_ops 0x40b00c06014a8 [ 1.317005] mvneta f1034000.ethernet: dev->dma_mask 0xffffffff [ 1.322867] mvneta f1034000.ethernet: dev->coherent_dma_mask 0xffffffff [ 1.329508] mvneta f1034000.ethernet: dev->dma_ops 0x40b00c06014a8 Regards Ralph