From: Peter Zijlstra <peterz@infradead.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Build breakage caused by the use of UDB
Date: Wed, 17 Dec 2025 13:35:36 +0100 [thread overview]
Message-ID: <20251217123536.GE3707891@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20251217124119.5832bba7@endymion>
On Wed, Dec 17, 2025 at 12:44:23PM +0100, Jean Delvare wrote:
> Hi Peter,
>
> Kernel v6.18.1 doesn't build on x86_64 for me. The build failure is:
>
> make[1]: Entering directory '/home/khali/src/linux-6.18/drivers/net/wireless/realtek/rtlwifi/rtl8192c'
> CC [M] main.o
> CC [M] dm_common.o
> CC [M] fw_common.o
> CC [M] phy_common.o
> CHECK main.c
> fw_common.c: Assembler messages:
> fw_common.c:416: Error: unknown pseudo-op: `.byte0x0f'
> fw_common.c:391: Error: unknown pseudo-op: `.byte0x0f'
> make[3]: *** [/home/khali/src/linux-6.18/scripts/Makefile.build:287: fw_common.o] Error 1
> make[3]: *** Waiting for unfinished jobs....
> CHECK dm_common.c
> phy_common.c: Assembler messages:
> phy_common.c:58: Error: unknown pseudo-op: `.byte0x0f'
> phy_common.c:67: Error: unknown pseudo-op: `.byte0x0f'
> ../wifi.h:3033: Error: unknown pseudo-op: `.byte0x0f'
> ../wifi.h:3033: Error: unknown pseudo-op: `.byte0x0f'
> phy_common.c:807: Error: unknown pseudo-op: `.byte0x0f'
> phy_common.c:714: Error: unknown pseudo-op: `.byte0x0f'
> make[3]: *** [/home/khali/src/linux-6.18/scripts/Makefile.build:287: phy_common.o] Error 1
> make[2]: *** [/home/khali/src/linux-6.18/Makefile:2010: .] Error 2
> make[1]: *** [/home/khali/src/linux-6.18/Makefile:248: __sub-make] Error 2
> make[1]: Leaving directory '/home/khali/src/linux-6.18/drivers/net/wireless/realtek/rtlwifi/rtl8192c'
> make: *** [Makefile:248: __sub-make] Error 2
>
> I bisected it down to:
>
> commit 85a2d4a890dce3cfc9c14aa91afc3dd7af8e3bf5
> Author: Peter Zijlstra
> Date: Mon Sep 1 12:49:58 2025 +0200
>
> x86,ibt: Use UDB instead of 0xEA
>
> Reverting this commit allows me to build v6.18.1.
>
> I must confess this is all way beyond me and I have no idea how this
> change can cause such a build failure, but it does. If it matters, my
> compiler is gcc 8.2.1.
Well, that is somewhat unexpected. None of the build robots fingered
this. Is there a particular .config I should try?
I don't seem to have 8.2.1 at hand, but I'll try with 8.3.0.
next prev parent reply other threads:[~2025-12-17 12:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 11:44 Build breakage caused by the use of UDB Jean Delvare
2025-12-17 12:35 ` Peter Zijlstra [this message]
2025-12-17 12:47 ` Peter Zijlstra
2025-12-17 13:02 ` Peter Zijlstra
2025-12-17 13:34 ` Peter Zijlstra
2025-12-17 14:39 ` Uros Bizjak
2025-12-18 8:54 ` Peter Zijlstra
2025-12-18 10:26 ` Uros Bizjak
2025-12-18 10:38 ` Peter Zijlstra
2025-12-18 10:46 ` Peter Zijlstra
2025-12-18 11:03 ` [tip: x86/urgent] x86/bug: Fix old GCC compile fails tip-bot2 for Peter Zijlstra
2025-12-18 12:38 ` Build breakage caused by the use of UDB Brian Gerst
2025-12-17 13:10 ` Jean Delvare
2025-12-17 13:22 ` Peter Zijlstra
2025-12-17 22:07 ` Jean Delvare
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=20251217123536.GE3707891@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=jdelvare@suse.de \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.