From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Gregory CLEMENT <gregory.clement@free-electrons.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Jason Cooper <jason@lakedaemon.net>, Andrew Lunn <andrew@lunn.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Boris BREZILLON <boris.brezillon@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v4 1/2] ARM: dma-mapping: Don't use outer_flush_range when the L2C is coherent
Date: Tue, 29 Sep 2015 19:55:14 +0200 [thread overview]
Message-ID: <20150929195514.277efd80@free-electrons.com> (raw)
In-Reply-To: <20150929174835.GO21513@n2100.arm.linux.org.uk>
Hello,
On Tue, 29 Sep 2015 18:48:35 +0100, Russell King - ARM Linux wrote:
> > It might very well be the case. If there's enough PCIe traffic and a
> > PL310 cache maintenance operation happening at the same time, the
> > system will lockup. I'm a bit surprised that just the initialization of
> > the PCIe card generates enough traffic to trigger the deadlock, but
> > maybe I'm underestimating the problem.
>
> It isn't every boot - the board has booted around 240 kernels so far and
> maybe 5% of them have needed the reset button pressed because of this.
> It only happens when I have the SATA card connected. I don't have any
> drives on the SATA card at the moment though.
Hum, ok. Then I'm not sure it's the same problem. I believe it's
unlikely that the few PCIe accesses used just to enumerate the PCIe
device and initialize it are enough to cause the deadlock. But I don't
have (and anyway wouldn't fully understand) all the details about this
issue, so I can't say for sure.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-29 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1443545458-14807-1-git-send-email-gregory.clement@free-electrons.com>
2015-09-29 16:50 ` [PATCH v4 1/2] ARM: dma-mapping: Don't use outer_flush_range when the L2C is coherent Gregory CLEMENT
2015-09-29 17:10 ` Russell King - ARM Linux
2015-09-29 17:30 ` Thomas Petazzoni
2015-09-29 17:48 ` Russell King - ARM Linux
2015-09-29 17:55 ` Thomas Petazzoni [this message]
2015-09-30 9:28 ` Gregory CLEMENT
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=20150929195514.277efd80@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=catalin.marinas@arm.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=nadavh@marvell.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=stable@vger.kernel.org \
--cc=tawfik@marvell.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).