From: Sourajyoti Basak <basak.sb2006@gmail.com>
To: platform-driver-x86@vger.kernel.org
Cc: mpearson-lenovo@squebb.ca,
Derek John Clark <derekjohn.clark@gmail.com>,
ikepanhc@gmail.com, hansg@kernel.org,
ilpo.jarvinen@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [BUG] ideapad_laptop: fans do not ramp up properly under CPU load on Lenovo IdeaPad 3 15ALC6 Ub (82KU)
Date: Tue, 2 Jun 2026 20:43:26 +0530 [thread overview]
Message-ID: <49faacb7-3e01-4d01-80b1-4b939a904138@gmail.com> (raw)
In-Reply-To: <CAA7g7-S_nP+jPfi7pJKj0a0g-gKXMJ7+fMH_+v11JbRRm96b9g@mail.gmail.com>
On 09/05/26 9:00 pm, Sourajyoti Basak wrote:
> Hello,
>
> I am using a Lenovo IdeaPad 3 15ALC6 Ub (82KU), and I am encountering an
> issue where the laptop fans do not respond appropriately to increasing
> CPU temperatures under Linux.
>
> System information:
> Laptop: Lenovo IdeaPad 3 15ALC6 Ub
> BIOS version:GLCN46WW
> System performance mode in BIOS: Extreme Performance
> Kernel: Linux 7.0.5-1-cachyos
> Distribution: CachyOS
> CPU: AMD Ryzen 5 5500U (12) @ 4.06 GHz
>
> Issue description:
> Under sustained CPU load (for example using stress -c $(nproc)), CPU
> temperatures rapidly increase to around 95-100°C. However, the fans do
> not ramp to maximum speed as expected. Therefore, the system begins
> thermal throttling after some time in this state.
>
> As a result:
>
> - The CPU reaches thermal throttling temperatures.
> - CPU frequencies drop significantly once throttling begins.
> - Fan RPM appears capped or insufficient despite high temperatures.
> - The issue appears consistently reproducible on my laptop and another
> person's laptop.
>
> Additional observations:
>
> - The issue persists across multiple recent kernel versions.
> - No hardware issues appear to be present. (Verified that the fans can
> indeed
> ramp up to max speed by
> `echo 1 | sudo tee /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/
> fan_mode`,
> which makes the fan enter "dust cleaning mode," causing it to ramp up to
> max speed
> and then back down to 0 RPM about 10 times.)
>
> Attachments:
> - DSDT in `DSDT.gz`
> - `dmidecode` in `dmidecode.txt`
>
> Data Collected during `stress -c $(nproc)` until thermal throttling:
> - EC information collected in a CSV file named `ec.csv`
> (using `sudo ec_probe monitor -i 0.5 -r ec.csv` from the NBFC project)
> - `sensors` information in `sensors.log`
> - CPU frequencies in `cpu-freq.log`
> - `dmesg` in `dmesg-live.log`
>
> Thank you for your time.
>
> Best regards,
> Sourajyoti Basak
Hello everyone,
Just a gentle ping on this bug report. The thermal throttling issue is
still present. Please let me know if there is any further ACPI/EC
debugging information I can provide.
Best Regards,
Sourajyoti Basak
next prev parent reply other threads:[~2026-06-02 15:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 15:30 [BUG] ideapad_laptop: fans do not ramp up properly under CPU load on Lenovo IdeaPad 3 15ALC6 Ub (82KU) Sourajyoti Basak
2026-06-02 15:13 ` Sourajyoti Basak [this message]
2026-07-06 16:50 ` Sourajyoti Basak
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=49faacb7-3e01-4d01-80b1-4b939a904138@gmail.com \
--to=basak.sb2006@gmail.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=ikepanhc@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpearson-lenovo@squebb.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox