8086:0166 [Lenovo IdeaPad Z580] 12.04-13.10 10-20min boot delay (From 3.2.0.29->3.12-rc2)

[Abhishek Ellore Sreenath]

On updating the kernel from 3.2.0.29 to any later version (3.2.0.30) and above, Ubuntu will not boot. I see a blank screen with a cursor but nothing happens after that.

Trying to boot into recovery mode is not useful either.

Booting into an older version of the kernel (3.2.0.29) is successful.

I have seen this issue with all kernels after 3.2.0.29 till date : 3.2.0.31, 3.2.0.32, 3.2.0.33, 3.2.0.34, 3.2.0.35

---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu15.1
Architecture: i386, AMD64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC269VC Analog [ALC269VC Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: abhishek 2104 F.... pulseaudio
 /dev/snd/pcmC0D0p: abhishek 2104 F...m pulseaudio
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf0610000 irq 46'
   Mixer name : 'Intel PantherPoint HDMI'
   Components : 'HDA:10ec0269,17aa4022,00100202 HDA:80862806,80860101,00100000'
   Controls : 26
   Simple ctrls : 12
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=4b3dd96d-8b88-4dbf-97d4-e2d78e5ad0fc
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3)
MachineType: LENOVO IdeaPad Z580
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic-pae root=UUID=a24e74a5-a245-4b37-b63c-96869939bf5c ro quiet splash
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic-pae N/A
 linux-backports-modules-3.2.0-29-generic-pae N/A
 linux-firmware 1.79.1
StagingDrivers: rts5139 mei
Tags: precise running-unity staging
Uname: Linux 3.2.0-29-generic-pae i686
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
dmi.bios.date: 06/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 5FCN34WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Lenovo
dmi.board.vendor: LENOVO
dmi.board.version: Lenovo Z580
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1:
dmi.product.name: IdeaPad Z580
dmi.product.version: Lenovo Z580
dmi.sys.vendor: LENOVO

These logs were collected from 3.2.0.29 version which boots successfully

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1093217/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Abhishek Ellore Sreenath (abhishek-es)]

Additional Info : I have a Lenovo Thinkpad with an Intel Core i7 and on board graphcs

[Dave Gilbert (ubuntu-treblig)]

Flipping to linux package since it's a kernel bug.

You'll be asked to record some logs; please do this on the kernel that does boot ok, and put a note on the end reminding people that it's the different version that fails

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1093217

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[Abhishek Ellore Sreenath (abhishek-es)]

apport information

[penalvch (penalvch)]

Abhishek Ellore Sreenath, 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. 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.8-rc1

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[penalvch (penalvch)]

Abhishek Ellore Sreenath, thank you for testing the mainline kernel. The next step is to perform a Ubuntu kernel commit bisect from 3.2.0.29 to 3.2.0.30, in order to identify the last good Ubuntu kernel commit, followed immediately by the first bad one.

Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Stanie (stanson1)]

I have no time to do kernel bisection - just adding a small info.

I also have Lenovo Z580 (Intel Core i5 with Ivybridge & NVIDIA GeForce GT 635M with CUDA)
But there seems to be a slight difference. I use Ubuntu 12.04 64b (not i386).
I have tried ubuntu 12.10 and 13.04 (both 64b), but no change. Quantal runs well only in live mode and Raring is a no go - won't even start live mode.

When I choose i386 version instead of amd64, there is no problem with blank screen or not booting into either of them at all. But that is not my preference.

BTW this bug is only present in *buntu based distributions. No such troubles with a few distro based on Arch or Debian I have tried so far...

[Abhishek Ellore Sreenath (abhishek-es)]

I have faced this issue as well. 64 bit variant of Ubuntu does not boot for me either.

[penalvch (penalvch)]

Stanie, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
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 may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

Abhishek Ellore Sreenath, have you had a chance to see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093217/comments/28 ?

[Stanie (stanson1)]

Sorry for not being more "precise".
I have the same bug in ubuntu kernel as Abhishek Ellore Sreenath. That is why I added a little additional info instead of only clicking "This bug affects me as well". No need to file a new report...

[Tom Thompson (tom2460)]

I believe the problematic kernels do actually boot. It just takes 12 to 13 minutes. dmesg shows several 120 second timeouts. Here is an excerpt that shows the final timeout and then (presumably) the error that is related to the hang.

