kworker consuming cpu due to GPE13 interrupt storm on Fujitsu A544

By bisecting the kernel I have determined that the problem is not seen on the last Ubuntu 3.19 kernel 3.19.8-vivid but is seen on the first 4.0 kernel that will build using fakeroot debian/rules binary-headers binary-generic, which is

commit 636cdd7b2930ca2cdaf90eedd04fdb9fc7a8d5ec
Author: Stefan Bader <email address hidden>
Date: Thu Feb 14 09:55:49 2008 -0500

    UBUNTU: SAUCE: (no-up) ubuntu: dm-raid45

from https://code.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily

It also exists on the latest mainline kernel 4.2.0

This change was made by a bot.

I'd like to perform a bisect to figure out what commit caused this regression. We need to identify the earliest kernel where the issue started happening as well as the latest kernel that did not have this issue.

Before we start the bisect, can you first confirm that 3.19 final does not have the bug an 4.0-rc1 does have it? The two kernels can be downloaded from:

v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/
4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/

Thanks in advance!

Also, can you test the latest mainline kernel, 4.2 final? I'd like to confirm the bug is not fixed in mainline yet. If it is, we can perform a "Reverse" bisect to identify the commit that is the fix. The mainline kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/

I can confirm that
v3.19 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/ does not show the problem

4.0-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.0-rc1-vivid/
and
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.2-unstable/
both do show the problem

Great, thanks for testing. I'll start the bisect and post the first test kernel shortly.

I started a kernel bisect between v3.19 final and v4.0-rc1. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
02f1f2170d2831b3233e91091c60a66622f29e82

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

02f1f2170d2831b3233e91091c60a66622f29e82
http://kernel.ubuntu.com/~jsalisbury/lp1491467
linux-image-3.19.0-031900-generic_3.19.0-031900.201509021605_amd64.deb

is BAD
that is it shows the bug.

Thanks, I'll build the next test kernel.

I built the next test kernel, up to the following commit:
c5ce28df0e7c01a1de23c36ebdefcd803f2b6cbb

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

c5ce28df0e7c01a1de23c36ebdefcd803f2b6cbb
linux-image-3.19.0-031900-generic_3.19.0-031900.201509022146_amd64.deb

is GOOD :)

I built the next test kernel, up to the following commit:
718749d56214aa97015fe01b76b6d6dd0c171796

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

718749d56214aa97015fe01b76b6d6dd0c171796
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031253_amd64.deb

is GOOD

I built the next test kernel, up to the following commit:
b3d6524ff7956c5a898d51a18eaecb62a60a2b84

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

b3d6524ff7956c5a898d51a18eaecb62a60a2b84
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031452_amd64.deb

is GOOD

I built the next test kernel, up to the following commit:
8cc748aa76c921d8834ef00f762f31acd2c93aa8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

8cc748aa76c921d8834ef00f762f31acd2c93aa8
linux-image-3.19.0-031900-generic_3.19.0-031900.201509031637_amd64.deb

is BAD

I built the next test kernel, up to the following commit:
d3f180ea1a44aecba1b0dab2a253428e77f906bf

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

d3f180ea1a44aecba1b0dab2a253428e77f906bf
linux-image-3.19.0-031900-generic_3.19.0-031900.201509032049_amd64.deb

is GOOD

I built the next test kernel, up to the following commit:
ba4877b9ca51f80b5d30f304a46762f0509e1635

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

ba4877b9ca51f80b5d30f304a46762f0509e1635
linux-image-3.19.0-031900-generic_3.19.0-031900.201509041408_amd64.deb

is GOOD

I built the next test kernel, up to the following commit:
7b1ee96f074cc931a2c226b33607fe7a74d5cba3

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

7b1ee96f074cc931a2c226b33607fe7a74d5cba3
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509050242_amd64.deb

is BAD

As a matter of interest, which repository have you cloned from?

This is the repo I am using:
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/

I built the next test kernel, up to the following commit:
875edad528cf29b382e82837e652e997aec16c49

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

875edad528cf29b382e82837e652e997aec16c49
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb

is GOOD

Can you confirm the repo please, I get
$ git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/
Cloning into 'linux'...
fatal: remote error: Repository '~ubuntu-kernel/ubuntu/+source/linux' not found.

Alternatively is it fundamentally the same (as far as this exercise is concerned) as
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily

I built the next test kernel, up to the following commit:
afb5abc262e962089ef2d7c2bbf71bb6f53a2a78

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

