From: Mark Brown <broonie@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Ben Skeggs <bskeggs@redhat.com>
Cc: linux-tegra@vger.kernel.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129)
Date: Thu, 29 Nov 2018 11:44:13 +0000 [thread overview]
Message-ID: <20181129114413.GC10570@sirena.org.uk> (raw)
In-Reply-To: <5bffcc4f.1c69fb81.ee2e8.b541@mx.google.com>
[-- Attachment #1.1: Type: text/plain, Size: 990 bytes --]
On Thu, Nov 29, 2018 at 03:23:59AM -0800, kernelci.org bot wrote:
Today's -next crashes on Jetson TK1 when the Nouveau module is loaded if
it can't find firmware:
[ 7.617291] nouveau 57000000.gpu: Linked as a consumer to regulator.33
[ 7.624037] nouveau 57000000.gpu: NVIDIA GK20A (0ea000a1)
[ 7.629880] nouveau 57000000.gpu: imem: using IOMMU
[ 7.635013] nouveau 57000000.gpu: Direct firmware load for nvidia/gk20a/fecs_inst.bin failed with error -2
[ 7.644726] nouveau 57000000.gpu: Direct firmware load for nouveau/nvea_fuc409c failed with error -2
[ 7.653960] nouveau 57000000.gpu: Direct firmware load for nouveau/fuc409c failed with error -2
[ 7.662916] nouveau 57000000.gpu: gr: failed to load fuc409c
[ 7.669694] Unable to handle kernel NULL pointer dereference at virtual address 0000006c
This has been there for ~30 days but obscured by other issues. Full
log and other info can be found at:
https://kernelci.org/boot/id/5bffa74b59b5148342fddd64/
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next parent reply other threads:[~2018-11-29 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5bffcc4f.1c69fb81.ee2e8.b541@mx.google.com>
2018-11-29 11:44 ` Mark Brown [this message]
[not found] ` <20181129114413.GC10570-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2018-11-29 11:54 ` next/master boot: 142 boots: 2 failed, 130 passed with 7 offline, 3 conflicts (next-20181129) Thierry Reding
2018-11-29 11:57 ` Mark Brown
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=20181129114413.GC10570@sirena.org.uk \
--to=broonie@kernel.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jonathanh@nvidia.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--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