<pre>
[ 840.304049] INFO: task swapper/0:1 blocked for more than 120 seconds.
[ 840.304052] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 840.304054] swapper/0 D ffffffff81806240 0 1 0 0x00000000
[ 840.304058] ffff880118301e80 0000000000000046 0000000000000000 ffff880114537040
[ 840.304061] ffff880118301fd8 ffff880118301fd8 ffff880118301fd8 00000000000137c0
[ 840.304065] ffff880117c19700 ffff8801182f8000 ffff880118301e70 0000000000000009
[ 840.304068] Call Trace:
[ 840.304074] [<ffffffff8165b50f>] schedule+0x3f/0x60
[ 840.304078] [<ffffffff81092df5>] async_synchronize_cookie_domain+0x75/0x120
[ 840.304082] [<ffffffff8108bd20>] ? add_wait_queue+0x60/0x60
[ 840.304085] [<ffffffff81092ef7>] async_synchronize_full+0x17/0x20
[ 840.304090] [<ffffffff81641107>] init_post+0xe/0xc5
[ 840.304094] [<ffffffff81cfcd74>] kernel_init+0x164/0x164
[ 840.304098] [<ffffffff81667b74>] kernel_thread_helper+0x4/0x10
[ 840.304101] [<ffffffff81cfcc10>] ? start_kernel+0x3bd/0x3bd
[ 840.304104] [<ffffffff81667b70>] ? gs_change+0x13/0x13
[ 947.952877] ACPI Error: Method parse/execution failed [\_SB_.WADR] (Node ffff880118260028), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952891] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UPBI] (Node ffff880118260258), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952898] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIF] (Node ffff880118260208), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952906] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BIF (20110623/battery-419)
[ 947.952909] ACPI: Battery Slot [BAT1] (battery present)
[ 947.954127] Freeing unused kernel memory: 924k freed
[ 947.954237] Write protecting the kernel read-only data: 12288k
</pre>

This is with 3.2.0-36-generic #57-Ubuntu SMP Tue Jan 8 21:44:52 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

[Dave Gilbert (ubuntu-treblig)]

Abhishek and anyone else, given Tom's post, can you all try and leave it for 15mins or so and see if it eventually boots,
if so please include a dmesg from the successful boot.

Tom: What hardware exactly are you running on and bios version ( dmesg|grep -i DMI should give us that info).

[Tom Thompson (tom2460)]

DMI info from dmesg:

[ 0.000000] DMI 2.7 present.
[ 0.000000] DMI: LENOVO IdeaPad Z580 /Lenovo , BIOS 5FCN89WW 08/27/2012

It has i3-3110M CPU @ 2.40GHz and Intel Integrated Graphics.

Some numbers associated with the model are 59345252 and 20135.

[penalvch (penalvch)]

Tom Thompson, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

As is already discussed in the links above, this will help by allowing us to analyze your hardware.

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

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

Thank you for your understanding.

[Abhishek Ellore Sreenath (abhishek-es)]

Hi,

I did try this out and saw that it does boot, albeit after a long time.

Here is the repeated stack trace I saw:

241.600106] Call Trace:
[ 241.600112] [<c1036a98>] ? default_spin_lock_flags+0x8/0x10
[ 241.600115] [<c1036a98>] ? default_spin_lock_flags+0x8/0x10
[ 241.600119] [<c15a84bd>] ? _raw_spin_lock_irqsave+0x2d/0x40
[ 241.600121] [<c15a68b5>] schedule+0x35/0x50
[ 241.600124] [<c1081015>] async_synchronize_cookie_domain+0xb5/0x130
[ 241.600128] [<c10c5572>] ? call_rcu_sched+0x12/0x20
[ 241.600131] [<c107a0e0>] ? add_wait_queue+0x50/0x50
[ 241.600133] [<c10810ea>] async_synchronize_full+0x1a/0x20
[ 241.600136] [<c158f594>] init_post+0x10/0xae
[ 241.600139] [<c18798e3>] kernel_init+0x15b/0x15b
[ 241.600141] [<c1879788>] ? start_kernel+0x353/0x353
[ 241.600144] [<c15afcfe>] kernel_thread_helper+0x6/0x10

My BIOS version :
[ 0.000000] DMI 2.7 present.
[ 0.000000] DMI: LENOVO IdeaPad Z580 /Lenovo , BIOS 5FCN34WW 06/11/2012
[ 1698.204135] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0

