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 6.8-rc5
Date: Tue, 20 Feb 2024 11:08:59 -0800 [thread overview]
Message-ID: <538327ff-8d34-41d5-a9ae-1a334744f5ae@roeck-us.net> (raw)
In-Reply-To: <CAHk-=wi8vZD7EXZfob-yhfDERyfzWxzMOzG9FsOuaKU-v6+PHA@mail.gmail.com>
On Sun, Feb 18, 2024 at 01:13:34PM -0800, Linus Torvalds wrote:
[ ... ]
>
> Please commence testing,
>
Build results:
total: 155 pass: 151 fail: 4
Failed builds:
csky:allmodconfig
openrisc:allmodconfig
parisc:allmodconfig
xtensa:allmodconfig
Qemu test results:
total: 549 pass: 547 fail: 2
Unit test results:
pass: 161596 fail: 740
============
Build errors
Building csky:allmodconfig ... failed
Building openrisc:allmodconfig ... failed
Building parisc:allmodconfig ... failed
Building xtensa:allmodconfig ... failed
--------------
Error log:
ERROR: modpost: "__umoddi3" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
ERROR: modpost: "__moddi3" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
Commit a64056bb5a32 ("drm/tests/drm_buddy: add alloc_contiguous test"):
+ u64 mm_size, ps = SZ_4K, i, n_pages, total;
...
+ n_pages = mm_size / ps;
This patch breaks the build on all 32-bit systems since it introduces an
unhandled direct 64-bit divide operation.
Runtime crashes
===============
Nothing new, so shortened.
an385:mps2_defconfig:mps2-an385:initrd
xtensa:de212:kc705-nommu:nommu_kc705_defconfig
Warning backtraces
==================
WARNING: inconsistent lock state
6.8.0-rc4 #1 Tainted: G N
--------------------------------
inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage.
kworker/0:2/39 [HC1[1]:SC0[2]:HE0:SE0] takes:
ef792074 (&syncp->seq#2){?...}-{0:0}, at: sun8i_dwmac_dma_interrupt+0x9c/0x28c
{HARDIRQ-ON-W} state was registered at:
lock_acquire+0x11c/0x368
__u64_stats_update_begin+0x104/0x1ac
stmmac_xmit+0x4d0/0xc58
dev_hard_start_xmit+0xc4/0x2a0
sch_direct_xmit+0xf8/0x30c
__dev_queue_xmit+0x400/0xcc4
ip6_finish_output2+0x254/0xafc
mld_sendpack+0x260/0x5b0
mld_ifc_work+0x274/0x588
process_one_work+0x230/0x604
worker_thread+0x1dc/0x494
kthread+0x100/0x120
ret_from_fork+0x14/0x28
Caused by commit 38cc3c6dcc09 ("net: stmmac: protect updates of 64-bit
statistics counters.")
Report:
https://lore.kernel.org/lkml/ea1567d9-ce66-45e6-8168-ac40a47d1821@roeck-us.net/
Unit test failures
==================
Previously reported:
checksum (various architectures)
cpumask (parisc only)
stackinit (m68k only)
New (that is, newly enabled)
mean and variance tests (all architectures)
-------------------------------------------
This is bcachefs related.
test cases 2 and 4 fail on all architectures/branches, and I don't see how
those tests can pass. See report for details.
Report:
https://lore.kernel.org/lkml/065b94eb-6a24-4248-b7d7-d3212efb4787@roeck-us.net/
drm kunit tests (all architecstures, with qemu)
-----------------------------------------------
Failures all over the place when running in qemu, followed by list corruptions
and a crash. Anyone interested is invited to enable CONFIG_DRM_KUNIT_TEST,
CONFIG_DRM_TTM_KUNIT_TEST, CONFIG_DRM_XE_KUNIT_TEST, CONFIG_DRM_VC4_KUNIT_TEST
together with lockdep and list debugging, run the resulting images in qemu,
and look at the results.
Note: This is a one-time report; there are two many issues to list here.
I reported a recently introduced problem at
https://lore.kernel.org/lkml/a45b796d-5e04-4eac-b5ba-ea6bb3b6131b@roeck-us.net/
and tried to analyze further, but there are just too many issues and I gave up.
next prev parent reply other threads:[~2024-02-20 19:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 21:13 Linus Torvalds
2024-02-19 8:07 ` Build regressions/improvements in v6.8-rc5 Geert Uytterhoeven
2024-02-19 9:54 ` Geert Uytterhoeven
2024-02-19 8:12 ` Geert Uytterhoeven
2024-02-20 19:08 ` Guenter Roeck [this message]
2024-02-20 19:57 ` Linux 6.8-rc5 Linus Torvalds
2024-02-20 20:16 ` Linus Torvalds
2024-02-20 23:07 ` Shuah Khan
2024-02-20 20:37 ` Linus Torvalds
2024-02-20 20:51 ` Geert Uytterhoeven
2024-02-20 21:48 ` Guenter Roeck
2024-02-20 22:02 ` Linus Torvalds
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=538327ff-8d34-41d5-a9ae-1a334744f5ae@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
all inboxes | Powered by JetHome®