From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Christoph Hellwig <hch@lst.de>,
Krzysztof Kozlowski <krzk@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefan Agner <stefan@agner.ch>, Fugang Duan <fugang.duan@nxp.com>
Subject: Re: [BUG BISECT] Ethernet fail on VF50 (OF: Don't set default coherent DMA mask)
Date: Mon, 30 Jul 2018 11:23:06 +0200 [thread overview]
Message-ID: <20180730092306.GA18701@lst.de> (raw)
In-Reply-To: <20180728165820.GA5731@roeck-us.net>
On Sat, Jul 28, 2018 at 09:58:20AM -0700, Guenter Roeck wrote:
> I would call it a serious regression. Also, no longer setting a default
> coherent DMA mask is a quite substantial behavioral change, especially
> if and since the code worked just fine up to now.
>
> Crash when booting sam460ex attached below, as is a bisect log.
Things should be ok again with:
commit a5516219b10218a87abb3352c82248ce3088e94a
Author: Robin Murphy <robin.murphy@arm.com>
Date: Fri Jul 27 15:14:15 2018 +0100
of/platform: Initialise default DMA masks
from the lastest dma-mapping tree as of Friday. It isn't in the
latest linux-next tree yet but be in the next one.
next prev parent reply other threads:[~2018-07-30 9:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-27 13:11 [BUG BISECT] Ethernet fail on VF50 (OF: Don't set default coherent DMA mask) Krzysztof Kozlowski
2018-07-27 13:18 ` Krzysztof Kozlowski
2018-07-27 14:04 ` Christoph Hellwig
2018-07-28 16:58 ` Guenter Roeck
2018-07-30 9:23 ` Christoph Hellwig [this message]
2018-07-30 14:38 ` Robin Murphy
2018-07-31 0:50 ` Guenter Roeck
2018-07-31 8:19 ` Stefan Agner
2018-07-31 12:32 ` Robin Murphy
2018-07-31 13:26 ` Guenter Roeck
2018-07-31 14:09 ` Robin Murphy
2018-07-31 15:43 ` Guenter Roeck
2018-07-31 15:58 ` Robin Murphy
2018-07-31 17:38 ` Guenter Roeck
2018-08-01 16:33 ` Robin Murphy
2018-08-01 18:23 ` Guenter Roeck
2018-07-31 15:53 ` Stefan Agner
2018-07-31 16:29 ` Robin Murphy
2018-07-31 19:02 ` Stefan Agner
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=20180730092306.GA18701@lst.de \
--to=hch@lst.de \
--cc=ard.biesheuvel@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=stefan@agner.ch \
/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).