[Dave Gilbert (ubuntu-treblig)]

Hi Abhishek,
  OK - that's good; and for added fun you have the same hardware as Tom (Ideapad Z580); can you include the full output of dmesg after that slow boot please.

Dave

[Abhishek Ellore Sreenath (abhishek-es)]

dmesg after successful boot:

[Dave Gilbert (ubuntu-treblig)]

OK, so in the dmesg we see the following;

[ 4.153751] usb 3-3: new high-speed USB device number 2 using xhci_hcd
[ 4.521320] usb 1-1.3: new high-speed USB device number 3 using ehci_hcd
[ 241.600057] INFO: task swapper/0:1 blocked for more than 120 seconds.
[ 241.600063] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 241.600067] swapper/0 D f690e000 0 1 0 0x00000000
[ 241.600074] f749df64 00000046 f690e000 f690e000 00000000 f759cc20 c1931e00 c1931e00
[ 241.600085] db45b94e 00000000 f7bb9e00 f74a0000 f759cc20 019ff37b 00000004 f690e001
[ 241.600102] 00000000 ef804080 ef8e22a0 00000001 00000004 00000000 f749df40 c1036a98
[ 241.600106] Call Trace:
[ 241.600112] [<c1036a98>] ? default_spin_lock_flags+0x8/0x10
[ 241.600115] [<c1036a98>] ? default_spin_lock_flags+0x8/0x10
[ 241.600119] [<c15a84bd>] ? _raw_spin_lock_irqsave+0x2d/0x40
[ 241.600121] [<c15a68b5>] schedule+0x35/0x50
[ 241.600124] [<c1081015>] async_synchronize_cookie_domain+0xb5/0x130
[ 241.600128] [<c10c5572>] ? call_rcu_sched+0x12/0x20
[ 241.600131] [<c107a0e0>] ? add_wait_queue+0x50/0x50
[ 241.600133] [<c10810ea>] async_synchronize_full+0x1a/0x20
[ 241.600136] [<c158f594>] init_post+0x10/0xae
[ 241.600139] [<c18798e3>] kernel_init+0x15b/0x15b
[ 241.600141] [<c1879788>] ? start_kernel+0x353/0x353
[ 241.600144] [<c15afcfe>] kernel_thread_helper+0x6/0x10

and then we get the repeating hang messages every 120 seconds or so until:
[ 1319.994057] [<c1879788>] ? start_kernel+0x353/0x353
[ 1319.994059] [<c15afcfe>] kernel_thread_helper+0x6/0x10
[ 1672.348773] ACPI Error: Method parse/execution failed [\_SB_.WADR] (Node f74348a0), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 1672.348785] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UPBI] (Node f74349f0), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 1672.348812] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIF] (Node f74349c0), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 1672.348820] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BIF (20110623/battery-419)

which matches what Tom saw (although yours took a bit longer).

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 106855
DSDT

For the past few releases of almost all popular Linux-based distributions, users of Lenovo's Z580 laptop have been noticing that past a particular kernel version (usually a certain build of 3.2), the boot would seem to hang. In reality, the boot would eventually complete, though after 15-20 minutes (or more in extreme cases). Looking at dmesg output of boots that hung but eventually finished, three ACPI timeouts are reported (120s infinite loop timeout in BIOS).

Testing of this bug on my end took place on Ubuntu 12.04 LTS and Fedora 19, running mainline builds (unmodified mainline tree sources with distribution kernel configurations). However, users of Fedora, Arch, Mint, and Gentoo report similar issues both with distribution and mainline kernels.

Ubuntu Bug Report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093217

From the dmesg output, it was found that booting without the battery physically installed was always successful. Later inserting the battery after boot had no adverse consequences. Furthermore, compiling a kernel without battery support (either not at all or as a module later blacklisted on the command line) would also produce successful boots.

dmesg from above showing impacted area:

