LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: Linux 4.19-rc2
Date: Mon, 3 Sep 2018 11:22:02 -0700 [thread overview]
Message-ID: <20180903182202.GA14258@roeck-us.net> (raw)
In-Reply-To: <CA+55aFyG0GbDfoghEhAmKBPcZCiPu6CCpPRz9GwjCzLuP_Vv5Q@mail.gmail.com>
On Sun, Sep 02, 2018 at 02:45:22PM -0700, Linus Torvalds wrote:
> As usual, the rc2 release is pretty small. People are taking a
> breather after the merge window, and it takes a bit of time for bug
> reports to start coming in and get identified. Plus people were
> probably still on vacation (particularly Europe), and some people were
> at Open Source Summit NA last week too. Having a calm week was good.
>
> Regardless of the reason, it's pretty quiet/ The bulk of it is drivers
> (network and gpu stand out), with the rest being a random collection
> all over (arch/x86 and generic networking stands out, but there's misc
> stuff all over).
>
> Go out and test.
>
Build results:
total: 134 pass: 133 fail: 1
Failed builds:
sparc32:allmodconfig
Qemu test results:
total: 302 pass: 301 fail: 1
Failed tests:
riscv:virt:defconfig:initrd
The sparc32:allmodconfig build problem is the same as last week.
David - any interest/plan to get this fixed, or should I just drop
the build ?
The riscv:virt:defconfig:initrd boot test is known to fail. The patch
fixing it is in -next.
---
Runtime warnings:
arm:
WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 drm_gem_cma_create+0x13c/0x158
This is seen now due to a newly enabled configuration option.
Fix is in -next.
---
sh4:
WARNING: CPU: 0 PID: 932 at mm/slab.c:2666 cache_alloc_refill+0x8a/0x594
Same as before. I'll try to dig up the patch and ask for the status.
---
sparc32:
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/0x4f4
Fix is in -next.
Detailed logs are available at https://kerneltests.org/builders/.
Guenter
next prev parent reply other threads:[~2018-09-03 18:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 21:45 Linux 4.19-rc2 Linus Torvalds
2018-09-03 18:22 ` Guenter Roeck [this message]
2018-09-03 19:09 ` David Miller
2018-09-03 19:36 ` Guenter Roeck
2018-09-11 7:53 ` [REGRESSION 4.19-rc2] sometimes hangs with black screen when resuming from suspend or hibernation (was: Re: Linux 4.19-rc2) Martin Steigerwald
2018-09-11 8:17 ` Rafael J. Wysocki
2018-09-11 10:17 ` Martin Steigerwald
2018-09-12 17:10 ` [Intel-gfx] " Ville Syrjälä
2018-09-12 21:03 ` Martin Steigerwald
2018-10-26 15:43 ` Martin Steigerwald
2018-10-30 6:41 ` Rafael J. Wysocki
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=20180903182202.GA14258@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davem@davemloft.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;
as well as URLs for NNTP newsgroup(s).