Bug 1328633

Summary: ACPI errors on Kernel 4.5.1-300 i
Product: [Fedora] Fedora Reporter: jd528927
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 24CC: gansalmon, hcmeyer, itamar, jforbes, jonathan, kernel-maint, madhu.chinakonda, mail, mchehab, micsim2007
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: kernel-4.5.4-300.fc24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-14 23:24:04 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:
Attachments:
Description Flags
dmesg output none

Description jd528927 2016-04-19 23:08:55 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
Kernel 4.5.1-300 i


How reproducible:
Every time OS is installed

Steps to Reproduce:
1.Install F24 Alpha on AMD APU system
2.
3.

Actual results:
ACPI errors
K worker high cpu usage

Expected results:
lots of ACPI handler errors 

Additional info:
My system : AMD A4-5000 APU with Radeon(TM) HD Graphics
There were lots of ACPI errors in dmesg & the kworker taking up all power, so much that I couldn't login to the graphical desktop.

I tried to blacklist it but it did not work, so I removed it and the problem was solved for me:

Code:

rm -rf /lib/modules/4.5.1-300.fc24.x86_64/kernel/drivers/watchdog/sp5100_tco.ko.xz
Comment 1 jd528927 2016-04-19 23:16:50 UTC 
Description of problem:
sp5100 module causing constant ACPI handler errors, locking up system resources. removal of module solved problem.
Comment 2 Justin M. Forbes 2016-04-20 02:49:44 UTC 
This is being tracked upstream at https://bugzilla.kernel.org/show_bug.cgi?id=114201
Comment 3 Mike Simms 2016-04-20 21:49:26 UTC 
*** Bug 1327674 has been marked as a duplicate of this bug. ***
Comment 4 Mike Simms 2016-04-20 21:52:33 UTC 
Created attachment 1149211 [details]
dmesg output

Same behavioural issue I am experiencing with my system and this specific kernel version please see the attached dmesg output
Comment 5 Mike Simms 2016-04-22 17:48:13 UTC 
following steps resolved the issue for me. The system was previously clean installed with Alpha 7 and updated with dnf to stay current.

This solution was a bit drastic but a simple kernel upgrade with dnf made no difference.

1. clean install from Alpha 7 live ISO and restart
2. open terminal
3. sudo dnf distro-sync
4. systemctl daemon-reload
5. restart

I am back up and running with all previously installed packages without any breakages.

note I still get the '[   10.061554] sp5100_tco: I/O address 0x0cd6 already in use' entry in dmesg so I think that can be ruled out.
Comment 6 Justin M. Forbes 2016-05-09 14:51:00 UTC 
*** Bug 1329910 has been marked as a duplicate of this bug. ***
Comment 7 Justin M. Forbes 2016-05-09 14:52:47 UTC 
Patch from upstream has been applied to 4.5 kernels and should appear in the next builds.
Comment 8 Fedora Update System 2016-05-12 11:56:13 UTC 
kernel-4.5.4-300.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ef973efab7
Comment 9 Fedora Update System 2016-05-12 22:26:27 UTC 
kernel-4.5.4-300.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-ef973efab7
Comment 10 Herbert Carl Meyer 2016-05-14 08:20:22 UTC 
See bug 1323420. Kernel 4.5.4-300 has resolved it on my AMD hardware. This bug should also be resolved.
Comment 11 Fedora Update System 2016-05-14 23:22:10 UTC 
kernel-4.5.4-300.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.