dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ben Skeggs <bskeggs@redhat.com>, David Airlie <airlied@linux.ie>
Cc: Stephen Warren <swarren@nvidia.com>,
	kernel-build-reports@lists.linaro.org, khilman@baylibre.com,
	dri-devel@lists.freedesktop.org,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Thierry Reding <thierry.reding@gmail.com>,
	nouveau@lists.freedesktop.org, linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Boot failures in -next on Jetson TK1
Date: Sat, 26 May 2018 11:36:29 +0100	[thread overview]
Message-ID: <20180526103629.GB1564@sirena.org.uk> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2253 bytes --]

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 []

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2018-05-26 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-26 10:36 Mark Brown [this message]
     [not found] ` <20180526103629.GB1564-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-05-29 15:01   ` Boot failures in -next on Jetson TK1 Thierry Reding

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=20180526103629.GB1564@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=airlied@linux.ie \
    --cc=bskeggs@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jonathanh@nvidia.com \
    --cc=kernel-build-reports@lists.linaro.org \
    --cc=khilman@baylibre.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=swarren@nvidia.com \
    --cc=thierry.reding@gmail.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 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).