[Kernel-packages] [Bug 1790688] Re: x86/pti: 32-bit x86 systems support already available.
PTI makes my 2 32 bit laptops unstable. I have lubuntu 18.04 installed on both and they both started having trouble after the linux-image upgrade from 4.15.0-46/47 to 4.15.0-50/51. They either fail to boot without locking up or fail to shut down cleanly. I rarely get any useful logs or messages on the screen, although if the machines do boot without locking up, I have seen messages like this when they fail to shut down: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1] I did manage to recover some BUGs with call traces from kern.log when I tried the ubuntu mainline kernel build, 4.19.31-041931-generic #201903231635. Here are typical BUG stmts: Apr 22 10:16:04 mikedell kernel: [ 43.339955] BUG: unable to handle kernel NULL pointer dereference at 0008 Apr 22 10:16:04 mikedell kernel: [ 43.484957] BUG: unable to handle kernel paging request at eef4817c Unfortunately, I think it's the only kernel that's given me this much info. I'd be happy to share the full call traces I have captured if anyone is interested. Neither laptop has a serial port and I'm not a kernel developer, so I don't feel I've got the means to properly diagnose the problem. Howver, I have since found that when I compile the kernel from: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/ and change only one config parameter, CONFIG_PAGE_TABLE_ISOLATION, the kernel with the param enabled is unstable, but the kernel with the param disabled is stable. I have found this to be the case with kernels 4.19.50 and 5.1.9. The two laptops are: Dell Inspiron B130 with an Intel Celeron M 1.50GHz (family: 0x6, model: 0xd, stepping: 0x8) IBM Thinkpad R51 1836HAU with Intel Pentium M processor 725 (1.6 GHz) The Thinkpad's Pentium M 725 is a Dothan processor that supports PAE, but lies about it, so it requires the forcepae kernel parameter. The Dell's Celeron M does not requre the forcepae parameter. I've been trying to figure out if this is a known problem. THere's so little love for 32 bt hardware these days. Then I saw this bug report and thought it might be a good place to start. Should I post this info on the linux-kernel mailing list? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790688 Title: x86/pti: 32-bit x86 systems support already available. Status in linux package in Ubuntu: Triaged Bug description: Hello. This is a very good news: 'PTI' support for x86-32 architecture is available. Linux kernel v4.19 release candidate, finally have Kernel Page-Table Isolation ('PTI', previously known as 'KAISER') support. As we know, 'PTI' provides protection against attack, known as the "Meltdown" (CVE-2017-5754), that breaks isolation between user applications and the operating system etc. However, this protection - needed for "Meltdown" mitigation - wasn't available on 32-bit x86 systems. Until now. So, I would like to ask a question: are there any plans to backport Kernel Page-Table Isolation patches for Linux kernels available in "Trusty"/14.04, "Xenial"/16.04 and "Bionic"/18.04 releases etc.? I'm asking, because it seems, that pretty much no developers run 32-bit any more. However, there still are many 32-bit users out there. For more informations about how 'PTI' was implemented, created for 32 bit x86 architecture, please check - for example - commit '7757d607c6b31' ("x86/pti: Allow CONFIG_PAGE_TABLE_ISOLATION for x86_32") and these messages on lkml mailing list and lwn.net website (which contains summary of the first half of the 4.19 kernel merge window): ✗ http://lkml.iu.edu/hypermail/linux/kernel/1807.2/02790.html ('PTI' on x86-32; PATCH v.8) ✗ https://lwn.net/Articles/762566/ (See "Architecture-specific" changes) I would like to send a big "Thank You" to Mr Joerg Roedel (and Others, of course) for his amazing work - a whole raft of measures and patches to make this possible - to enable 'PTI' mitigation on x86-32 architecture etc. Thanks, best regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
Here's link to upstream bug report, including a fix that works for me: https://bugzilla.kernel.org/show_bug.cgi?id=135691 ** Bug watch added: Linux Kernel Bug Tracker #135691 http://bugzilla.kernel.org/show_bug.cgi?id=135691 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Triaged Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. git bisecting the linux-stable kernel led me to the bad commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Gateway dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: NE570 dmi.product.version: V2.06 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
Reported to upstream here: http://www.spinics.net/lists/linux-acpi/msg67711.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Triaged Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. git bisecting the linux-stable kernel led me to the bad commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Gateway dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: NE570 dmi.product.version: V2.06 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
I tested v4.7-rc7, specifically this deb: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc7/linux-image-4.7.0-040700rc7-generic_4.7.0-040700rc7.201607110032_amd64.deb It does not fix the problem, so I will be adding the kernel-bug-exists-upstream tags as you requested. The ACPI error messages have changed to reflect a newer version: ACPI Error: Method reached maximum reentrancy limit (255) (20160422/dsmethod-340) FWIW, I haven't found it necessary to install linux-header debs since the generic kernels support all the hardware on this machine and I don't need to compile any third party modules. I have also found that if the machine is idle, there's a pause in the "ACPI Error" messages. I think it depends on how much writing to disk is going on, but that's just a gut feeling. I'm not quite sure how to verify that assumption, or if it would help diagnose the problem. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.7-rc7 ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Confirmed Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. Since I can reproduce the problem with a kernel built from the linux- stable git tree, should this problem also be reported to bugzilla.kernel.org? Or, should I try to contact the author of the "first bad commit", Lv Zheng with the info in this bug report? Is there more testing I should do? Starting with enabling CONFIG_ACPI_DEBUG? Would there be value in me reverting the "first bad commit" to the latest Linux-4.4 kernel or to the latest xenial kernel to see if that helps or hurts? Is there more info I should collect, like output from acpidump? (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
The attachment, kernels.txt, are notes I took while manually bisecting ubuntu kernels listed here: https://launchpad.net/ubuntu/xenial/+source/linux and mainline kernels from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ The attachment, bisect.txt, is an annotated "git bisect log" associating commits from the linux-stable tree with the deb packages I built, installed, and tested. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Confirmed Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. Since I can reproduce the problem with a kernel built from the linux- stable git tree, should this problem also be reported to bugzilla.kernel.org? Or, should I try to contact the author of the "first bad commit", Lv Zheng with the info in this bug report? Is there more testing I should do? Starting with enabling CONFIG_ACPI_DEBUG? Would there be value in me reverting the "first bad commit" to the latest Linux-4.4 kernel or to the latest xenial kernel to see if that helps or hurts? Is there more info I should collect, like output from acpidump? (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPa
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
** Attachment added: "kernels.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701218/+files/kernels.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Confirmed Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. Since I can reproduce the problem with a kernel built from the linux- stable git tree, should this problem also be reported to bugzilla.kernel.org? Or, should I try to contact the author of the "first bad commit", Lv Zheng with the info in this bug report? Is there more testing I should do? Starting with enabling CONFIG_ACPI_DEBUG? Would there be value in me reverting the "first bad commit" to the latest Linux-4.4 kernel or to the latest xenial kernel to see if that helps or hurts? Is there more info I should collect, like output from acpidump? (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
** Attachment added: "bisect.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701219/+files/bisect.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Confirmed Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. Since I can reproduce the problem with a kernel built from the linux- stable git tree, should this problem also be reported to bugzilla.kernel.org? Or, should I try to contact the author of the "first bad commit", Lv Zheng with the info in this bug report? Is there more testing I should do? Starting with enabling CONFIG_ACPI_DEBUG? Would there be value in me reverting the "first bad commit" to the latest Linux-4.4 kernel or to the latest xenial kernel to see if that helps or hurts? Is there more info I should collect, like output from acpidump? (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
** Tags removed: acpi ** Tags added: kernel-acpi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9 Status in linux package in Ubuntu: Confirmed Bug description: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. Since I can reproduce the problem with a kernel built from the linux- stable git tree, should this problem also be reported to bugzilla.kernel.org? Or, should I try to contact the author of the "first bad commit", Lv Zheng with the info in this bug report? Is there more testing I should do? Starting with enabling CONFIG_ACPI_DEBUG? Would there be value in me reverting the "first bad commit" to the latest Linux-4.4 kernel or to the latest xenial kernel to see if that helps or hurts? Is there more info I should collect, like output from acpidump? (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 d
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
** Description changed: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection - which lead me to doing "git bisect" on the linux-stable tree. The result lead me to this commit: + which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. - I assume this should also be reported to bugzilla.kernel.org. It is - convenient to have the ubuntu-bug command do initial data collection. + Since I can reproduce the problem with a kernel built from the linux- + stable git tree, should this problem also be reported to + bugzilla.kernel.org? Or, should I try to contact the author of the + "first bad commit", Lv Zheng with the info in this + bug report? + + Is there more testing I should do? Starting with enabling + CONFIG_ACPI_DEBUG? + + Would there be value in me reverting the "first bad commit" to the + latest Linux-4.4 kernel or to the latest xenial kernel to see if that + helps or hurts? + + Is there more info I should collect, like output from acpidump? + (Something I've seen mentioned on bugzilla.kernel.org) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_
[Kernel-packages] [Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
** Description changed: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection - which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: + which lead me to doing "git bisect" on the linux-stable tree. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. I assume this should also be reported to bugzilla.kernel.org. It is convenient to have the ubuntu-bug command do initial data collection. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Gateway dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: NE570 dmi.product.version: V2.06 dmi.sys.vendor: Gateway -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1603230 Title: acpi regression first bad commit 02b771b64b7
[Kernel-packages] [Bug 1603230] [NEW] acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9
Public bug reported: I found what I believe is a regression on my Gateway ne570 laptop. It was running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.803775] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.866294] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) Jul 10 17:01:10 buus-ne570 kernel: [ 57.928403] ACPI Error: Method reached maximum reentrancy limit (255) (20150818/dsmethod-341) These messages would be repeated several times a second, and then pause for several seconds, then start again. I believe they are the cause of more sluggish behavior than with the older *Buntu releases. I followed the instructions here: https://wiki.ubuntu.com/Kernel/KernelBisection which lead me to doing "git bisect" on the linux-stable kernel. The result lead me to this commit: # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations commit 02b771b64b73226052d6e731a0987db3b47281e9 Author: Lv Zheng Date: Wed Aug 12 11:12:02 2015 +0800 ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations It is proven that Windows evaluates _Qxx handlers in a parallel way. This patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to form a separate queue, so that _Qxx evaluations can be queued up on different CPUs rather than being queued up on a CPU0 bound queue. Event handling related callbacks are also renamed and sorted in this patch. Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411 Reported-and-tested-by: Gabriele Mazzotta Signed-off-by: Lv Zheng Signed-off-by: Rafael J. Wysocki The laptop was purchased from tigerdirect. Here's link to specs: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911 The laptop appears to be a re-branded Acer Aspire E1-570: http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001 Both have Insyde UEFI firmware. The latest version for both is v2.06 and have same release date, 11/11/2013, according to the Acer & Gateway support web sites, although the firmware reports an Oct date. I realize it's quite likely that the laptop's firmware is the root cause of the problem. However, since the problem did not exist on older kernels, I hope a patch or workaround can be identified that will allow me to make good use of this laptop. I assume this should also be reported to bugzilla.kernel.org. It is convenient to have the ubuntu-bug command do initial data collection. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buus 1830 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 14 18:11:02 2016 HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190 InstallationDate: Installed on 2016-07-01 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gateway NE570 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-31-generic N/A linux-backports-modules-4.4.0-31-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/08/2013 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA50_CX dmi.board.vendor: Gateway dmi.board.version: V2.06 dmi.chassis.asset.tag: Acer Asset Tag String dmi.chassis.type: 10 dmi.chassis.vendor: Insyde Corp. dmi.chassis.version: V2.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06: dmi.product.name: NE570 dmi.product.version: V2.06 dmi.sys.vendor: Gateway ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial ** Description changed: - I found what I believe is a regression on my Gateway ne570 laptop. It was running - mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed - ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like this: - Jul 10 17:01:10 buus-ne570 kernel: [ 57.741630] ACPI Error: Method reached maximum - reentrancy limit (255) (