Jump to content
  • Kworker 100cpu bug fixed with go code


    dopeytree
    • Minor

    6.12.4

     

    Bug: Something causes kworker cpu to get stuck at 100% while not really doing anything which in turn causes unnecessary boosting and power usage.

     

    This kernel bug https://askubuntu.com/questions/33640/kworker-what-is-it-and-why-is-it-hogging-so-much-cpu

     

    Quote

     

    Instead I think this CPU usage is not normal and is related to the well-known kworker bug:https://bugs.launchpad.net/ubuntu/+source/linux/+bug/887793

     

    The solution for me and for many others was, first of all, find out the "gpe" that is causing the bad stuff with something like:

    grep . -r /sys/firmware/acpi/interrupts/

     

    and check for an high value (mine was gpe13 - with a value like 200K - so, you have to change it accordingly, if differs). After that:

     

     

    So 

     

    grep . -r /sys/firmware/acpi/interrupts/

     

    To find the culprit then..

     

    Fixed with the following inserted into config go file

     

    # -------------------------------------------------
    # CPU bug fix
    # -------------------------------------------------
    
    echo disable > /sys/firmware/acpi/interrupts/gpe69 2>/dev/null

     




    User Feedback

    Recommended Comments



    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.

×
×
  • Create New...