From: Mark Brown <broonie@kernel.org>
To: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Josh Snyder <josh@code406.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the tip-fixes tree
Date: Wed, 8 Apr 2026 13:44:08 +0100 [thread overview]
Message-ID: <adZNmIpSOkd6P5c7@sirena.org.uk> (raw)
Hi all,
After merging the tip-fixes tree, today's linux-next build (arm64 kunit)
failed like this:
[12:34:18] Configuring KUnit Kernel ...
[12:34:18] Building KUnit Kernel ...
Populating config with:
$ make ARCH=arm64 O=/tmp/next/arm64_kunit olddefconfig CROSS_COMPILE=aarch64-linux-gnu-
Building with:
$ make all compile_commands.json scripts_gdb ARCH=arm64 O=/tmp/next/arm64_kunit --jobs=192 CROSS_COMPILE=aarch64-linux-gnu-
[12:34:34] Starting KUnit Kernel (1/1)...
Running tests with:
$ qemu-system-aarch64 -nodefaults -m 1024 -kernel /tmp/next/arm64_kunit/arch/arm64/boot/Image.gz -append 'kunit.enable=1 console=ttyAMA0 kunit_shutdown=reboot' -no-reboot -nographic -accel kvm -accel hvf -accel tcg -serial stdio -machine virt -cpu max
Command '['qemu-system-aarch64', '-nodefaults', '-m', '1024', '-kernel', '/tmp/next/arm64_kunit/arch/arm64/boot/Image.gz', '-append', 'kunit.enable=1 console=ttyAMA0 kunit_shutdown=reboot', '-no-reboot', '-nographic', '-accel', 'kvm', '-accel', 'hvf', '-accel', 'tcg', '-serial', 'stdio', '-machine', 'virt', '-cpu', 'max']' timed out after 300 seconds
[12:39:34] [FAILED] <missing>
[12:39:34] Testing complete. Ran 0 tests: errors: 1
[12:39:34] Test results stored in /tmp/next/arm64_kunit.json
[12:39:34] Elapsed time: 316.083s total, 0.002s configuring, 16.074s building, 300.006s running
which isn't super helpful. I haven't isolated which commit but it'll be
one of the three:
b81207470caf ("clockevents: Prevent timer interrupt starvation")
82b915051d32 ("tick/nohz: Fix inverted return value in check_tick_dependency() fast path")
105c42566a55 ("ata: ahci: force 32-bit DMA for JMicron JMB582/JMB585")
which are new since yesterday, I'm guessing not the latter. I have used
the tree from next-20260407 instead.
next reply other threads:[~2026-04-08 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 12:44 Mark Brown [this message]
2026-04-08 14:50 ` linux-next: build failure after merge of the tip-fixes tree Mark Brown
2026-04-08 14:54 ` Thomas Weißschuh
2026-04-08 15:21 ` Thomas Gleixner
2026-04-08 15:45 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 23:38 Stephen Rothwell
2025-03-26 1:12 ` Josh Poimboeuf
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=adZNmIpSOkd6P5c7@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hpa@zytor.com \
--cc=josh@code406.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@kernel.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