From: Andreas Schwab <schwab@suse.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-arm-kernel@lists.infradead.org
Subject: Re: 5.2: arm-smmu e0600000.smmu: Unexpected global fault, this could be serious
Date: Tue, 06 Aug 2019 14:33:22 +0200 [thread overview]
Message-ID: <mvmh86u323x.fsf@suse.de> (raw)
In-Reply-To: <5036fcb8-131e-9ffe-4bfe-dc8cbae71bc4@arm.com> (Robin Murphy's message of "Tue, 6 Aug 2019 13:17:12 +0100")
On Aug 06 2019, Robin Murphy <robin.murphy@arm.com> wrote:
> I take it you have firmware still using the old "mmu-masters" DT binding
> on that machine?
Yes.
> The way the legacy binding is handled turns out to interact badly with the
> disable_bypass option, so CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT is
> presumably now tripping you up. The immediate workaround would be to turn
> that off and/or boot with "arm-smmu.disable_bypass=0" to ensure it's
> overridden.
I will try the command line parameter.
> If you can update the firmware to something newer using either
> the generic "iommus" binding or ACPI (I believe Seattle is supported in
> EDK2 these days) that would remove the problem entirely.
AMD won't be releasing any new firmware for their seattle platform.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-06 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 11:28 5.2: arm-smmu e0600000.smmu: Unexpected global fault, this could be serious Andreas Schwab
2019-08-06 12:17 ` Robin Murphy
2019-08-06 12:33 ` Andreas Schwab [this message]
2019-08-07 11:49 ` Andreas Schwab
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=mvmh86u323x.fsf@suse.de \
--to=schwab@suse.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.