[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170427164014.422a124c@gmail.com>
Date: Thu, 27 Apr 2017 16:40:14 +0200
From: Ralph Sennhauser <ralph.sennhauser@...il.com>
To: Sricharan R <sricharan@...eaurora.org>
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
On Thu, 27 Apr 2017 19:05:09 +0530
Sricharan R <sricharan@...eaurora.org> 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.
Regards
Ralph
Powered by blists - more mailing lists