CentOS - Apr 2015 - Centos 7 kworker uses 100% of single core on mulit-core processor usage inquiry

Greetings everyone. 

I am experiencing the kworker issue where a kworker is using 100% of a given
core.

This behavior was only observed after having installed a new water cooler, to
replace a cooler that had died. (Sealed closed loop device from Corsair)

The processor is staying around 40 degrees celsius as reported by the MB UEFI
interface. (ksysguard shows between 29 degrees and 30 degrees, when running KDE
4)

I am unable to isolate a cause, or resolution for getting the kworker usage back
to normal.

Very basic description of specs are as follows: 

AMD FX-8350 (not overclocked) 

32GB Corsair memory (1866Mhz non-overclocked) 

Sabortooth 990FX MB 

I have checked the locations for interrupts which has been indicated online,
however, I do not have any specific interrupts that are showing as even having a
high integer value to unset.

Here is the result of running the referenced command to view interrupts. 

[sysadmin at imaginationland ~]$ grep . -r /sys/firmware/acpi/interrupts/ 
/sys/firmware/acpi/interrupts/sci: 0 
/sys/firmware/acpi/interrupts/error: 0 
/sys/firmware/acpi/interrupts/gpe00: 0 invalid 
/sys/firmware/acpi/interrupts/gpe01: 0 invalid 
/sys/firmware/acpi/interrupts/gpe02: 0 invalid 
/sys/firmware/acpi/interrupts/gpe03: 0 disabled 
/sys/firmware/acpi/interrupts/gpe04: 0 disabled 
/sys/firmware/acpi/interrupts/gpe05: 0 enabled 
/sys/firmware/acpi/interrupts/gpe06: 0 invalid 
/sys/firmware/acpi/interrupts/gpe07: 0 invalid 
/sys/firmware/acpi/interrupts/gpe08: 0 invalid 
/sys/firmware/acpi/interrupts/gpe09: 0 invalid 
/sys/firmware/acpi/interrupts/gpe10: 0 disabled 
/sys/firmware/acpi/interrupts/gpe11: 0 disabled 
/sys/firmware/acpi/interrupts/gpe12: 0 disabled 
/sys/firmware/acpi/interrupts/gpe13: 0 invalid 
/sys/firmware/acpi/interrupts/gpe14: 0 invalid 
/sys/firmware/acpi/interrupts/gpe15: 0 invalid 
/sys/firmware/acpi/interrupts/gpe16: 0 enabled 
/sys/firmware/acpi/interrupts/gpe0A: 0 enabled 
/sys/firmware/acpi/interrupts/gpe17: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0B: 0 disabled 
/sys/firmware/acpi/interrupts/gpe18: 0 disabled 
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid 
/sys/firmware/acpi/interrupts/gpe19: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0D: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0F: 0 disabled 
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1B: 0 disabled 
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid 
/sys/firmware/acpi/interrupts/sci_not: 0 
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid 
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled 
/sys/firmware/acpi/interrupts/gpe_all: 0 
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled 
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled 
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid 

Respectfully, 

Martes G Wigglesworth

Greetings again everyone. 

Can someone please respond to this? 

I am not sure what is causing this issue, however, others seem to have
experienced it in the past.

Could this be caused by the processor being damaged? 

Nothing has changed on the system, except for the heat warning shutoff when the
water cooler died, and the system was not restarted until the new one was
installed.

Any input would be appreciated, however, no response at all is just
disappointing.

Thanks for any help that can be provided. 

Respectfully, 

Martes G Wigglesworth 


From: "Martes" <mailinglistmember at mgwigglesworth.net> 
To: "centos" <centos at centos.org> 
Sent: Sunday, April 19, 2015 4:46:12 PM 
Subject: kworker 100% of single core on mulit-core processor usage inquiry 

Greetings everyone. 

I am experiencing the kworker issue where a kworker is using 100% of a given
core.

This behavior was only observed after having installed a new water cooler, to
replace a cooler that had died. (Sealed closed loop device from Corsair)