[ 840.304049] INFO: task swapper/0:1 blocked for more than 120 seconds.
[ 840.304052] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 840.304054] swapper/0 D ffffffff81806240 0 1 0 0x00000000
[ 840.304058] ffff880118301e80 0000000000000046 0000000000000000 ffff880114537040
[ 840.304061] ffff880118301fd8 ffff880118301fd8 ffff880118301fd8 00000000000137c0
[ 840.304065] ffff880117c19700 ffff8801182f8000 ffff880118301e70 0000000000000009
[ 840.304068] Call Trace:
[ 840.304074] [<ffffffff8165b50f>] schedule+0x3f/0x60
[ 840.304078] [<ffffffff81092df5>] async_synchronize_cookie_domain+0x75/0x120
[ 840.304082] [<ffffffff8108bd20>] ? add_wait_queue+0x60/0x60
[ 840.304085] [<ffffffff81092ef7>] async_synchronize_full+0x17/0x20
[ 840.304090] [<ffffffff81641107>] init_post+0xe/0xc5
[ 840.304094] [<ffffffff81cfcd74>] kernel_init+0x164/0x164
[ 840.304098] [<ffffffff81667b74>] kernel_thread_helper+0x4/0x10
[ 840.304101] [<ffffffff81cfcc10>] ? start_kernel+0x3bd/0x3bd
[ 840.304104] [<ffffffff81667b70>] ? gs_change+0x13/0x13
[ 947.952877] ACPI Error: Method parse/execution failed [\_SB_.WADR] (Node ffff880118260028), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952891] ACPI Error: Method parse/execution failed [\_SB_.BAT1.UPBI] (Node ffff880118260258), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952898] ACPI Error: Method parse/execution failed [\_SB_.BAT1._BIF] (Node ffff880118260208), AE_AML_INFINITE_LOOP (20110623/psparse-536)
[ 947.952906] ACPI Exception: AE_AML_INFINITE_LOOP, Evaluating _BIF (20110623/battery-419)
[ 947.952909] ACPI: Battery Slot [BAT1] (battery present)
[ 947.954127] Freeing unused kernel memory: 924k freed
[ 947.954237] Write protecting the kernel read-only data: 12288k

Specifically, this bug has been reported to appear sometime between 3.2 and 3.3, though the exact commit is unknown. Some temporary workarounds have been proposed, both on the Ubuntu tracker a...

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 106856
DSDT.aml

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 106857
DSDT.dsl

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 106858
DSDT.dsl.orig

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 106859
DSDT.dsl.diff

[aaron.lu (aaron.lu-linux-kernel-bugs)]

Add Zheng Lv.

In the meantime, it would be good if someone can do the bisect to find the offending commit.

[lv.zheng (lv.zheng-linux-kernel-bugs)]

From the DSDT, we can see that all BYFG accesses are invoked inside _BIF method.
I just wonder how _BIF method is invoked by the OSPM.
We may need to investigate to see the bisect result first.

[sduddikunta (sduddikunta-linux-kernel-bugs)]

After further testing, this bug may not be a regression. Because of the nature of the problem, boots even with bad kernels often don't hang. However, in the recent testing I did, I found that versions dating back to 3.0 (including the previously thought good 3.2) also exhibited the issue. I'll continue to test versions prior to 3.0.

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Attempted to test 2.6.39 and 2.6.38; my system does not boot either one. It's not that they hang the same way the 3.x kernels do, the kernel doesn't load at all. I get no output to the screen. There is no indication of anything happening.

[aaron.lu (aaron.lu-linux-kernel-bugs)]

Please attach acpidump like this:
# acpidump > acpidump.txt

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Created attachment 107191
acpidump.txt

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Has there been any progress on this? There is still active discussion on the Ubuntu bug tracker with no true workarounds or fixes yet.

[lv.zheng (lv.zheng-linux-kernel-bugs)]

Have you tested the kernel with an ACPICA fix that has filled a gap for operation region fields?

The commit is:
Commit 4be4be8fee2ee99a52f94f90d03d2f287ee1db86
Author: Bob Moore <email address hidden> 2013-09-06 06:27:15 (GMT)
Subject: ACPICA: Fix for a Store->ArgX when ArgX contains a reference to a field.

Which is shipped in the mainline kernel tagged as 3.12-rc2.

This bug seems to be a duplicate of the issue fixed by this commit.

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Thanks for the response. I just installed the Ubuntu mainline 3.12-rc2 build, and initial testing seems to be showing good results. I've asked the folks on the Ubuntu tracker for additional help in testing, and I'll report back once we're done.

[aaron.lu (aaron.lu-linux-kernel-bugs)]

Anything new about the test?

[sduddikunta (sduddikunta-linux-kernel-bugs)]

