public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David Wang" <00107082@163.com>
To: "Gautham R.Shenoy" <gautham.shenoy@amd.com>
Cc: perry.yuan@amd.com, Alexander.Deucher@amd.com, Li.Meng@amd.com,
	 Mario.Limonciello@amd.com, Xiaojian.Du@amd.com,
	Xinmei.Huang@amd.com,  linux-kernel@vger.kernel.org,
	linux-pm@vger.kernel.org,  rafael.j.wysocki@intel.com,
	viresh.kumar@linaro.org
Subject: Re: [Regression] 6.11.0-rc1: AMD CPU boot with error when CPPC feature disabled by BIOS
Date: Wed, 31 Jul 2024 20:58:40 +0800 (CST)	[thread overview]
Message-ID: <2f793cc8.a13d.19108df0a58.Coremail.00107082@163.com> (raw)
In-Reply-To: <87zfpxsweb.fsf@BLR-5CG11610CF.amd.com>

Hi,

At 2024-07-31 18:12:12, "Gautham R.Shenoy" <gautham.shenoy@amd.com> wrote:
>Hello David,
>
>David Wang <00107082@163.com> writes:
>
>> Hi,
>>
>> I notice some kernel warning and errors when I update to 6.11.0-rc1:
>>
>>  kernel: [    1.022739] amd_pstate: The CPPC feature is supported but currently disabled by the BIOS.
>>  kernel: [    1.022739] Please enable it if your BIOS has the CPPC option.
>>  kernel: [    1.098054] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.110058] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.122057] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.134062] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.134641] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.135128] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.135693] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.136371] amd_pstate: min_freq(0) or max_freq(0) or nominal_freq(0) value is incorrect
>>  kernel: [    1.136390] amd_pstate: failed to register with return -19
>>  kernel: [    1.138410] ledtrig-cpu: registered to indicate activity on CPUs
>>
>>
>> Those warning message was introduced by commit:
>>  bff7d13c190ad98cf4f877189b022c75df4cb383 ("cpufreq: amd-pstate: add debug message while CPPC is supported and disabled by SBIOS)
>> , which make sense.
>
>
>If CPPC is disabed in the BIOS, then the _CPC objects shouldn't have
>been created. And the error message that you should have seen is
>"the _CPC object is not present in SBIOS or ACPI disabled".
>
>
>Could you please share the family and model number of the platform where
>you are observing this ?

My `cat /proc/cpuinfo` shows something as following:
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 23
model		: 113
model name	: AMD Ryzen 3 3100 4-Core Processor
stepping	: 0
microcode	: 0x8701021
cpu MHz		: 3600.000
cache size	: 512 KB
physical id	: 0
siblings	: 8
core id		: 0
cpu cores	: 4
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 16
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip rdpid overflow_recov succor smca sev sev_es
bugs		: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass retbleed smt_rsb srso
bogomips	: 7199.95
TLB size	: 3072 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 43 bits physical, 48 bits virtual
power management: ts ttp tm hwpstate cpb eff_freq_ro [13] [14]




>
>--
>Thanks and Regards
>gautham.



  reply	other threads:[~2024-07-31 12:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 14:01 [Regression] 6.11.0-rc1: AMD CPU boot with error when CPPC feature disabled by BIOS David Wang
2024-07-30 17:43 ` Xiaojian Du
2024-07-31  0:25   ` David Wang
2024-07-31  3:16     ` Xiaojian Du
2024-07-31  3:39       ` David Wang
2024-07-31  4:21         ` Xiaojian Du
2024-07-31  4:33           ` David Wang
2024-07-31 10:12 ` Gautham R.Shenoy
2024-07-31 12:58   ` David Wang [this message]
2024-08-02  5:02     ` Gautham R.Shenoy
2024-09-26 20:56       ` Luna Nova
2024-09-30 14:47         ` Gautham R. Shenoy

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=2f793cc8.a13d.19108df0a58.Coremail.00107082@163.com \
    --to=00107082@163.com \
    --cc=Alexander.Deucher@amd.com \
    --cc=Li.Meng@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=Xiaojian.Du@amd.com \
    --cc=Xinmei.Huang@amd.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=perry.yuan@amd.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=viresh.kumar@linaro.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