Upgrading 18.04 to 20.04 Causes Fan to run at maximum after resume from suspend ...

[Patrick Gillespie]

In brief, I upgraded Kubuntu 18.04 to 20.04 Beta.

STEPS TO REPRODUCE
1. Sleep/Suspend System
2. Resuming from Suspend can cause cooling fan to run at maximum.

I have a vague memory that this is a recurring issue with certain systems and has been dealt with elsewhere. And it would appear that this bug has come back to life in the latest kernel.

WORKAROUND:

1. Sleep/Suspend System and Resume again. (This may have to be done once or twice. Only occasionally do I need to completely restart.)
2. Revert to older kernel. In my case I reverted to 4.18.5-041805-generic and the bug has gone away. Tried reverting to a more recent kernel 5.2, but the bug persisted.

System: Host: ThinkPad Kernel: 5.4.0-21-generic x86_64 bits: 64 Desktop: KDE Plasma 5.18.3
           Distro: Ubuntu 20.04 LTS (Focal Fossa)
Machine: Type: Laptop System: LENOVO product: 20HF0012US v: ThinkPad T470s serial: <superuser/root required>
           Mobo: LENOVO model: 20HF0012US v: SDK0J40697 WIN serial: <superuser/root required> UEFI: LENOVO v: N1WET31W (1.10 )
           date: 04/17/2017
Battery: ID-1: BAT0 charge: 21.6 Wh condition: 22.0/23.5 Wh (94%)
           ID-2: BAT1 charge: 21.4 Wh condition: 21.7/26.3 Wh (82%)
CPU: Topology: Dual Core model: Intel Core i5-7300U bits: 64 type: MT MCP L2 cache: 3072 KiB
           Speed: 800 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 792 2: 830 3: 809 4: 822
Graphics: Device-1: Intel HD Graphics 620 driver: i915 v: kernel
           Display: x11 server: X.Org 1.20.7 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz
           OpenGL: renderer: Mesa Intel HD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.0.2
Audio: Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel
           Sound Server: ALSA v: k5.4.0-21-generic
Network: Device-1: Intel Ethernet I219-LM driver: e1000e
           IF: enp0s31f6 state: down mac: c8:5b:76:e3:99:5b
           Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi
           IF: wlp58s0 state: up mac: f8:59:71:49:f6:2e
Drives: Local Storage: total: 476.94 GiB used: 272.06 GiB (57.0%)
           ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 PRO 512GB size: 476.94 GiB
Partition: ID-1: / size: 33.65 GiB used: 22.44 GiB (66.7%) fs: ext4 dev: /dev/nvme0n1p2
           ID-2: swap-1 size: 15.62 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4
Sensors: System Temperatures: cpu: 36.5 C mobo: N/A
           Fan Speeds (RPM): cpu: 0
Info: Processes: 236 Uptime: 1d 19h 44m Memory: 19.43 GiB used: 6.50 GiB (33.5%) Shell: bash inxi: 3.0.38

Workaround:

This may have to with a Kernel Regression or be Kernel related? (This is getting quickly above my pay grade.) I used Grub Customizer to boot with kernel 4.18.5-041805-generic and network connectivity/throughput is now functioning as it should.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1871411/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1871411

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Patrick Gillespie (vermontpoet)]

Because the bug doesn't produce any error messages (segmentation violation, bus error, floating point exception, etc.)" apport wouldn't seem to be useful in this case? I'm going to mark the bug as 'Confirmed', according to your instructions, but by all means change if I'm incorrect.