Sorry about the delay. The new kernel does not fix the bug. Myself and a few on the Ubuntu tracker have found that it still exhibits the same occasional, seemingly random issues with the infinite loop.

[Siddu (sduddikunta)]

I'm not sure about DKMS, but if you don't have any special kernel modules
like Virtualbox or proprietary NVIDIA drivers, you should be okay. No new
entry should appear in grub.

[Jacob Cram (cramjaco)]

Excellent. So far no problems then. I do run virtualbox but "sudo /etc/init.d/vboxdrv setup" seemed sufficient to get that working again.

[Jochen Fahrner (jofa)]

What is the advantage of a patched kernel over a patched DSDT (as described in comment #160), which works with ANY kernel?

[Siddu (sduddikunta)]

The patched dsdt is actually not guaranteed to work. I've had instances
where it didn't. That patch attempts to fix what's seems to be a race
condition by adding a delay to the relevant function. But with all timing
workarounds, it won't always work. The kernel patch will always work,
because battery support simply isn't available until late in the boot
process, where it can't do any harm.

[Jochen Fahrner (jofa)]

Maybe this race condition is also an issue on other platforms. I'm wondering why my Acer Aspire One 521 netbook often hangs on reboot. Powerup is fine, but reboot often does not boot. Could be the same problem.

[Dave Gilbert (ubuntu-treblig)]

Jochen: Please open a separate bug for your Acer; this one mostly seems to be pretty specific to this hardware.

[lv.zheng (lv.zheng-linux-kernel-bugs)]

Hi,

The WAEC method has created a named object inside of it:

        Method (WAEC, 0, NotSerialized)
        {
            Name (CUNT, 0x1E)
            While (LNotEqual (^PCI0.LPCB.EC0.BYFG, Zero))
            {
                Sleep (0x05)
                Decrement (CUNT)
                If (LEqual (CUNT, Zero))
                {
                    Store (Zero, ^PCI0.LPCB.EC0.BYFG)
                    Store (Zero, ^PCI0.LPCB.EC0.DRFG)
                    Break
                }
            }
        }

So this looks like a method should be marked as Serialized.
Recently we have fix shipped in the Linux upstream to automatically marking control methods as Serialized.

Could you give it try?

1. Please download and checkout the git repo that this series is based on (linux-pm/linux-next branch):
   # git clone https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
   # git checkout -b linux-next --track origin/linux-next
2. Please boot the kernel without DSDT customized.

Thanks in advance.

[sduddikunta (sduddikunta-linux-kernel-bugs)]

I will test and report back in a few days.

[sduddikunta (sduddikunta-linux-kernel-bugs)]

This does not fix the bug. The same condition is seen: a seemingly randomly occurring hang. I also noticed that my computer was unable to shut down via the usual channels with this kernel. It would halt but not power off.

[lv.zheng (lv.zheng-linux-kernel-bugs)]

OK, Let's do some basic debugging.

1. Please use the v3.14-rc5 kernel (it is linus/master branch);
2. Please apply the following patches:
    attachment 129031 [details]
    attachment 129041 [details]
    attachment 129051 [details]
    attachment 129061 [details]
    attachment 129071 [details]
3. Boot the kernel with "acpi.debug_layer=0x000000E4 acpi.debug_level=0x00000010 acpi_trace_once=_SB_.BAT1._BIF";
4. Post dmesg here.

Let's first track what has been executed in this case.

Thanks in advance.

[Matthew Pray (matthewpray1)]

Does using something like coreboot to replace the BIOS fix this problem? How about supergrubdisc?

[Jacob Cram (cramjaco)]

I have been running Siddhu's patched kernal for the last few months and I have occasionally (maybe 2x/week) been experiencing whole system freezes. Everything on the screen stops moving or responding. I don't know if this is a problem with that particular kernal or something else (I haven't controlled for all the system changes I have made), but it wasn't a problem with other kernals. Has anyone else experienced this pattern?

[Siddu (sduddikunta)]

I haven't experienced it. Are you running any graphics kernel modules, such
as the NVIDIA or AMD proprietary drivers? What version of Ubuntu are you
on? I recall that such a bug used to exist in the Intel Graphics Stack for
Ivy Bridge GPUs, but it has since been fixed. I'm not quite sure which
kernel version the fix was released with, but I think that Precise is still
affected.

[Matthew Pray (matthewpray1)]

Has anyone tried out Ubuntu 14.04?

I have recently tried Manjaro, and then a full Arch Install on my Lenovo z580. Both successfully boot without any modifications. I'll keep an eye out here in the mean time, in hopes that this gets resolved.

[Siddu (sduddikunta)]

14.04 has the same issue. I've since installed arch on a separate LV, and
I'm intending on switching to it as soon as it get it with all the software
and whatnot installed.

[Jon Baca (jtbaca001)]

The only way I have been able to get the patched DSDT to work is to build it into the kernel. This is less than ideal but will allow you to use your computer. If you have been unable to get a patched DSDT to work, this should work for you. I am currently running 14.04 with a custom kernel build. The following should work with other kernel versions as well. I am only posting the steps exactly as I performed them, so if version number etc don't match for you, you are on your own.

1) Install Ubuntu 14.04. If you have to, just pull out your battery and complete the installation. Just leave it out until we are finished.

2) Compile your custom DSDT - this should produce a DSDT.hex file that you will need for incorporation into the kernel.
sudo iasl -tc DSDT.dsl

