Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Mon, 27 Aug 2018 14:32:37 -0700 (PDT)
Subject:     Re: Linux 4.19-rc1
In-Reply-To: <20180827134459.GA16094@roeck-us.net>
CC:     Linus Torvalds <torvalds@linux-foundation.org>,
        linux-kernel@vger.kernel.org
From:   Palmer Dabbelt <palmer@sifive.com>
To:     linux@roeck-us.net
Message-ID: <mhng-e4120cac-c7ab-4244-a565-805892fad85c@palmer-si-x1c4>
Mime-Version: 1.0 (MHng)
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, 27 Aug 2018 06:44:59 PDT (-0700), linux@roeck-us.net wrote:
> 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.

Thanks for the patch (as well as running the build farm)!  It should be in the 
PR I submit today, assuming I can get through my email...

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