kworker uses 70-90% of a CPU core (hyperthreaded)

This change was made by a bot.

why is this incomplete? should I add something?

Sorry to budge in. Experiencing the exact same problem on my brand new Samsung Chronos Series 7 using Arch Linux.

Just thought you might be interested in a dirty workaround that takes CPU usage down (at the expense of some problem? dunno, still haven't experienced any):

1 - Locate problematic GPE in /sys/firmware/acpi/interrupts/ (just cat each gpe until you see one with a high interrupt count - mine was gpe13)
2 - execute: echo disable > /sys/firmware/acpi/interrupts/gpexx (substitute for the one you found on the previous step).

If that works, you might want to execute it on every system launch (using systemd or whatever ubuntu uses for that) and after resume (I'm using pm-utils for that).

I suspect either some driver not playing well or samsung BIOS problem (although I still get it after update) are creating a never-ending interrupt stream. I saw no difference between lsmod when boot worked ok or when the high CPU usage was detected so maybe it is execution-order related?

I'm also getting [drm:__gen6_gt_force_wake_mt_get] *ERROR* Timed out waiting for forcewake old ack to clear. on boot. This might be related?

@Alexandre: great work man! thank you very much, your solution is really appreciated.

I'm experiencing the same problem as exposed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793
(this bug it's a duplicate of the 887793, but because of the solution is really appreciated)

I've tried your solution (mine too is the gpe13, so I think there is some magic in this number lol) and the CPU is quickly returned to a normal state.

Though the workaround works, this is a serious issue (definitely above "Medium" importance and needs to be solved at the kernel level. WTH is interrupt 13 anyway? Maybe it is invoking/reporting something important.

I could not execute the echo command from a normal terminal, however it works on boot - added to /etc/rc.local file (Ubuntu's "user" startup script). The suspend fix is described in the original (887793) bug thread: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793/comments/114

Just did a little blog post on the subject, which sums up the fixes. I hope it is useful.

http://carlocapocasa.com/crushing-the-kworker-uprising-or-how-to-fix-your-linux-lenovo-ideapad-y560p/

This bug also affects me, using Asus A53S Notebook. For me the problem was in gpe06, thanks a ton for the workaround.

Same here, on an Asus X53sc. Disabling gpe06 fixed the issue.
Thank you very much!!

Mio, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mark 1883 F.... pulseaudio
DistroRelease: Ubuntu 13.10
HibernationDevice: RESUME=UUID=c15da4c5-75e7-4590-ad12-5b994dd400bb
InstallationDate: Installed on 2013-11-23 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 700Z3C/700Z5C
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-13-generic N/A
 linux-backports-modules-3.11.0-13-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/19/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P04ABJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: NP700Z5C-SO2ZA
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP04ABJ:bd09/19/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn700Z3C/700Z5C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP700Z5C-SO2ZA:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 700Z3C/700Z5C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Mark Holtzhausen, please do not apport-collect to this bug as you are not the original reporter. If you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions or comments, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

I have 12.04, but I try all availiable kernels from 12.10, 13.04, 13.10 and this bug affect me

This change was made by a bot.

Vladimir Scherbaev, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Just had this again.

Pablo Almeida, making "Me too!" comments is just simply unhelpful. However, so your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

the above apport was sent from the current 18.04 release (with gpe13 interrupt disabled).
I did a fresh install and noticed again this problem

the workaround was the same as described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491467

echo "disable" > /sys/firmware/acpi/interrupts/gpe13

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

This change was made by a bot.

the above apport was sent while gpe13 interrup was enabled and issue was occurring (massive amount of interrupt, high cpu usage)

$ cat /sys/firmware/acpi/interrupts/gpe13
 3913101 STS enabled unmasked

just in a few seconds

i tested the 4.17.0-rc4 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc4/ and can confirm that this is still an issue there
 4.17.0-rc5 would not boot

Full computer model is Samsung Chronos 7 NP700Z7C-S02DE

Mio, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO: Rafael J. Wysocki and Len Brown CC: linux-acpi)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your help.

Mio, please don't change the Description. It is filled with old, irrelevant, and speculative statements that confuse and hinder developers resolving the problem.

Despite this, have you reported this upstream as noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1087010/comments/73 ?

I did some more research and found this kernel bug https://bugzilla.kernel.org/show_bug.cgi?id=53071 which seems to descibe exactly this issue. In that thread there is mentioned that a bios update might fix the problem.
Thus I went hunting for an update for my model since the Software Update tool from Samsung does not show any updates. Eventually i found this https://www.samsung.com/us/support/owners/product/np700z7c (could not find an equivalent on the german site..). At "firmware" there is a download button that does work for me but in the HTML code there is a link http://org.downloadcenter.samsung.com/downloadfile/ContentsFile.aspx?CDSite=US&CttFileID=4986477&CDCttType=FM&ModelType=C&ModelName=NP700Z7C-S01US&VPath=FM/201203/20120305100525911/BIOSUpdate.exe
which leads to a BIOS Update Tool (changing the modelname to my model leads to the same download)
lunching this from windows allowed me to update to version P06AAE from P04AAE.

I can confirm that this does NOT solve the issue of the gpe13 interrupt spamming.

In that kernel bug it is mentioned that the output of dmidecode might be / is useful to fix this. Thus I have attached that here too (executed after the bios update as you can see)

sorry i continued posting with information i thought might be relevant or helpful without reloading the page and did not see the new comments.
I did now send the report as requested. How do i know when it is available in the archives?

here is the mailing list post https://marc.info/?l=linux-acpi&m=152675757008502&w=2

Hi Mio,

Can you install linux-tools-generic and use `perf top` to see which functions cause this issue?

`perf top` output on 4.15.0-20-generic

13,09% [kernel] [k] acpi_os_read_port
11,81% [kernel] [k] acpi_ns_search_one_scope
 6,42% [kernel] [k] acpi_os_write_port
 4,62% [kernel] [k] acpi_ut_track_stack_ptr
 4,17% [kernel] [k] acpi_ut_trace_ptr
 3,42% [kernel] [k] strncpy
 3,28% [kernel] [k] __tick_nohz_idle_enter
 2,49% [kernel] [k] acpi_ut_status_exit
 1,63% [kernel] [k] acpi_ex_resolve_node_to_value
 1,50% [kernel] [k] nmi
 1,34% libapt-pkg.so.5.0.2 [.] lroundf@plt
 1,31% [kernel] [k] acpi_ut_update_ref_count.part.1
 1,28% [kernel] [k] acpi_ex_resolve_operands
 1,25% [kernel] [k] acpi_ut_add_reference
 1,23% [kernel] [k] acpi_ut_acquire_mutex
 1,19% libapt-pkg.so.5.0.2 [.] _ZNK8pkgCache11DepIterator10IsNegativeEv
 1,18% [kernel] [k] acpi_ns_evaluate
 1,12% [kernel] [k] acpi_ut_trace
 1,00% libstdc++.so.6.0.25 [.] _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE9_M_createERmm
 0,97% [kernel] [k] _find_next_bit
 0,92% [kernel] [k] kmem_cache_alloc
 0,82% [kernel] [k] rcu_note_context_switch
 0,71% [kernel] [k] menu_select
 0,67% [kernel] [k] __kmalloc
 0,64% [kernel] [k] acpi_ut_valid_internal_object
 0,62% [kernel] [k] acpi_ut_update_object_reference
 0,57% [kernel] [k] kfree
 0,57% libapt-pkg.so.5.0.2 [.] _Z13stringcasecmpN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEEES9_S2_S2_
 0,51% libapt-pkg.so.5.0.2 [.] _ZN6FileFd5WriteEPKvy
 0,49% [kernel] [k] kmem_cache_free
 0,48% [kernel] [k] acpi_ns_lookup
 0,48% python3.6 [.] 0x0000000000184852
 0,47% [kernel] [k] acpi_hw_validate_io_request
 0,45% [kernel] [k] acpi_ut_match_predefined_method
 0,42% [kernel] [k] prefetch_freepointer
 0,39% [kernel] [k] acpi_ps_get_next_arg
 0,39% [kernel] [k] acpi_ut_get_next_predefined_method
 0,35% [kernel] [k] acpi_ds_exec_begin_op
 0,35% [kernel] [k] acpi_ps_create_op
 0,33% [kernel] [k] acpi_ps_get_opcode_info
 0,33% [kernel] [k] acpi_ps_parse_loop
 0,32% [kernel] [k] acpi_ut_repair_name
 0,31% [kernel] [k] acpi_ex_read_data_from_field
 0,31% [kernel] [k] acpi_ns_build_normalized_path
 0,30% [kernel] [k] acpi_ds_delete_result_if_not_used
 0,30% [kernel] [k] acpi_ds_create_operand
 0,...

Ok I just saw it's a GPE issue. Can you try latest mainline kernel [1]? There are several GPE/EC fixes.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc6/

I can confirm that the issue is present with 4.17-rc6 too

Can you attach acpidump?

Does this laptop have a free fall sensor?

Seems like gpe13 tries to notify your SATA controller something. Or maybe it's related to the ExpressCache?

    Scope (_GPE)
    {
        Method (_L13, 0, NotSerialized) // _Lxx: Level-Triggered GPE
        {
            If ((PFLV == FDTP))
            {
                Return (Zero)
            }

            GPE3 = Zero
            GL08 |= 0x10
            Notify (\_SB.PCI0.SAT0, 0x82) // Device-Specific Change
            Return (Zero)
        }
    }

I dont't believe my laptop has a free fall sensor, didn't ever hear of such a thing. How do I check?
It does have ExpressCache though.
My vague hypothesis is that it has something to do with the ODD but i don't understand enough of this for being able to verify any of this without instructions.

Sorry for the belated response.

In this case, I think kernel parameter "acpi_mask_gpe=0x13" to disable it is the only workaround.