As far as my repo, I should have posted:
git://kernel.ubuntu.com/ubuntu/linux.git

What I posted in comment 26 was part of the path to my Wily remote.

afb5abc262e962089ef2d7c2bbf71bb6f53a2a78
/home/colinl/Downloads/linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081446_amd64.deb

is GOOD

I built the next test kernel, up to the following commit:
30fc8d138e9123f374a3c3867e7c7c5cd4004941

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

30fc8d138e9123f374a3c3867e7c7c5cd4004941
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509081948_amd64.deb

is Bad

I built the next test kernel, up to the following commit:
71ed848fd791bc0b53a1b7a04f29eb9e994c7cbb

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I don't think you have actually, there's nowt there :)

Sorry, my scp timed out. They should be there now.

71ed848fd791bc0b53a1b7a04f29eb9e994c7cbb
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509091541_amd64.deb

is BAD

Only one, or two, to go :)

It may be of interest that another A544 running kernel 3.13 exhibits the problem. It went away some time between then and 3.19 and came back in 4.0. The other machine does not have an SSD so that may not be a factor, though comments in the upstream bug suggested that it was a factor. Of course there may be multiple causes for apparently similar symptoms.

I built the next test kernel, up to the following commit:
0dc553652102c55a43eb1ab52e2049e478469f53

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1491467

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

0dc553652102c55a43eb1ab52e2049e478469f53
linux-image-3.19.0-031900rc4-generic_3.19.0-031900rc4.201509092055_amd64.deb

is BAD

The bisect reported the following commit as the commit that introduced the regression:

commit 0dc553652102c55a43eb1ab52e2049e478469f53
Author: Jarkko Sakkinen <email address hidden>
Date: Fri Dec 12 11:46:35 2014 -0800

    tpm: fix raciness of PPI interface lookup

I'll build a test kernel with just this commit reverted to see if it fixes the bug.

Have I missed something or has it not arrived yet?

I have gone back and confirmed that afb5abc262e962089e was good and 0dc553652102c55a4 is bad, just in case I had made a mistake.

No, there is no test kernel available yet. I attempted a revert of commit 0dc5536. However, the revert requires that other commits be reverted first.

I also need to ping the patch author that this commit is the cause of the regression.

OK. In case it is of interest I have determined that the problem was originally fixed between mainline kernels 3.13.11.11-trusty and 3.14-rc1-trusty, before being reintroduced in 4.0.

Thanks for the info. The 4.3-rc1 kernel is now available. It might be worthwhile giving that kernel a test. It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/

I think 4.3-rc1 kernel build has failed, at least there are no images there. I will test it when they appear.

4.3-rc1 kernel (linux-image-4.3.0-040300rc1-generic_4.3.0-040300rc1.201509160642_amd64.deb) also exhibits the problem.

The patch author requested an acpidump. Could you provide this? It can be done by installing the acpidump package the running:
 sudo acpidump -o acpidump.txt

Is anything happening on this?

I will ping upstream again and see if there is an update.

I am using a Fujitsu Lifebook A544, with normal HDD and optical drive.

The high-cpu load issue is present with kernel 3.19 (Ubuntu Trusty), 4.2 (Ubuntu Wily and Fedora 23) and 4.3 (Ubuntu Xenial), with BIOS 1.18 and 1.19. Moreover, the optical drive seems to be unable to read CDs and DVDs.

After upgrading the BIOS to 1.20, the problem disappears with all the aforementioned kernels, and the optical drive is back to reading CDs and DVDs again.

I believe that the issue was known by Fujitsu itself, since it reports the bug as fixed in the BIOS 1.19-1.20 changelog.

I am wondering if upgrading the BIOS solves the problem also for the SSD-equipped laptop.

I can confirm that updating to BIOS 1.20 also fixes it for me (with SSD drive). Strange that the problem only exhibited itself with certain kernel versions. So it seems Joseph and myself have wasted our time bisecting the kernel. Sorry Joseph. I learnt a lot in the process however. I will close the bug, I presume that correct status is ' invalid'.

I can confirm that on a clean install of 16.04 and kernel 4.4 and BIOS 1.10 this issue was also present, and also disappeared after upgrading the BIOS to 1.20.

On my Samsung NP700Z3C I discovered that the gpe13 is triggered if no disk is loaded in the slot-loading ODD (TSSTcorp SU-208CB). I noticed that the Fujitsu A544 has the same drive.
https://bugzilla.kernel.org/show_bug.cgi?id=53071#c75