From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Guenter Roeck <linux@roeck-us.net>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Tzung-Bi Shih <tzungbi@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-next:master 10251/12094] drivers/hwmon/cros_ec_hwmon.o: error: objtool: cros_ec_hwmon_read+0x6c: can't find jump dest instruction at .text+0xd2d
Date: Sat, 7 Feb 2026 11:56:46 +0100 [thread overview]
Message-ID: <4db66fc2-dc8a-4499-bc9d-c1f85e2ba4c1@t-8ch.de> (raw)
In-Reply-To: <202602071311.Q6tATiyh-lkp@intel.com>
On 2026-02-07 13:14:53+0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 9845cf73f7db6094c0d8419d6adb848028f4a921
> commit: 165c14597d53cfa7bc97b4ff8bc85f7bd98262b7 [10251/12094] hwmon: (cros_ec) Add support for temperature thresholds
> config: x86_64-randconfig-071-20260207 (https://download.01.org/0day-ci/archive/20260207/202602071311.Q6tATiyh-lkp@intel.com/config)
> compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260207/202602071311.Q6tATiyh-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202602071311.Q6tATiyh-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> drivers/hwmon/cros_ec_hwmon.o: error: objtool: cros_ec_hwmon_read+0x6c: can't find jump dest instruction at .text+0xd2d
This is due to the call to unreachable() in cros_ec_hwmon_attr_to_thres().
Replacing it with BUG() avoids the issue.
Guenter, do you want to drop the patches for now and I'll resend them
next cycle? I can also send an incremental patch. Or you just fix it up
in your branch.
Thomas
next parent reply other threads:[~2026-02-07 10:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202602071311.Q6tATiyh-lkp@intel.com>
2026-02-07 10:56 ` Thomas Weißschuh [this message]
2026-02-07 15:07 ` Guenter Roeck
2026-02-07 15:33 ` Thomas Weißschuh
2026-02-07 16:26 ` Guenter Roeck
2026-02-07 16:43 ` Thomas Weißschuh
2026-02-07 17:34 ` Guenter Roeck
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=4db66fc2-dc8a-4499-bc9d-c1f85e2ba4c1@t-8ch.de \
--to=linux@weissschuh.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tzungbi@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
all inboxes | Powered by JetHome®