Bug 198399 - No display output on Tegra Acer Chromebook 13 starting with 4.14
Summary: No display output on Tegra Acer Chromebook 13 starting with 4.14
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: IOMMU (show other bugs)
Hardware: ARM Linux
: P1 normal
Assignee: drivers_iommu
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-08 18:05 UTC by Matías Zúñiga
Modified: 2020-11-08 02:08 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.14
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Oops with kernel 4.14.11 (5.01 KB, text/plain)
2018-01-08 18:05 UTC, Matías Zúñiga
Details
System log for a failing kernel (29.10 KB, text/plain)
2018-01-08 18:08 UTC, Matías Zúñiga
Details
System log for a working kernel (34.44 KB, text/plain)
2018-01-08 18:09 UTC, Matías Zúñiga
Details

Description Matías Zúñiga 2018-01-08 18:05:57 UTC
Created attachment 273471 [details]
Oops with kernel 4.14.11

Starting with kernel 4.14, there is no display output on the Acer Chromebook 14. I get a KERNEL BUG at exynos-iommu.c:743, exynos_iommu_domain_alloc (even though this device has a Nvidia Tegra K1)


Reverting commit 928055a01b3: "iommu/exynos: Remove custom platform device registration code" makes it work again.


I have the Oops message and system logs for a working and a failing kernel (the failing one is with kernel 4.14.10 because new versions came out while bisecting, but the bug still exists with the last version)
Comment 1 Matías Zúñiga 2018-01-08 18:08:02 UTC
Created attachment 273473 [details]
System log for a failing kernel
Comment 2 Matías Zúñiga 2018-01-08 18:09:06 UTC
Created attachment 273475 [details]
System log for a working kernel

when it works, i get lots of "iommu: Adding device *name* to group *number*"
Comment 3 NicolasChauvet 2018-08-23 09:16:38 UTC
FYI, there are few patches pending to disable arm implicit iommu conflicting with iommu handled by tegra:

https://github.com/grate-driver/linux/commit/7f0750065a31ae491278a8960c1aceb4a44b847f

(see also the others for tegra devices on the grate-driver/linux tree)

Hopefully this can be fixed by 4.20
Comment 4 Matías Zúñiga 2020-11-08 02:08:04 UTC
This has been fixed for some time (at least a year)

Note You need to log in before you can comment on or make changes to this bug.