The processor is staying around 40 degrees celsius as reported by the MB UEFI
interface. (ksysguard shows between 29 degrees and 30 degrees, when running KDE
4)

I am unable to isolate a cause, or resolution for getting the kworker usage back
to normal.

Very basic description of specs are as follows: 

AMD FX-8350 (not overclocked) 

32GB Corsair memory (1866Mhz non-overclocked) 

Sabortooth 990FX MB 

I have checked the locations for interrupts which has been indicated online,
however, I do not have any specific interrupts that are showing as even having a
high integer value to unset.

Here is the result of running the referenced command to view interrupts. 

[sysadmin at imaginationland ~]$ grep . -r /sys/firmware/acpi/interrupts/ 
/sys/firmware/acpi/interrupts/sci: 0 
/sys/firmware/acpi/interrupts/error: 0 
/sys/firmware/acpi/interrupts/gpe00: 0 invalid 
/sys/firmware/acpi/interrupts/gpe01: 0 invalid 
/sys/firmware/acpi/interrupts/gpe02: 0 invalid 
/sys/firmware/acpi/interrupts/gpe03: 0 disabled 
/sys/firmware/acpi/interrupts/gpe04: 0 disabled 
/sys/firmware/acpi/interrupts/gpe05: 0 enabled 
/sys/firmware/acpi/interrupts/gpe06: 0 invalid 
/sys/firmware/acpi/interrupts/gpe07: 0 invalid 
/sys/firmware/acpi/interrupts/gpe08: 0 invalid 
/sys/firmware/acpi/interrupts/gpe09: 0 invalid 
/sys/firmware/acpi/interrupts/gpe10: 0 disabled 
/sys/firmware/acpi/interrupts/gpe11: 0 disabled 
/sys/firmware/acpi/interrupts/gpe12: 0 disabled 
/sys/firmware/acpi/interrupts/gpe13: 0 invalid 
/sys/firmware/acpi/interrupts/gpe14: 0 invalid 
/sys/firmware/acpi/interrupts/gpe15: 0 invalid 
/sys/firmware/acpi/interrupts/gpe16: 0 enabled 
/sys/firmware/acpi/interrupts/gpe0A: 0 enabled 
/sys/firmware/acpi/interrupts/gpe17: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0B: 0 disabled 
/sys/firmware/acpi/interrupts/gpe18: 0 disabled 
/sys/firmware/acpi/interrupts/gpe0C: 0 invalid 
/sys/firmware/acpi/interrupts/gpe19: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0D: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0E: 0 invalid 
/sys/firmware/acpi/interrupts/gpe0F: 0 disabled 
/sys/firmware/acpi/interrupts/gpe1A: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1B: 0 disabled 
/sys/firmware/acpi/interrupts/gpe1C: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1D: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1E: 0 invalid 
/sys/firmware/acpi/interrupts/gpe1F: 0 invalid 
/sys/firmware/acpi/interrupts/sci_not: 0 
/sys/firmware/acpi/interrupts/ff_pmtimer: 0 invalid 
/sys/firmware/acpi/interrupts/ff_rt_clk: 0 disabled 
/sys/firmware/acpi/interrupts/gpe_all: 0 
/sys/firmware/acpi/interrupts/ff_gbl_lock: 0 enabled 
/sys/firmware/acpi/interrupts/ff_pwr_btn: 0 enabled 
/sys/firmware/acpi/interrupts/ff_slp_btn: 0 invalid 

Respectfully, 

Martes G Wigglesworth

On Mon, Apr 20, 2015 at 09:00:07AM -0400, Martes wrote:
> Greetings again everyone. 
> 
> Can someone please respond to this? 
You just posted yesterday...

Anyway, you didn't give much context.  I can see from a google search
why you provided the interrupts output, but judging from what you
posted, that's not the problem.

Perhaps you have a CPU task that's running at 100%?  Did you try and
run 'top'?

Also, what version of CentOS are you running?  Are you running the
latest kernel?

-- 
Jonathan Billings <billings at negate.org>