From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 4.19-rc1
Date: Mon, 27 Aug 2018 06:44:59 -0700 [thread overview]
Message-ID: <20180827134459.GA16094@roeck-us.net> (raw)
In-Reply-To: <CA+55aFw9mxNPX6OtOp-aoUMdXSg=gBkQudGGamo__sh_ts_LdQ@mail.gmail.com>
On Sun, Aug 26, 2018 at 02:49:14PM -0700, Linus Torvalds wrote:
> So two weeks have passed, and the merge window for 4.19 is over.
>
[ ... ]
>
> Anyway, go forth and test,
>
Build results:
total: 132 pass: 129 fail: 3
Failed builds:
riscv:defconfig
riscv:allnoconfig
sparc32:allmodconfig
Qemu test results:
total: 299 pass: 297 fail: 2
Failed tests:
riscv:virt:defconfig:initrd
riscv:virt:defconfig:virtio-blk:rootfs
---
riscv:
In file included from arch/riscv/include/asm/tlb.h:17:0,
from arch/riscv/include/asm/pgalloc.h:19,
from arch/riscv/mm/fault.c:30:
include/asm-generic/tlb.h: In function 'tlb_flush_mmu_tlbonly':
include/asm-generic/tlb.h:147:2: error: implicit declaration of function 'tlb_flush'
Known problem, patch submitted.
---
sparc32:allmodconfig:
arch/sparc/kernel/head_32.o: In function `current_pc':
arch/sparc/kernel/.tmp_head_32.o:(.head.text+0x5040): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/head_32.o: In function `halt_notsup':
arch/sparc/kernel/.tmp_head_32.o:(.head.text+0x5100): relocation truncated to fit: R_SPARC_WDISP22 against `.init.text'
arch/sparc/kernel/head_32.o: In function `leon_init':
arch/sparc/kernel/.tmp_head_32.o:(.init.text+0xa4): relocation truncated to fit: R_SPARC_WDISP22 against symbol `leon_smp_cpu_startup' defined in .text section
in arch/sparc/kernel/trampoline_32.o
arch/sparc/kernel/process_32.o:(.fixup+0x4): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/process_32.o:(.fixup+0xc): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x0): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x8): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x10): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x18): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x20): relocation truncated to fit: R_SPARC_WDISP22 against `.text'
arch/sparc/kernel/signal_32.o:(.fixup+0x28): additional relocation overflows omitted from the output
For the most part this is due to calls / short jumps between .head.text,
.text, and .init.text. Probably old, now seen because the image is now
too large.
---
On top of that, there are various runtime warnings.
sh:
WARNING: CPU: 0 PID: 932 at mm/slab.c:2666 cache_alloc_refill+0x8a/0x594
Known problem. Fix was under discussion. I don't know if it was accepted.
https://marc.info/?t=153301426900002&r=1&w=2
https://www.spinics.net/lists/linux-sh/msg53298.html
---
sparc:
WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 esp_sbus_probe+0x408/0x6e8
WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 sparc_lance_probe_one+0x428/0x4f
Missing initialization of coherent_dma_mask in the respective drivers.
---
Each platform driver instantiated through a devicetree node now generates
the following warning:
esp ffd38e00: DMA mask not set
It isn't a traceback so it may fly under the radar. There is nothing the
drivers can do about it; the message is generated by the core before the
driver probe function is called. No idea what a correct fix might be.
Guenter
next prev parent reply other threads:[~2018-08-27 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-26 21:49 Linux 4.19-rc1 Linus Torvalds
2018-08-27 1:39 ` linux-next: stats (Was: Linux 4.19-rc1) Stephen Rothwell
2018-08-27 13:44 ` Guenter Roeck [this message]
2018-08-27 15:46 ` Linux 4.19-rc1 Christoph Hellwig
2018-08-27 17:11 ` Guenter Roeck
2018-08-27 18:13 ` Christoph Hellwig
2018-08-27 19:32 ` Guenter Roeck
2018-08-27 21:32 ` Palmer Dabbelt
2018-08-27 21:56 ` Linus Torvalds
2018-08-28 16:01 ` Guenter Roeck
2018-08-27 19:10 ` Shuah Khan
2018-08-27 20:25 ` Winkler, Tomas
2018-08-29 9:56 ` David Laight
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=20180827134459.GA16094@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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