From: Sricharan R <sricharan@codeaurora.org>
To: Joerg Roedel <jroedel@suse.de>,
Ralph Sennhauser <ralph.sennhauser@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Bjorn Helgaas <bhelgaas@google.com>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
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
Date: Thu, 27 Apr 2017 14:24:22 +0530 [thread overview]
Message-ID: <28fbd821-c975-48e0-92bf-2d3938286cc5@codeaurora.org> (raw)
In-Reply-To: <20170427084427.GV5077@suse.de>
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
next prev parent reply other threads:[~2017-04-27 8:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-26 16:15 [REGRESSION next-20170426] Commit 09515ef5ddad ("of/acpi: Configure dma operations at probe time for platform/amba/pci bus devices") causes oops in mvneta Ralph Sennhauser
2017-04-27 8:44 ` Joerg Roedel
2017-04-27 8:54 ` Sricharan R [this message]
2017-04-27 13:35 ` Sricharan R
2017-04-27 14:40 ` Ralph Sennhauser
2017-04-28 5:43 ` Sricharan R
2017-04-28 6:19 ` Ralph Sennhauser
2017-04-28 11:56 ` Sricharan R
2017-04-28 12:25 ` Ralph Sennhauser
2017-04-28 13:18 ` Sricharan R
2017-04-28 15:00 ` Joerg Roedel
2017-04-28 4:29 ` Sricharan R
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=28fbd821-c975-48e0-92bf-2d3938286cc5@codeaurora.org \
--to=sricharan@codeaurora.org \
--cc=bhelgaas@google.com \
--cc=jroedel@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ralph.sennhauser@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=thomas.petazzoni@free-electrons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).