From: bugzilla-daemon@kernel.org
To: linux-pm@vger.kernel.org
Subject: [Bug 219051] amd_pstate=active reset computer
Date: Tue, 23 Jul 2024 07:04:43 +0000 [thread overview]
Message-ID: <bug-219051-137361-6ZKMPSR2Q6@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219051-137361@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219051
Perry Yuan(AMD) (Perry.Yuan@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Perry.Yuan@amd.com
--- Comment #6 from Perry Yuan(AMD) (Perry.Yuan@amd.com) ---
Mario is OOO lately,
[ 864.970948] asus_wmi: fan_curve_get_factory_default (0x00110024) failed: -61
[ 864.972365] asus_wmi: fan_curve_get_factory_default (0x00110025) failed: -61
[ 864.973533] asus_wmi: fan_curve_get_factory_default (0x00110032) failed: -19
The errors show the BIOS broken to get factory default fan curve data.
I would like sugguest to submit support case to ASUS for further help.
The system reset is triggered when system reach critical temperature.
"I noticed that the processor runs at lower frequencies than 20.04, so do the
fans, most of the time at 0 rpm. Temps 50-70 degrees."
Like you said, the frequencies are lower than 20.04 which have no amd-pstate
driver loaded, so the system temperature increasing slower than 24.04 kernel
which has amd-pstate-epp driver loaded.
I would guess the root cause is system fan error instead of amd-pstate driver.
After you resolve the Fan issue, system will not reset any more.
static int fan_curve_get_factory_default(struct asus_wmi *asus, u32 fan_dev)
{
struct fan_curve_data *curves;
u8 buf[FAN_CURVE_BUF_LEN];
int err, fan_idx;
u8 mode = 0;
if (asus->throttle_thermal_policy_available)
mode = asus->throttle_thermal_policy_mode;
/* DEVID_<C/G>PU_FAN_CURVE is switched for OVERBOOST vs SILENT */
if (mode == 2)
mode = 1;
else if (mode == 1)
mode = 2;
// asus_wmi_evaluate_method_buf failed here, it is a broken bios issue.
err = asus_wmi_evaluate_method_buf(asus->dsts_id, fan_dev, mode, buf,
FAN_CURVE_BUF_LEN);
if (err) {
pr_warn("%s (0x%08x) failed: %d\n", __func__, fan_dev, err);
return err;
}
.....
}
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2024-07-23 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 12:52 [Bug 219051] New: amd_pstate=active reset computer bugzilla-daemon
2024-07-17 17:17 ` [Bug 219051] " bugzilla-daemon
2024-07-17 17:29 ` bugzilla-daemon
2024-07-17 17:49 ` bugzilla-daemon
2024-07-17 19:22 ` bugzilla-daemon
2024-07-19 11:16 ` bugzilla-daemon
2024-07-23 7:04 ` bugzilla-daemon [this message]
2024-07-23 12:10 ` bugzilla-daemon
2024-07-24 3:01 ` bugzilla-daemon
2024-07-25 14:51 ` bugzilla-daemon
2024-07-25 14:52 ` 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-219051-137361-6ZKMPSR2Q6@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-pm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).