3) Get the source:
sudo apt-get source linux-image-3.13.0-24-generic

4) Untar the source:
gzip -cd linux_3.13.0.orig.tar.gz | tar xvf -

5) Move into the directory that contains the kernel source code and apply the patch:
cd linux-3.13/
gzip -cd ~/linux_3.13.0-24.47.diff.gz | patch -p1

6) Get the required tools to build the kernel
sudo apt-get install git-core libncurses5 libncurses5-dev libelf-dev asciidoc binutils-dev linux-source qt3-dev-tools libqt3-mt-dev libncurses5 libncurses5-dev fakeroot build-essential crash kexec-tools makedumpfile kernel-wedge kernel-package gcc

7) Configure the kernel for compilation:
make menuconfig

When the menu comes up navigate to Power Management and ACPI options -> ACPI
In the field "Custom DSDT Table file to include" enter the path to your DSDT.hex file which for me was /home/DSDT.hex

Now navigate to General Setup (you will have to go back to the main menu)
In the field "Local Version" enter "-custom-dsdt"

Now navigate to Device Drivers -> Generic Driver Options
Deselect the field "Prevent Firmware from being built"

Select save at the bottom, accept the default file name and exit

8) Build the kernel:
sudo make -j3 deb-pkg

At this point, just walk away from you computer. Come back every so often to check on the progress but the build will probably take a couple of hours(depending on your system). Try to resolve it and retry building the kernel

9) Install the kernel:
sudo dpkg -i linux-image-3.13.9-custom-dsdt_3.13.9-custom-dsdt-4_amd64.deb

This will install the new kernel. If it completes successfully, reboot your system. The default grub option should now be your new kernel. You can verify the custom DSDT is loaded in dmesg and you should see your custom version number with the "uname -r" command. If all goes well power off your computer, reinstall your battery, and boot your computer up.

Let me know if I missed anything and good luck.

[Jon Baca (jtbaca001)]

Sorry, end of 8 was supposed to say if you encounter any errors, try to resolve them and retry building the kernel.

[rui.zhang (rui.zhang-linux-kernel-bugs)]

<email address hidden>, any update on this?

[lv.zheng (lv.zheng-linux-kernel-bugs)]

Hi, Rui

This bug is a valid report.
All information needed are uploaded here.
It reflects a gap in ACPICA interpreter.
We just don't have time working on it.
There are 2 ACPICA releases queued up for 3.16 and some urgent issues are handled this Q.

Thanks

[rui.zhang (rui.zhang-linux-kernel-bugs)]

Do we have a patch that has been verified to fix this?
If no, we need one, and I think this is what you want to do in comment #19, no?

[lv.zheng (lv.zheng-linux-kernel-bugs)]

No(In reply to Zhang Rui from comment #22)
> Do we have a patch that has been verified to fix this?
> If no, we need one, and I think this is what you want to do in comment #19,
> no?

You are right.
I confused this bug to another.

That kind of logging message could be useful.

Thanks

[lv.zheng (lv.zheng-linux-kernel-bugs)]

Closing since no response.
You can re-open it if you still suffer from the same issue in the recent kernel.

[Tommy_CZ (t-kijas)]

It seems to be resolved, right?

[tomplatz567 (tomplatz567-linux-kernel-bugs)]

Created attachment 283621
118