From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221441] asus-wmi/asus-armoury warnings on ASUS FX608LP: no matching power limits, fan_curve_get_factory_default failed
Date: Thu, 30 Apr 2026 11:30:10 +0000 [thread overview]
Message-ID: <bug-221441-215701-ViFxfoge4U@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221441-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221441
--- Comment #1 from fxzxaxon@outlook.com ---
Additional information: I also noticed several firmware thermal zones failing
to report temperature and being disabled on the same boot.
Relevant kernel log:
thermal_sys: Registered thermal governor 'fair_share'
thermal_sys: Registered thermal governor 'bang_bang'
thermal_sys: Registered thermal governor 'step_wise'
thermal_sys: Registered thermal governor 'user_space'
thermal LNXTHERM:00: registered as thermal_zone0
ACPI: thermal: Thermal Zone [TZ00] (28 C)
thermal thermal_zone2: Temperature check failed (-5)
thermal thermal_zone4: Temperature check failed (-5)
thermal thermal_zone5: Temperature check failed (-5)
asus-nb-wmi asus-nb-wmi: Using throttle_thermal_policy for platform_profile
support
proc_thermal_pci 0000:00:04.0: enabling device (0000 -> 0002)
Consider using thermal netlink events interface
thermal thermal_zone5: Unable to get temperature, disabling!
thermal thermal_zone5: Disabled thermal zone with critical trip point
thermal thermal_zone4: Unable to get temperature, disabling!
thermal thermal_zone4: Disabled thermal zone with critical trip point
thermal thermal_zone2: Unable to get temperature, disabling!
thermal thermal_zone2: Disabled thermal zone with critical trip point
/sys/class/thermal summary:
thermal_zone2:
type: SEN2
temp: unreadable
mode: disabled
trips:
passive: -274000
passive: -274000
critical: 80050
hot: 75050
passive: 65050
active: 60050
active: 50050
active: 40050
thermal_zone3:
type: SEN3
temp: 45050
mode: enabled
trips:
passive: -274000
passive: -274000
critical: 80050
hot: 75050
passive: 65050
active: 60050
active: 50050
active: 40050
thermal_zone4:
type: SEN4
temp: unreadable
mode: disabled
trips:
passive: -274000
passive: -274000
critical: 80050
hot: 75050
passive: 65050
active: 60050
active: 50050
active: 40050
thermal_zone5:
type: SEN5
temp: unreadable
mode: disabled
trips:
passive: -274000
passive: -274000
critical: 80050
hot: 75050
passive: 65050
active: 60050
active: 50050
active: 40050
SEN3 appears to work and reports temperature, while SEN2/SEN4/SEN5 have the
same trip layout but fail to report temperature and are later disabled.
I am not sure whether this is related to the ASUS WMI / Armoury warnings, but I
am adding it here because the same boot also reports:
asus-nb-wmi asus-nb-wmi: Using throttle_thermal_policy for platform_profile
support
No clear user-visible malfunction has been observed so far.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-04-30 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 11:04 [Bug 221441] New: asus-wmi/asus-armoury warnings on ASUS FX608LP: no matching power limits, fan_curve_get_factory_default failed bugzilla-daemon
2026-04-30 11:30 ` bugzilla-daemon [this message]
2026-05-03 22:12 ` [Bug 221441] " bugzilla-daemon
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=bug-221441-215701-ViFxfoge4U@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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.