[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0a3e7a85-babb-8ae7-2c19-480c5203a8e5@codeaurora.org>
Date: Fri, 28 Apr 2017 09:59:32 +0530
From: Sricharan R <sricharan@...eaurora.org>
To: Ralph Sennhauser <ralph.sennhauser@...il.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Joerg Roedel <jroedel@...e.de>,
Bjorn Helgaas <bhelgaas@...gle.com>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
netdev@...r.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
Hi Ralph,
On 4/27/2017 7:05 PM, 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". 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 ?
>
Attached the patch with debug prints.
Regards,
Sricharan
View attachment "0001-Debug-prints.patch" of type "text/plain" (1113 bytes)
Powered by blists - more mailing lists