Bug 1766198

Summary: Fan doesn't stop on Dell XPS 17 with NVIDIA GPU after kernel-upgrade 5.2->5.3
Product: [Fedora] Fedora Reporter: redhat
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 30CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-02 13:35:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description redhat 2019-10-28 14:53:19 UTC
Description of problem:
After upgrading from kernel 5.2.17 to 5.3.6/5.3.7 the fan of my laptop Dell XPS17 does not stop. I'm pretty sure that I'm hit by the very same issue reported against Arch Linux https://bbs.archlinux.org/viewtopic.php?id=249330

Version-Release number of selected component (if applicable):
linux 5.3.6-200.fc30.x86_64

How reproducible:
Alway with kernel 5.3.


Steps to Reproduce:
1. Just boot the kernel 5.3.x
2.
3.

Actual results:
Fan does not stop.


Expected results:
Fan only runs on hight CPU or GPU usage.

Additional info:
With kernel 5.3 a new pci device pops up and does not get powered down.

 # cat /sys/kernel/debug/vgaswitcheroo/switch
 0:IGD:+:Pwr:0000:00:02.0
 1:DIS: :DynPwr:0000:01:00.0
 2:DIS-Audio: :DynPwr:0000:01:00.1

Removing it helps temporarily

 # echo 1 > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.1/remove
 # cat /sys/kernel/debug/vgaswitcheroo/switch
 0:IGD:+:Pwr:0000:00:02.0
 1:DIS: :DynOff:0000:01:00.0

Comment 1 Hans de Goede 2019-11-02 13:35:21 UTC
This should be fixed in 5.3.8 which is currently in updates-testing.

*** This bug has been marked as a duplicate of bug 1757891 ***