linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: Boot failures in -next on Jetson TK1
Date: Tue, 29 May 2018 17:01:13 +0200	[thread overview]
Message-ID: <20180529150113.GA16038@ulmo> (raw)
In-Reply-To: <20180526103629.GB1564@sirena.org.uk>

On Sat, May 26, 2018 at 11:36:29AM +0100, Mark Brown wrote:
> Currently -next is failing to boot on Jetson TK1.  The problem looks to
> be the Nouveau driver, during initialization it reports an address
> decode error then starts printing error messages saying "nouveau
> 57000000.gpu: fifo: SCHED_ERROR 20 []" over and over again.
> 
> I've pasted the start of the errors below, you can see a full log and
> more details at:
> 
>    https://kernelci.org/boot/id/5b0882a259b514339779a881/
> 
> The warnings about Spectre are a separate issue and don't seem to affect
> the boot.
> 
> [ 15.194484] nouveau 57000000.gpu: NVIDIA GK20A (0ea000a1)
> [   15.200109] udevd[109]: could not rename interface '3' from 'eth0' to 'enp1s0': Device or resource busy
> [   15.206399] nouveau 57000000.gpu: imem: using IOMMU
> [   15.315122] CPU2: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
> [   15.320021] nouveau 57000000.gpu: Direct firmware load for nvidia/gk20a/fecs_inst.bin failed with error -2
> [   15.384841] nouveau 57000000.gpu: Direct firmware load for nouveau/nvea_fuc409c failed with error -2
> [   15.393972] nouveau 57000000.gpu: Direct firmware load for nouveau/fuc409c failed with error -2
> [   15.402679] nouveau 57000000.gpu: gr: failed to load fuc409c
> [   15.409434] CPU1: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
> [   15.419398] CPU1: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
> [   15.482568] tegra-mc 70019000.memory-controller: gpusrd: read @0x00041200: EMEM address decode error (EMEM decode error)
> [   15.491232] [TTM] Zone  kernel: Available graphics memory: 375202 kiB
> [   15.502768] [TTM] Zone highmem: Available graphics memory: 1030050 kiB
> [   15.509290] [TTM] Initializing pool allocator
> [   15.513658] nouveau 57000000.gpu: DRM: VRAM: 0 MiB
> [   15.518451] nouveau 57000000.gpu: DRM: GART: 1048576 MiB
> [   15.526546] CPU1: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
> [   15.527290] tegra-mc 70019000.memory-controller: gpusrd: read @0x00072000: EMEM address decode error (EMEM decode error)
> [   15.537050] CPU1: Spectre v2: firmware did not set auxiliary control register IBE bit, system vulnerable
> [   15.546928] nouveau 57000000.gpu: fifo: SCHED_ERROR 20 []

This is a known issue that was introduced in v4.16 by a combination of
the 32-bit ARM DMA/IOMMU glue and an Tegra SMMU driver change.

There is a fix here:

	http://patchwork.ozlabs.org/patch/902830/

Which got remotely NAK'ed by the DMA API maintainer. I then came up with
this, based on feedback from Christoph:

	http://patchwork.ozlabs.org/project/linux-tegra/list/?series=40853

But that's kind of blocked right now, awaiting feedback. I'll send out
another version, which will hopefully strike the right balance.

Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180529/1f1a3b2f/attachment-0001.sig>

      reply	other threads:[~2018-05-29 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 10:36 Boot failures in -next on Jetson TK1 Mark Brown
2018-05-29 15:01 ` Thierry Reding [this message]

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=20180529150113.GA16038@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).