* Thierry Reding <thierry.reding@xxxxxxxxx> [2017-01-02 17:08]: > Martin, one thing to check might be if your .config enables the > TEGRA_IOMMU_SMMU option. Yes, it's built-in. I disabled TEGRA_IOMMU_SMMU (but left TEGRA_MC=y) and now I get: [ 6.556591] tegra-mc 70019000.memory-controller: gpusrd: read @0x0000000000000000: EMEM address decode error (EMEM decode error) [ 6.568158] tegra-mc 70019000.memory-controller: gpusrd: read @0x0000000000000000: Page fault (EMEM decode error) Ok, this is interesting. With both TEGRA_MC and TEGRA_IOMMU_SMMU disabled, the boot process hangs. Unfortunately I don't have time to investigate more right now. > Perhaps you can also regenerate a log with drm.debug=0x3f on the > kernel command-line. Maybe throw in a NOUVEAU_DEBUG_DEFAULT=5 in > .config to make sure Nouveau gives us as much info as possible (=7 > should give more, but it might be a little overkill). Maybe I made a mistake, but I didn't get any more verbose logs with drm.debug=0x3f and NOUVEAU_DEBUG_DEFAULT=5. Let me know if you can reproduce the (original) problem. -- Martin Michlmayr http://www.cyrius.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
