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).

[Stanie (stanson1)]

Here's my two cents:

dmesg|grep -i DMI
[ 0.000000] DMI 2.7 present.
[ 0.000000] DMI: LENOVO IdeaPad Z580 /Lenovo , BIOS 5FCN35WW 08/03/2012
[ 21.308809] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[ 21.308938] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11

Enclosed you will find the whole dmesg output with ubuntu kernel 3.2.0-37-generic after successfull boot (closer to 20 min!)

[Tom Thompson (tom2460)]

If the battery is removed from the laptop, then it will boot and reboot normally in a few seconds.

Another observation is that after the slow boot, the line "ACPI: Battery Slot [BAT1] (battery present)" shows up twice in dmesg. Once early on and again after the timeouts and AE_AML_INFINITE_LOOP ACPI exception. But with the battery removed the line "ACPI: Battery Slot [BAT1] (battery absent)" appears twice and only separated by a millisecond or so.

I see there was a change to drivers/acpi/battery.c between 3.0.29 and 3.0.35. See http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.0.34

[Stanie (stanson1)]

Tom's right - the laptop boots normally without the battery...

[Tom Thompson (tom2460)]

My mention of the change to battery.c was actually between ubuntu kernels 3.2.0-29 and 3.2.0.30 (ref browsing kernel.ubuntu.com/git) . I'm not qualified on determining if it is related to problem -- it is just as likely coincidence as far as I know but I did want to correct the misleading version numbers I posted before.

[Abhishek Ellore Sreenath (abhishek-es)]

Since we have so much more information for this bug, thanks to Tom and Stanie, could we move this bug to Confirmed and expect to get a fix as soon as possible ?

[Dave Gilbert (ubuntu-treblig)]

Tom/Abishek/Stanie: Can either of you try to follow the bisection instructions Christopher asked for in #28; but if you can do it and confirm it's the commit that Tom mentions in #44 then that would nail it down.

[Dave Gilbert (ubuntu-treblig)]

Also, since this loops like it's ACPI related please provide the information shown in the bug filing section of :

https://wiki.ubuntu.com/DebuggingACPI

and also try booting with the various ACPI boot options to see if it goes away.

Dave

[Chris Hyatt (n3twrkm4n-deactivatedaccount)]

Lenovo IdeaPad Z580 with Core i5. In kernel 3.5.0-17 I was able to boot with acpi=force but after upgrade to 3.5.0-23 that ability disappeared. Instead I can not boot the kernel with acpi=ht successfully.

This is for Dave Gilbert above as he requested ACPI options testing. I didn't provide my Debugging ACPI script output since I had mostly disabled ACPI. Let me know if you need anything else, I can revert and get copies of the data as needed.

[Chris Hyatt (n3twrkm4n-deactivatedaccount)]

^ my mistake... I meant to say I CAN boot the kernel with acpi=ht in the boot string. And it boots quickly.

[Abhishek Ellore Sreenath (abhishek-es)]

I was able to boot with acpi=noacpi noot parameter.
On trying other options, I found that I was unable to boot with acpi=ht
But was able to boot with pci=noacpi

[Abhishek Ellore Sreenath (abhishek-es)]

Output of commands from ACPI debugging.
I was unable to copy the /var/acpi directory as it was in user

[Abhishek Ellore Sreenath (abhishek-es)]

Kernel log after hibernate+restart

[Tom Thompson (tom2460)]

I did a bisection and found the point where the long boot started happening:

ca2281b Prevent interface errors with Seagate FreeAgent GoFlex {BAD}
cf1ed4a Fix a dead loop in async_synchronize_full() {GOOD}

There are a couple of puzzling things.

First this good to bad point is between Ubuntu-3.2.0-32.51 and Ubuntu-3.2.0-33.52. Either Ubuntu 3.2.0-30 is not affected or there are multiple places that would go from good to bad and the bisect methodology caused them to be skipped over.

When bisection started hovering around the "Fix a dead loop in async_synchronize_full()" commit I thought it would be the culprit since the stack traces in dmesg show it is stuck in/near this code. However, the version with this change works and it is the one right after it that fails.

The messages about AE_AML_INFINITE_LOOP start appearing at a different point. When they start occurring the boot time is still normal. The INIFINITE_LOOP messages show up in dmesg a couple minutes after boot. I did not fully bisect this but did make 3 kernels near a point where it went from no INFINITE_LOOP message to one.

3001d0d mm: mmu_notifier: fix freed page still mapped in secondary MMU {has INIFINITE_LOOP}
fef5d62 mm: setup pageblock_order before it's used by sparsemem
6c9bb2e mm/page_alloc.c: remove pageblock_default_order()
f00167c ASoC: wm8962: Allow VMID time to fully ramp {no INF_LOOP}
661696d USB: echi-dbgp: increase the controller wait time to come out of halt.
426561c ARM: Fix undefined instruction exception handling
310f418 ARM: 7478/1: errata: extend workaround for erratum #720789 {no INF_LOOP}

But the funny thing is the kernel at commit cf1ed4a ({GOOD} above) does has neither the long timeout problem nor the INIFINITE_LOOP problem.

[Dave Gilbert (ubuntu-treblig)]

Triaged: Upstream has been tested, and a bisect tried.

Tom, thanks for trying that bisect; I'll leave it to others to try and figure out where it's going.

Can you provide the copy of /proc/acpi (as detailed on https://wiki.ubuntu.com/DebuggingACPI )

Dave

[Tom Thompson (tom2460)]

Here is /proc/acpi from 3.2.0-37

[Tom Thompson (tom2460)]

I made a kernel from the Ubuntu-3.2.0-35.55 sources except two commits had been undone. These were

ca2281b Prevent interface errors with Seagate FreeAgent GoFlex
cf1ed4a Fix a dead loop in async_synchronize_full()

It did not have the slow boot problem.

I've seen that some small percent of the time, a "slow boot" kernel will boot normally. Thus in testing I've been trying any normal boot more than once to make sure I just didn't get lucky. I think this is around 3-5% of the time.

[Abhishek Ellore Sreenath (abhishek-es)]

What are the next steps for this bug ?

[Tom Thompson (tom2460)]

I built a stock linux kernel from the latest at kernel.org (3.9.0-rc1) and it has the same slow boot problem. One time I booted in recovery mode and it was actually quick. I will report if this is consistent or just a fluke after more trials. But in normal mode it is slow, about 20 minutes, and dmesg looks similar to the other cases.

I followed the instructions at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild. I did not do the optional 4 steps listed at the bottom of that web page that make the kernel more Ubuntu-like.

[Tommy_CZ (t-kijas)]

In my opinion, the problem was in bumblebee 3.0. Without this and with disabled NVIDIA card in BIOS, I could boot and boot times were varying from fast to slow but I always boot. With bumblebee 3.0 I was unable to boot in most cases.
With bumblebee 3.1 with primus support enabled it seems OK but it needs aditional testing.
Ubuntu 12.10 64bit
Lenovo Z580

[Abhishek Ellore Sreenath (abhishek-es)]

I do not think it is bumbleebee. My laptop has Intel Integrated graphics

[Tommy_CZ (t-kijas)]

Only intel graphic card? Because my computer (Lenovo Z580) has intel integrated gpu and nvidia gpu too (GT 630 I think?)

[Abhishek Ellore Sreenath (abhishek-es)]

Yes, Mine has Intel graphics card only . My model is Z580 (Moden Name 2151)

[Tom Thompson (tom2460)]

Here is a possible workaround.

After reading up some on ACPI, I decided it was that the system got stuck in the BIOSs’ ACPI code. This is what the error message showed and I also came to the (possibly wrong) conclusion that this error was there all along and other kernel changes actually fixed something else that made async accesses to the ACPI functions “proper”. But for us Z580 users it created the long delay waiting for the AML interpreter to determine that the BIOS was hung.

So I got the iasl tool, decompiled, changed and recompiled the DSDT, then used grub to load the changed version before loading the kernel. It worked and now there is no delay with this workaround.

The change I made was in DSDT method WAEC (wait on embedded controller?). Here is the method along with the one line fix:

        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
                }
            }
            Sleep (50) // #### adding this line is the only change ####
        }

When getting battery info, this method is used 3 times. It is called just before commanding the EC to return a different piece of battery info. Since battery info is fetched twice for some reason, this only adds about 300 milliseconds (a lot better than 20 minutes).

Here are the approximate steps I used:

Install the ASL compiler iasl (apt-get install iasl I think).

Make a copy of /sys/firmware/acpi/tables/DSDT

isal -d DSDT to decompile to DSDT.dsl

[Compile to aml and you see two differences, the version number of the compiler is different]

Edit the change into DSDT.dsl

iasl DSDT.dsl to produce DSDT.aml

sudo cp DSDT.aml /boot/.

Reboot and enter ‘c’ at the grub menu, then enter “acpi /boot/DSDT.aml”, then escape and boot (I am using 3.2.0-38-generic).

Then I edited /boot/grub/grub.cfg and put the acpi command in there. An approach that works even with upgrades is described by Michael Kuron at http://blog.michael.kuron-germany.de/2011/03/patching-dsdt-in-recent-linux-kernels-without-recompiling/

I just guessed on where to put the delay. I thought it must be a race or timing issue and I planned to shotgun delays everywhere, but got lucky and the first one worked. Someone else may be able to determine if there is a better fix.

By the way, you can confirm the DSDT is loaded from the line in dmesg:
[ 0.000000] ACPI: DSDT 00000000d82bc1f0 0AD5B (v02 LENOVO IVB-CPT 00000000 INTL 20100528)
The original has 20061109 I think.

Another thing I tried that did NOT help the problem was adding acpi_serialize to kernel boot options.

[Tom Thompson (tom2460)]

This DSDT fix also works in the recent kernel.org kernel (3.9.0-rc1). With the fix that kernel boots fast and the battery is recognized. (Not only did it boot slow without the fix, the battery was not detected).

[Abhishek Ellore Sreenath (abhishek-es)]

I am not sure why this bug is still unassigned.
Tom has gone as far as testing a possible fix. I suppose this issue is affecting other Lenovo Ideapad users as well.

Could someone please look into it and release a fix to the mainline so that we would not have to make those changes ourself.

[Tommy_CZ (t-kijas)]

Bumblebee is unrelated as you said, last boot took 1 hour. Second never ends. Third was succesful.
I can completely agree with #65

[vince (vincent-typerrr)]

Tom,
first of all I think you made a small typo: instead of isal -d DSDT it should be iasl -d DSDT
and secondly, the command doesn't work it says:
Could not open input file DSDT
if I try sudo iasl -d /sys/firmware/acpi/tables/DSDT it says:
Could not get table from the file

[Tom Thompson (tom2460)]

Vince
Yes there was a typo and iasl is the correct word.
As far as the other problem I am not near my system right now to try it. The only difference I can think of is I first copied /sys/firmware/acpi/tables/DSDT to another directory and then used that copy as the argument for the "iasl -d" command.

[Jacob Cram (cramjaco)]

Really sorry, I accedentally set the status to fix released and now I can't undo my action. Actually I have a related problem to this and would also like this fixed. Sorry again.

[Dave Gilbert (ubuntu-treblig)]

I've put this back to Triaged.

[nozyczek (nozyczek)]

Tom,
I would like to thank you for taking the time and documenting your findings and the workaround. I was able to successfully apply this DSDT workaround to my LinuxMint installation.
I'm hopping to see official fix soon.
Thanks again.

My distro and specs for anyone who is interested.

-->cat /etc/lsb-release
DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=14
DISTRIB_CODENAME=nadia
DISTRIB_DESCRIPTION="Linux Mint 14 Nadia"

-->uname -a
Linux z580 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

-->dmesg | grep " DMI"
[ 0.000000] DMI 2.7 present.
[ 0.000000] DMI: LENOVO IdeaPad Z580 /Lenovo , BIOS 5FCN89WW 08/27/2012

-->sudo lshw -short -sanitize
H/W path Device Class Description
=====================================================
                           system IdeaPad Z580 (System SKUNumber)
/0 bus Lenovo
/0/0 memory 128KiB BIOS
/0/4 processor Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz
/0/4/6 memory 32KiB L1 cache
/0/4/7 memory 256KiB L2 cache
/0/4/8 memory 3MiB L3 cache
/0/5 memory 32KiB L1 cache
/0/36 memory 6GiB System Memory
/0/36/0 memory 4GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/36/1 memory 2GiB SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
/0/100 bridge 3rd Gen Core processor DRAM Controller
/0/100/2 display 3rd Gen Core processor Graphics Controller
/0/100/14 bus 7 Series/C210 Series Chipset Family USB xHCI Host Controller
/0/100/16 communication 7 Series/C210 Series Chipset Family MEI Controller #1
/0/100/1a bus 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2
/0/100/1b multimedia 7 Series/C210 Series Chipset Family High Definition Audio Controller
/0/100/1c bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 1
/0/100/1c.1 bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 2
/0/100/1c.1/0 eth0 network RTL8101E/RTL8102E PCI Express Fast Ethernet controller
/0/100/1c.2 bridge 7 Series/C210 Series Chipset Family PCI Express Root Port 3
/0/100/1c.2/0 wlan0 network Centrino Wireless-N 2200
/0/100/1d bus 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1
/0/100/1f bridge HM76 Express Chipset LPC Controller
/0/100/1f.2 storage 7 Series Chipset Family 6-port SATA Controller [AHCI mode]
/0/100/1f.3 bus 7 Series/C210 Series Chipset Family SMBus Controller
/0/1 scsi0 storage
/0/1/0.0.0 /dev/sda disk 120GB KINGSTON SV300S3
/0/1/0.0.0/1 /dev/sda1 volume 111GiB EXT4 volume
/0/2 scsi2 storage
/0/...

[vince (vincent-typerrr)]

For me the problem hasn't occured while using ubuntu 13.04
Can someone confirm me that the problems are fixed in 13.04?

[vince (vincent-typerrr)]

Ignore my last comment, it turned out it didn't fix it, i just was lucky the first few boots

[Jacob Cram (cramjaco)]

Vince, Interesing you should mention that you had a "lucky first few" boots. I have noticed with my set-up that often, when I get a new kernal version, I am often able to boot ok the first one or two times before the slow boot times kick in.

[Jacob Cram (cramjaco)]

I just tried applying Tom's workaround. Unfortunately, it seems to have no effect on my boot time.

Further information:
I'm running Ubuntu 12.04 on a Lenovo Z580
Decompiling DSDT works fine.
I made the modification no problem.
When I recompiled, I got some warning messages, I'll attach the output from that below.
running "acpi /boot/DSDT.aml" does not give error messages (or return anything for that matter)
booting linux then takes about 17 minutes

I'd love to hear if anybody has other suggestions.
I'm happy to provide any additional information.
Thanks.

Intel ACPI Component Architecture
ASL Optimizing Compiler version 20100528 [Oct 15 2010]
Copyright (c) 2000 - 2010 Intel Corporation
Supports ACPI Specification Revision 4.0a

DSDT.dsl 5011: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 5094: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 5177: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 5260: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 5511: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 5594: Name (_T_0, Zero)
Remark 5111 - Use of compiler reserved name ^ (_T_0)

DSDT.dsl 7351: Name (_T_1, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_1)

DSDT.dsl 7352: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)

DSDT.dsl 11008: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)

DSDT.dsl 11068: Name (_T_6, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_6)

DSDT.dsl 11069: Name (_T_5, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_5)

DSDT.dsl 11070: Name (_T_4, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_4)

DSDT.dsl 11071: Name (_T_3, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_3)

DSDT.dsl 11072: Name (_T_2, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_2)

DSDT.dsl 11073: Name (_T_1, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_1)

DSDT.dsl 11074: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)

DSDT.dsl 11389: Name (_T_0, Zero)
Remark 5111 - ^ Use of compiler reserved name (_T_0)

DSDT.dsl 11561: Name (_VPC, Zero)
Warning 1099 - ^ Unknown reserved name (_VPC)

DSDT.dsl 11585: Method (_CFG, 0, NotSerialized)
Warning 1099 - Unknown reserved name ^ (_CFG)

DSDT.dsl 11585: ...

[nozyczek (nozyczek)]

Go to BIOS and change UEFI to Legacy and it will work.

[Tommy_CZ (t-kijas)]

No, it will not. I have it disabled, and the situation is the same. Sometimes it boot without problems, sometimes it doesn't.

[Tommy_CZ (t-kijas)]

Please can you change the title of this bug report to
" Ubuntu 12.04, 12.10 and 13.04 10-20min boot delay (From 3.2.0.29->3.8.0-19) " ?

[nozyczek (nozyczek)]

Can you confirm your modded DSDT gets loaded?

Here is Toms comment on this:
"By the way, you can confirm the DSDT is loaded from the line in dmesg:
[ 0.000000] ACPI: DSDT 00000000d82bc1f0 0AD5B (v02 LENOVO IVB-CPT 00000000 INTL 20100528)
The original has 20061109 I think."

[Jacob Cram (cramjaco)]

It looks like maybe the new DSDT is not loading.

dmsg line below:
[ 0.000000] ACPI: DSDT 00000000caff1000 0AD3E (v02 LENOVO IVB-CPT 00000000 INTL 20061109)

Is there a trick to get it to load?
I haven't tried changing UEFI to Legacy yet.

[nozyczek (nozyczek)]

It will load after you change to legacy.

[Tom Thompson (tom2460)]

The downside to setting legacy is that Windows cannot be loaded from the grub menu. The upside is that the little nuvo button next to the main power button on the Z580 makes it easy to get into the bios without having to hit DEL or F2 or something before a timeout. So to switch back to booting Windows, just powerdown and power up with the little nuvo button. A menu will allow you to enter the BIOS to turn UEFI back on.

Caveat - I installed Ubuntu with UEFI off and legacy enabled. Things may behave different if Ubuntu was installed with UEFI on.

[Jon Baca (jtbaca001)]

I successfully applied this fix to 12.10. Did you put add the acpi command to the grub.cfg file?

[Jon Baca (jtbaca001)]

Forgot to mention that I installed 12.10 in UEFI mode and am dual booting Windows8 from grub.

[Tom Thompson (tom2460)]

Yes I did, but I wanted the grub menu to still have the option to boot
without using the patched DSDT.

I put the patched DSDT in /boot/mydsdt.aml and changed
/etc/grub.d/10_linux per the diff/patch below. This was to 12.04 so
10_linux may be a little different in 12.10. I also have to watch out
for normal system updates of grub.

This adds another item to the menu and it is the first so it becomes the
default. This item is just like the normal linux non-recovery boot
except it first invokes grub's acpi command. The second menu item is
normal boot w/o acpi and the third is now recovery boot.

Let me know if something like this works with UEFI always enabled. In
my case I rarely run windows on the laptop so I just change the BIOS
back when I need to. Some of the other messages implied the DSDT could
not be loaded in UEFI mode.

The patch (made with "diff -c 10_linux.orig 10_linux" within /etc/grub.d):

*** 10_linux.orig 2012-12-10 06:20:08.000000000 -0600
--- 10_linux 2013-03-07 09:13:51.175997701 -0600
***************
*** 81,89 ****
--- 81,96 ----
     os="$1"
     version="$2"
     recovery="$3"
+ capi=false
+ if [ "xcustomacpi" = "x$recovery" ]; then
+ recovery="false"
+ capi="true"
+ fi
     args="$4"
     if ${recovery} ; then
       title="$(gettext_quoted "%s, with Linux %s (recovery mode)")"
+ elif ${capi} ; then
+ title="$(gettext_quoted "%s, with Linux %s (custom DSDT)")"
     else
       title="$(gettext_quoted "%s, with Linux %s")"
     fi
***************
*** 120,125 ****
--- 127,137 ----
         echo '$message'
   EOF
     fi
+ if ${capi} ; then
+ cat << EOF
+ acpi /boot/mydsdt.aml
+ EOF
+ fi
     if test -d /sys/firmware/efi && test -e "${linux}.efi.signed"; then
       cat << EOF
         linux ${rel_dirname}/${basename}.efi.signed
root=${linux_root_device_thisversion} ro ${args}
***************
*** 252,257 ****
--- 264,272 ----
       linux_root_device_thisversion=${GRUB_DEVICE}
     fi

+ linux_entry "${OS}" "${version}" "customacpi" \
+ "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_EXTRA}
${GRUB_CMDLINE_LINUX_DEFAULT}" \
+ quiet
     linux_entry "${OS}" "${version}" false \
         "${GRUB_CMDLINE_LINUX} ${GRUB_CMDLINE_EXTRA}
${GRUB_CMDLINE_LINUX_DEFAULT}" \
         quiet

The idea for this came from a similar approach at
http://blog.michael.kuron-germany.de/2011/03/patching-dsdt-in-recent-linux-kernels-without-recompiling/

Tom

On 4/21/2013 2:06 PM, Jon Baca wrote:
> I successfully applied this fix to 12.10. Did you put add the acpi
> command to the grub.cfg file?
>

[Jon Baca (jtbaca001)]

I am always booting in UEFI mode. I put the patched DSDT in the same location, but I edited /boot/grub/grub.cfg to include "acpi /boot/DSDT.aml" just before the linux and initrd load commands. This works for me on every boot. I am not at my computer right now, so if any of the info seems wrong I can double check it later, but it for sure works every time in UEFI mode.

[Tom Thompson (tom2460)]

Thats good and really the way you have it is all you need. I think you
might need to re-edit grub.cfg whenever the kernel or grub tools get
updated but that is not a big deal.
Tom

On 4/21/2013 3:11 PM, Jon Baca wrote:
> I am always booting in UEFI mode. I put the patched DSDT in the same
> location, but I edited /boot/grub/grub.cfg to include "acpi
> /boot/DSDT.aml" just before the linux and initrd load commands. This
> works for me on every boot. I am not at my computer right now, so if any
> of the info seems wrong I can double check it later, but it for sure
> works every time in UEFI mode.
>

[Jacob Cram (cramjaco)]

Thanks for the help so far everyone. I have a few questions:

Jon Baca: Could you please explain exactly where on grub.cfg you added the command, there seem to be a bunch of places where linux and initrd get referred to.

nozyczek: I seem to be having some trouble setting UEFI to legacy. I can go into setup by pressing F2 at the lenovo start screen and then tabbing over to Boot. I can then turn UEFI Boot from Enabled to disabled. Is this the right series of actions? If so, I am unable to start my computer with this setting.
I get to an alternate boot menu, but if I try to boot ubuntu or the hard disk a screen with some text flashes (too fast for me to read it, but it ends in "Exiting PXE ROM") and returns me to the boot menu screen.
Am I missing something?

[Tom Thompson (tom2460)]

Jacob, regarding setting UEFI to legacy ... When you toggle UEFI to disabled it creates another field in the form right below it. I cannot remember what it is called not what its default value is, but when you toggle it, it displays legacy.

[Jacob Cram (cramjaco)]

Hah, got it by editing grub.cfg as Jon and Tom suggested.

Specifically I added the acpi /boot/DSDT.aml command right before the line that says
"echo 'Loading Linux 3.2.0-40-generic ...'
And if I boot into the 3.2.0.40 kernal my computer starts right up.
Thanks everyone.

[Jacob Cram (cramjaco)]

Things stopped working for me.
It turned out that I pasted that fix into the wrong section of grub.cfg and actually the computer was just working by magic (or whatever makes it sometimes start up right away). Anyhow after playing around with some settings (installing and removing bumblebee and such to try to get google-earth working) the magic seems to have worn off. Long start up times again. Also I put the fix in the section of grub.cfg that I am acutally using
(just before /boot/vmlinuz-3.2.0-40-generic... etc)
which has no positive effect.
I'll play around with some of the other approaches suggested on this thread and report what works.

[Jacob Cram (cramjaco)]

Tom. Thanks for the pointer, but I'm not seeing that option.
Right now I see at the top Phoenix SecureCore Tiano Setup
Below that some tabs, I have boot selected
By UEFI Boot I selected disables. Nothing on the page changed other than
that line.
Am I in the wrong place?
-Jacob

On Sun, Apr 21, 2013 at 6:01 PM, Tom Thompson <email address hidden> wrote:

> Jacob, regarding setting UEFI to legacy ... When you toggle UEFI to
> disabled it creates another field in the form right below it. I cannot
> remember what it is called not what its default value is, but when you
> toggle it, it displays legacy.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1093217
>
> Title:
> Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19)
> [Lenovo IdeaPad Z580]
>
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> 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 lpadmi...

[nozyczek (nozyczek)]

If I remember correctly the BIOS admin password has to be setup in order to see all of the BIOS legacy options.

[Tom Thompson (tom2460)]

When I toggle "Boot Mode" to "Legacy Sup", a new field named "Boot
Priority" is created under it. This is different than the "Boot
Priority Order" further down the display. I have to toggle this new
field "Boot Priority" to "Legacy Fir".

I did not have to set an admin password.

On 4/21/2013 10:43 PM, Jacob Cram wrote:
> Tom. Thanks for the pointer, but I'm not seeing that option.
> Right now I see at the top Phoenix SecureCore Tiano Setup
> Below that some tabs, I have boot selected
> By UEFI Boot I selected disables. Nothing on the page changed other than
> that line.
> Am I in the wrong place?
> -Jacob
>
>
> On Sun, Apr 21, 2013 at 6:01 PM, Tom Thompson <email address hidden> wrote:
>
>> Jacob, regarding setting UEFI to legacy ... When you toggle UEFI to
>> disabled it creates another field in the form right below it. I cannot
>> remember what it is called not what its default value is, but when you
>> toggle it, it displays legacy.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1093217
>>
>> Title:
>> Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19)
>> [Lenovo IdeaPad Z580]
>>
>> Status in “linux” package in Ubuntu:
>> Triaged
>>
>> Bug description:
>> 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...

[Jacob Cram (cramjaco)]

It sounds to me almost like Tom is talking about a different boot window than I am seeing. For reference, I am attaching a picture of my screen in bios with boot tab selected. I have UEFI Boot set to disabled, and don't see a new sub menu appearing, or anything about legacy.

So far, I have also tried adding the "acpi /boot/DSDT.aml" line to grub, as suggested by jon
I have also tried adding that line by pressing c at the grub menu.
I also went ahead and tried the suggestions here with no success
http://ubuntuforums.org/showthread.php?t=1036051
in all cases dmesg suggests the custom DSDT.aml file does not get loaded.
I have not yet started playing around with resetting bios passwords.

Also for reference, I am attaching a dmesg output for both cases when my computer boots slow (most of the time) and when it boots fast (rarely).

Fast Boot:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.2.0-40-generic (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #64-Ubuntu SMP Mon Mar 25 21:22:10 UTC 2013 (Ubuntu 3.2.0-40.64-generic 3.2.40)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-40-generic root=UUID=defac77b-aa20-4f8f-9387-d9dd890a7366 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 0000000000090000 (usable)
[ 0.000000] BIOS-e820: 0000000000090000 - 00000000000c0000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000020000000 (usable)
[ 0.000000] BIOS-e820: 0000000020000000 - 0000000020200000 (reserved)
[ 0.000000] BIOS-e820: 0000000020200000 - 0000000040004000 (usable)
[ 0.000000] BIOS-e820: 0000000040004000 - 0000000040005000 (reserved)
[ 0.000000] BIOS-e820: 0000000040005000 - 00000000b623c000 (usable)
[ 0.000000] BIOS-e820: 00000000b623c000 - 00000000b643e000 (reserved)
[ 0.000000] BIOS-e820: 00000000b643e000 - 00000000c85c8000 (usable)
[ 0.000000] BIOS-e820: 00000000c85c8000 - 00000000caeef000 (reserved)
[ 0.000000] BIOS-e820: 00000000caeef000 - 00000000caf9f000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000caf9f000 - 00000000cafff000 (ACPI data)
[ 0.000000] BIOS-e820: 00000000cafff000 - 00000000cb000000 (usable)
[ 0.000000] BIOS-e820: 00000000cb000000 - 00000000cfa00000 (reserved)
[ 0.000000] BIOS-e820: 00000000f80f8000 - 00000000f80f9000 (reserved)
[ 0.000000] BIOS-e820: 00000000fed1c000 - 00000000fed20000 (reserved)
[ 0.000000] BIOS-e820: 0000000100000000 - 00000001af600000 (usable)
[ 0.000000] BIOS-e820: 00000001af600000 - 00000001b0000000 (reserved)
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] EFI v2.31 by Phoenix Technologies Ltd.
[ 0.000000] ACPI=0xcaffe000 ACPI 2.0=0xcaffe014 SMBIOS=0xcae8b000
[ 0.000000] Kernel-defined memdesc doesn't match the one from EFI!
[ 0.000000] EFI: mem00: type=3, attr=0xf, range=[0x0000000000000000-0x000000000000b000) (0MB)
[ 0.000000] EFI: mem01: type=7, attr=0xf, ...

[Jacob Cram (cramjaco)]

Also it looks like setting a password to access the bios doesn't change anything.

[Tom Thompson (tom2460)]

Jacob
It looks like there are different BIOS versions. A relative just
stopped by and they also have a Z580 (but no linux on it). We went into
the BIOS on it and it looks like yours on the boot page. On mine, the
main page shows bios version 5FCN89WW. On his it is 5FCN91WW and the
KBC version is about 2 different also.

Lenovo support does not show a downloadable BIOS.

[vince (vincent-typerrr)]

Hey,

I did all the steps but still have 1 problem: DSDT.aml is in the boot folder but when I try to run acpi /boot/DSDT.aml it says it's missing.

Regards Vince

[Lexx Ihrig (onilink42-deactivatedaccount)]

This issue is also affecting my Lenovo Z580 with Intel Ivybridge. Some boots get lucky, the unlucky boots force me to painfully hold down the power button untill the computer hard resets.

[vince (vincent-typerrr)]

Don't put it back in confirmed

[Tommy_CZ (t-kijas)]

Why not?

[vince (vincent-typerrr)]

Because triaged mean it has also been verified by a supervisor.
Anyway, Im switching back to windows 7 on my z580, this bug is way to annoying

[Jon Baca (jtbaca001)]

After a lot of digging, I found that the DSDT for my Windows 8 and Ubuntu are nearly identical. There is no delay in the WAEC method that Windows 8 is using. In method _OSC of the decompiled DSDT, there is a test against the OS name reported to the ACPI. In my case, I am dual booting with Windows 8 and the name that is being checked for is "Windows 2012".

That being said, I looked into my dmesg and the acpi command was not working for me either, just extra magic in my computer I guess :). Remove the acpi command from the grub.cfg menu entry for the version of Ubuntu you are running add the kernel parameter acpi_os_name="Windows 2012" as follows:

linux /boot/vmlinuz-3.8.0-19-generic root=UUID=b6449636-2d59-426d-88e4-4f6132af9e2f ro crashkernel=384M-2G:64M,2G-:128M quiet splash $vt_handoff acpi_os_name="Windows 2012"

If you are not running Windows 8, you may have to put a different string in for the acpi_os_name.

My magic ran out when I upgraded to 13.04. I have been using this to boot 13.04 with no issues. Give this a try and let us know if it works for you.

[Jon Baca (jtbaca001)]

I found that there is also a "Linux" option you can try too. It looks like there is a list of OS names in the DSDT and if Ubuntu isn't supplying one of those names, a lot of things don't get initialized properly. After saying that the Windows 2012 option was working, it immediately stopped working....So I am using the LInux option now and it seems to be working. Hopefully this trend continues after I post this.

[vince (vincent-typerrr)]

Any progress?
I really want to switch back to using Ubuntu!

[[e-mail] (jdean-uk)]

I'm curious too :)

It sounds like Jon has found a solution that doesn't involve patching DSDT (unless I've misunderstood)? I've been running 12.04 with the old kernel but keen to upgrade now.

[Jon Baca (jtbaca001)]

I am not sure if it fixed my computer or not. I seem to have better luck booting than a lot of people for some reason. Because the issue has occurred after a kernel update, I am just suggesting that maybe altering the DSDT is not the best solution to this problem(especially since Windows 8 is using the same code and it boots 100% of the time).

I did compile a kernel with the altered DSDT and it does seem to boot without problems. I have also tried diffing the 3.2 and 3.8 kernels and backing out some changes, focusing on the battery.c code in the ACPI drivers, but I have not been able to find anything that affects boot time. Anyone have any ideas on where else to look?

You should try booting your computer with some of the OS options that are listed in your decompiled DSDT. Until a solution is found, altering the DSDT is a good temporary solution(in my opinion).

[Jacob Cram (cramjaco)]

Jon,
     Could you please outline what steps I would need to take to duplicate how you have the current kernal booting on your computer?

Currently it sounds like you are running a recompiled DSDT and getting it to load with grub, but I am not 100% clear. Thanks for any suggestions you can provide.

Also, are things still working for you since your last post?

[[e-mail] (jdean-uk)]

I started to apply Tom's workaround in #63 and got the 3 warnings when recompiling DSDT (as reported in #75):

DSDT.dsl 11561: Name (_VPC, Zero)
Warning 1099 - ^ Unknown reserved name (_VPC)

DSDT.dsl 11585: Method (_CFG, 0, NotSerialized)
Warning 1099 - Unknown reserved name ^ (_CFG)

DSDT.dsl 11585: Method (_CFG, 0, NotSerialized)
Warning 1099 - Unknown reserved name ^ (_CFG)

Can these be ignored and the recompiled DSDT will still work? Also, anyone applied this to 13.04?

[Tom Thompson (tom2460)]

A few reserved name warnings when compiling the DSDT is normal.
Tom

On 5/31/2013 4:54 AM, <email address hidden> wrote:
> I started to apply Tom's workaround in #63 and got the 3 warnings when
> recompiling DSDT (as reported in #75):
>
> DSDT.dsl 11561: Name (_VPC, Zero)
> Warning 1099 - ^ Unknown reserved name (_VPC)
>
> DSDT.dsl 11585: Method (_CFG, 0, NotSerialized)
> Warning 1099 - Unknown reserved name ^ (_CFG)
>
> DSDT.dsl 11585: Method (_CFG, 0, NotSerialized)
> Warning 1099 - Unknown reserved name ^ (_CFG)
>
> Can these be ignored and the recompiled DSDT will still work? Also,
> anyone applied this to 13.04?
>

[Matthew Pray (matthewpray1)]

I have been following this bug since December 2012. I am having the same issues with ubuntu 12.04, 12.10, and 13.04 as well as Linux Mint 15.

Linux Mint 15 64-bit
Lenovo z580
Intel HD 4000
8GB Ram
750 HD

This is the bottom of my grub.cfg file
menuentry 'Linux Mint 15 Cinnamon 64-bit, 3.8.0-19-generic (/dev/sda2)' --class gnu-linux --class gnu --class os {
 recordfail
 gfxmode $linux_gfx_mode
 insmod gzio
 insmod part_gpt
 insmod ext2
 set root='hd0,gpt2'
 if [ x$feature_platform_search_hint = xy ]; then
   search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=hd0,gpt2 --hint-baremetal=ahci0,gpt2 ae563e6e-39b4-4a03-8b28-f2e6c44f303b
 else
   search --no-floppy --fs-uuid --set=root ae563e6e-39b4-4a03-8b28-f2e6c44f303b
 fi
        acpi /boot/DSDT.aml
 linux /boot/vmlinuz-3.8.0-19-generic root=UUID=ae563e6e-39b4-4a03-8b28-f2e6c44f303b ro
 initrd /boot/initrd.img-3.8.0-19-generic
}

I decompiled and recompile the DSDT file however I do not understand how to input this into grub.cfg. Every time I save the file, it will reset on the next boot. I also experimented where to put "acpi /boot/DSDT.aml but have no luck. Can someone post where this line should fit in grub.cfg? I get a message saying do not edit this file because it is auto-generated.

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub

So I tried going to /etc/default/grub and editing 40_custom with the same config as above, and booting from that, but still no luck.

Am I doing something wrong?

Thanks.
Matt

[Tom Thompson (tom2460)]

Matthew, here are some ideas.

First, remove the battery so you can reboot over and over without long
waits. If it does not boot faster now maybe it is a different problem.

Now the next thing is to prove the grub acpi command is working.

Restart and catch bootup at the grub menu. Then enter the 'e' command
and it will list an editable set of steps to be performed for the
selected boot entry. Insert the line "acpi /boot/badname.aml" and press
F10 to run these steps (and boot). There should be a error for the bad
acpi line and a prompt to press key to continue. Press key and let it
boot. Now we know that grub tries to process the acpi command.

Now do the same thing again, except this time insert the correct
filename in the acpi line "acpi /boot/DSDT.aml" and press F10 and let it
boot.

Once booted, run "dmesg | grep DSDT" and verify the date after INTL is
201000528 (or at least not 20061109).

If the date does verify, power down, put the battery back in, reboot and
again catch it at the grub menu. Use 'e' to edit the boot sequence and
insert "acpi /boot/DSDT.aml" and press F10 to boot.

If it boots fast (and works a couple times in a row), then eventually it
can be made to work, just need to figure out why grub.cfg changes are
not persisting.

If the "dmesg | grep DSDT" line did not indicate that the modded table
was loaded I'm not sure what to investigate next. Here are things that
might be different compared to my system.

  - BIOS version. On mine, "dmesg | grep Z580" shows "BIOS 5FCN89WW
08/27/2012"

  - UEFI setting in BIOS setup. On mine, it is set to disabled, which
causes another field in the menu and it is set to legacy". Maybe tables
cannot be loaded in UEFI without doing something else?

[[e-mail] (jdean-uk)]

The recompiled DSDT is working for me on Ubuntu 12.04. I've upgraded the kernel to 3.5.0-32 and booting nicely.

I just inserted the acpi line in grub.cfg here:

acpi /boot/DSDT.aml
linux /boot/vmlinuz-3.5.0-32-generic root=UUID=ad28a027-ec44-4c73-b42c-2fdc6e90b6dd ro quiet splash $vt_handoff
initrd /boot/initrd.img-3.5.0-32-generic

Thanks to Tom and everyone who added support here.

[Matthew Pray (matthewpray1)]

Tom,

I removed the battery and did as you said to test the acpi. Everything worked. I did get an error for badname.aml and it correctly loaded the DSDT.aml

I did dmesg | grep DSDT and got the date you said that I should NOT have.

dmesg | grep DSDT
[ 0.000000] ACPI: DSDT 00000000daff1000 0AD57 (v02 LENOVO IVB-CPT 00000000 INTL 20061109)
[ 0.130542] ACPI: EC: Look up EC in DSDT

Here is my original edit to the DSDT.dsl file: Is this correct? Do I need the two slash marks after Sleep (50)?

  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
                }
            }
     Sleep (50) //
        }

[Matthew Pray (matthewpray1)]

Also, I will confirm that my BIOS is the same as yours and that my UEFI settings are turned off...Set to legacy mode, and "Other OS"

[Jon Baca (jtbaca001)]

I think that I have found the culprit code change that is causing the slow boot issue. I have been comparing changes across the 3.2, 3.5, and 3.8 kernels and paying attention to the changes that remained the same across the 3.5 and 3.8 sources.

All calls to exit_idle() and irq_enter() were reversed from the 3.2 kernel to the 3.5 and 3.8 kernels in the file arch/x86/kernel/apic/apic.c. I reversed them all to match the 3.2 kernel and have been booting successfully with this kernel build. I have tried booting in every combination I could think of (quickly and slowly booting from grub, booting plugged in and uplugged etc.).
My changes are marked by the ADDED and REMOVED comments. The following is a copy of all the functions I edited.

void __irq_entry smp_apic_timer_interrupt(struct pt_regs *regs)
{
 struct pt_regs *old_regs = set_irq_regs(regs);

 /*
  * NOTE! We'd better ACK the irq immediately,
  * because timer handling can be slow.
  */
 ack_APIC_irq();
 /*
  * update_process_times() expects us to have done irq_enter().
  * Besides, if we don't timer interrupts ignore the global
  * interrupt lock, which is the WrongThing (tm) to do.
  */
 exit_idle();//ADDED
 irq_enter();
//REMOVED exit_idle();
 local_apic_timer_interrupt();
 irq_exit();

 set_irq_regs(old_regs);
}

void smp_spurious_interrupt(struct pt_regs *regs)
{
 u32 v;
 exit_idle();//ADDED
 irq_enter();
//REMOVED exit_idle();
 /*
  * Check if this really is a spurious interrupt and ACK it
  * if it is a vectored one. Just in case...
  * Spurious interrupts should not be ACKed.
  */
 v = apic_read(APIC_ISR + ((SPURIOUS_APIC_VECTOR & ~0x1f) >> 1));
 if (v & (1 << (SPURIOUS_APIC_VECTOR & 0x1f)))
  ack_APIC_irq();

 inc_irq_stat(irq_spurious_count);

 /* see sw-dev-man vol 3, chapter 7.4.13.5 */
 pr_info("spurious APIC interrupt on CPU#%d, "
  "should never happen.\n", smp_processor_id());
 irq_exit();
}

void smp_error_interrupt(struct pt_regs *regs)
{
 u32 v0, v1;
 u32 i = 0;
 static const char * const error_interrupt_reason[] = {
  "Send CS error", /* APIC Error Bit 0 */
  "Receive CS error", /* APIC Error Bit 1 */
  "Send accept error", /* APIC Error Bit 2 */
  "Receive accept error", /* APIC Error Bit 3 */
  "Redirectable IPI", /* APIC Error Bit 4 */
  "Send illegal vector", /* APIC Error Bit 5 */
  "Received illegal vector", /* APIC Error Bit 6 */
  "Illegal register address", /* APIC Error Bit 7 */
 };
 exit_idle();//ADDED
 irq_enter();
//REMOVED exit_idle();
 /* First tickle the hardware, only then report what went on. -- REW */
 v0 = apic_read(APIC_ESR);
 apic_write(APIC_ESR, 0);
 v1 = apic_read(APIC_ESR);
 ack_APIC_irq();
 atomic_inc(&irq_err_count);

 apic_printk(APIC_DEBUG, KERN_DEBUG "APIC error on CPU%d: %02x(%02x)",
      smp_processor_id(), v0 , v1);

 v1 = v1 & 0xff;
 while (v1) {
  if (v1 & 0x1)
   apic_printk(APIC_DEBUG, KERN_CONT " : %s", error_interrupt_reason[i]);
  i++;
  v1 >>= 1;
 }

 apic_printk(APIC_DEBUG, KERN_CONT "\n");

 irq_exit();
}

Other than the changes at the ADDED and REMOVED comments the source code I used to build my kernel is identical to 3.8.0-23.34, which I believe is the latest Raring kernel.

I am not sure how to submit these ch...

[Tom Thompson (tom2460)]

 > [ 0.000000] ACPI: DSDT 00000000daff1000 0AD57 (v02 LENOVO IVB-CPT
00000000 INTL 20061109)

The AD57 is the hex length of the DSDT, or 44375 decimal . 44375 is
size of original DSDT. In the modified one it should be AD5B (44379
decimal). See what the size of /boot/DSDT.aml is. If it is 44375 it is
not the re-compiled version.

If that turns out to be the case, review the compile procedure. In
particular look at the DefinitionBlock in the .dsl file which specifies
the name of the output -- maybe even change it to something like
mydsdt.aml and then use that file as input to grub.

[Jon Baca (jtbaca001)]

I realized I built the kernel with ACPI debugging enabled, rebuilt the kernel and now it doesn't work. So I guess don't waste your time testing the fix I proposed.

[Matthew Pray (matthewpray1)]

I seem to not know enough after researching how to decompile/compile. I think I'm entering all of the commands properly and I have a general idea of how it works.

Could someone post a step by step process from beginning to end including terminal commands for Comment #63.

I seem to be so close to getting this to work, but I may be missing a step in recompiling the DSDT.aml file. I have tried dozens of times and researched a ton, but I don't know enough of what I'm doing to get it right.

[Siddu (sduddikunta)]

That change was unintentional, I would appreciate it if someone could change it back. Sorry!

[bluenova (bluenova)]

Kernel 3.8.0-25 seems promising. I've tried rebooting several times and only experienced a delay of up to 10 secs before the boot screen shows.

[vince (vincent-typerrr)]

I'm using 3.8.0-23 and I also didn't experience any problems

[[e-mail] (jdean-uk)]

Matthew,

This blog post details the steps quite well: http://www.askmeaboutlinux.com/?p=2336

Though the final step of editing grub.cfg was slightly different for me. I added the 'acpi=' as per #112 here.

[Siddu (sduddikunta)]

Running upstream/mainline 3.10rc5 on 12.04 LTS and issue seems resolved;
rebooted many times with no problems.

On Sun, Jun 9, 2013 at 3:15 AM, <email address hidden> <email address hidden>wrote:

> Matthew,
>
> This blog post details the steps quite well:
> http://www.askmeaboutlinux.com/?p=2336
>
> Though the final step of editing grub.cfg was slightly different for me.
> I added the 'acpi=' as per #112 here.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1093217
>
> Title:
> Ubuntu 12.04/12.10/13.04 10-20min boot delay (From 3.2.0.29->3.8.0.19)
> [Lenovo IdeaPad Z580]
>
> Status in “linux” package in Ubuntu:
> In Progress
>
> Bug description:
> 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: Leno...

[vince (vincent-typerrr)]

So I guess it's correct to set it to fix released? if not please put it back but 3 people have said there aren't any problem anymore.

[Matthew Pray (matthewpray1)]

Does this work with Ubuntu 13.04 64-Bit?

[vince (vincent-typerrr)]

If you use the latest kernel it does

[Tommy_CZ (t-kijas)]

This bug is not fixed. Well... it is fixed, but not in Ubuntu. We cannot presume BFU will install new mainstream kernels, the update from canonical have to come. And because this is an Ubuntu bug, it should be "Fix commited" ... until we recieve the proper fix (kernel upgrade).

[Siddu (sduddikunta)]

I just experienced a hang on 3.10-rc5, the latest available upstream kernel. This bug is likely _not_ fixed, even upstream. This probably has to be re-opened or a new bug report created.

[Dave Gilbert (ubuntu-treblig)]

back to triaged (based on #128)

[Jacob Cram (cramjaco)]

The 3.10rc5 kernal worked for me without hanging most of the time from about a week after Siddu's first post untill today or so. Apparently the new-kernal magic seems to have worn off again and I am back to a 20 min boot most of the time.

[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

[Siddu (sduddikunta)]

Reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=60542

[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.

[Umut Karcı (cediddi)]

Lenovo Z580 352526 user. Workaround worked very well. I'm using 3.8.0-27-generic kernel in x64 system. Also to open, I unplugged battery and it boot up in normal time to change dsdt file and grub config.

[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

[karthik339 (karthik339)]

Recently brought Lenevo z580 and installed Ubuntu 12.04 LTS.
Boot issue exists . Tried the workaround as mentioned in the comment #63. But nothing worked.
Its very strange but I will try to explain here
For the first time when i boot it takes 20 mins to boot ,but if I shutdown after booting the second boot takes 10 seconds.
(Both with the fix as mentioned #63).

Also while delay in booting if I interrupt and restart the boot , it again boots just in 10seconds. So I am sort of confused whether the fix is working or not.
Kernel version.
3.5.0-37-generic #58~precise1-Ubuntu SMP Wed Jul 10 17:48:11 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
UEFI enabled Ubuntu installation .

[Romano Giannetti (romano-giannetti)]

Any new on this bug? I am thinking to buy this laptop --- just to know if the glitch is fixed or if there is some working workaround.
Thanks.

[Jacob Cram (cramjaco)]

I would not advocate buying this laptop if you plan to install Ubuntu. On my system I am running 3.10.0-031000rc5-generic. I find the 20 minute boot problem only happens about 50% of the time rather than 95% of the time, as it did with earlier kernal versions, but still not 0% of the time as I would prefer. I have been unable to get the workaround discussed here to work on my system, perhaps because newer versions of this computer use a bios configuration that does not seem allow the workaround. I have found that if the computer does not boot up, force restarting it into safe mode, shutting down and then restarting in normal mode results in a successful boot most of the time.

Also the following bug http://ubuntuforums.org/showthread.php?t=2043744&p=12461562#post12461562 still exists for 12.04 meaning you can't use the right click button on the mouse-pad, which is also kind of annoying.

[Romano Giannetti (romano-giannetti)]

Thanks. Have you tested too with the acpi command line options in the boot parameters? I have a little Asus which need the acpi_os_name=Linux to work reliably...
Nevertheless, thank for advising. Each new laptop is a PITA when you want to run Linux...

[Burkhard Hampl (burkhard-hampl)]

I have the same problem. If I start my Lenovo Z580 (Intel i5 and NVIDIA GeForce GT 640M) with battery in it, its a gamble if it starts in a few seconds or it takes about 10 minutes. Without battery it boots immediately. I handle the problem so, if I notice that the boot try is going to take longer, I interrupt the try (with 5 seconds power button press or with a kernel reboot (ALT + PRINT + R + E + I + S + U + B ( https://en.wikipedia.org/wiki/Magic_SysRq_key )). If after the reboot again a delay, I interrupt it again, till its boot "fast".

[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.

[Siddu (sduddikunta)]

Lv Zheng from Intel reported on the Kernel Bug Tracker that a fix may be available. I've tested using the 3.12-rc2 kernel from the Ubuntu mainline PPA with good results, but additional testing is needed before I can report back that it fixes the problem. See his comment reproduced below:

<quote>
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.
</quote>

If you can, please either install the 3.12-rc2 kernel from the Ubuntu Mainline Kernel PPA or download and compile from source a 3.12-rc2 kernel and test on a system as unmodified as possible (no DSDT modifications, init script hacks, or otherwise) and report back. The mainline kernel PPA's debs for 3.12-rc2 are tagged as Saucy (13.10), but should install and boot on any Ubuntu version back to 12.04 (maybe even earlier).

Thanks!

[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.

[bluenova (bluenova)]

3.12-rc2 64-bit didn't work for me. It was fine the first 5 reboots but the 6th got stuck.

[bluenova (bluenova)]

For clarity this is on a non DSDT modified machine running 13.04 and installed from the Mainline PPA.

[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.

[karthik339 (karthik339)]

issue persist even in Ubuntu 13.10 !

[Dave Gilbert (ubuntu-treblig)]

13.10 still uses kernel 3.11
The upstream comment says they believe it's fixed in kernel 3.12-rc2, so can some of you try the latest kernel by using the
instructions in comment #27 from Christopher.

[Siddu (sduddikunta)]

The issue has been confirmed as not fixed, even in 3.12-rc2. See the linked
entry on the kernel bug tracker.

[Dave Gilbert (ubuntu-treblig)]

Siddu: Hmm your description on there seems to be different; my understanding of the bug reported here was that it happened every/most times during boot, your comment on the upstream bug talks about occasional infinite loops - are we talking about the same bug here?

[Siddu (sduddikunta)]

We are. The infinite loop only happens occassionally with the new 3.12-rc2
kernel, as opposed to almost every time with the previous kernels.

[Matthew Pray (matthewpray1)]

Can this be confirmed that it only effects debian based distros? Has anyone tried Arch/Manjaro/Cent OS?

[Siddu (sduddikunta)]

It affects all Linux-based OSes. It is a bug in the upstream kernel itself.
I've tried Fedora, Arch, and even an LFS.

[nozyczek (nozyczek)]

I have not seen this problem on Arch yet. It has been only few weeks since I installed it on my z580 so I will wait few more weeks and I will report back. Kernel I'm using is stock vanilla Arch with no customization on my end.

-->uname -a
Linux z580 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64 GNU/Linux

-->dmesg | grep Z580
[ 0.000000] DMI: LENOVO IdeaPad Z580 /Lenovo , BIOS 5FCN89WW 08/27/2012

-->dmesg | grep DSDT
[ 0.000000] ACPI: DSDT 00000000daff1000 0AD57 (v02 LENOVO IVB-CPT 00000000 INTL 20061109)
[ 0.144683] ACPI: EC: Look up EC in DSDT

[nozyczek (nozyczek)]

Few more days on arch and i still have not seen this bug. I was on 3.12.0-1-ARCH for a bit and now I'm on 3.12.1-1-ARCH.

[provost (robert-lagndon)]

This is what worked for me.
1) Shut down laptop
2) Remove battery and unplug the power supply.
3) Press and hold power button for more than 40 seconds.
4) replace back battery and plug in power.
5) Boot into Ubuntu.Ubuntu boots normally without any delay.

Apparantly there is a bios level optimization put in by lenevo that prevents battery charging until it reches below a certain percentage. They claim this is to improve battery life. It seems that this bios level optimization messes with Ubuntu start up and hangs it.

Steps mentioned above will disable this setting and apparantly fixes ubuntu boot delay.
I have not seen boot delay after this fix for more than 3 weeks now.
I am on
~$ uname -a
Lenovo-Z580 3.8.0-33-generic #48-Ubuntu SMP Wed Oct 23 09:16:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

P.S. the steps mentioned above also fixes Windows 8/8.1 glitch of battery not charging even when power adapter is connected

[bluenova (bluenova)]

@provost, Sounds a little like witchcraft but I'll give anything a try. Unfortunately first boot was stuck on a delay using 3.11.0-13-generic.

[penalvch (penalvch)]

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

If it remains an issue, could you please just make a comment to this.

Also, could you please test the latest upstream kernel available (v3.13-rc3, not rc4 as it doesn't have the necessary files) 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.13-rc3

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

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

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

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

[Paul Abrahams (abrahams)]

I also have a Lenovo Z580 running (Kubuntu) 13.10. I have a slightly different problem (also reported elsewhere) that I assume has the same cause and probably the same fix. My system often freezes for anywhere from 10 seconds to a minute or two. Switching to a virtual console and back seems to help speed up the recovery but I'm not sure of that. It's particularly noticeable when running Firefox, but I've seen it in other contexts. The mouse continues to work during the freeze.

[nozyczek (nozyczek)]

@Paul
I don't think this is related to this bug.

[Matthew Pray (matthewpray1)]

I have read that this is an issue with software in the battery. Would buying a new battery help at all with this issue...such as a non-lenovo battery?

[Siddu (sduddikunta)]

I may have come across a workaround. After diff-ing the Arch and Ubuntu kernel configs (the only true difference as the Ubuntu mainline series is impacted as well), I found that Arch compiles ACPI battery support as a module, while Ubuntu has it built-in. The difference seems to manifest in the time at which ACPI battery support is loaded. Since Arch has it as a module and not in the initramfs, it loads the battery module after the root filesystem comes up, long after the danger of a hang. Recompiling the Ubuntu kernel using the kernel source package with battery support as a module, adding a blacklist entry in /etc/modprobe.d to prevent battery support from coming up too early, and adding a system service in /etc/init to bring up the battery after filesystems are mounted has worked so far for me and a friend with the same machine. The only downside is that the kernel must be recompiled each time it is released, unless Ubuntu adopts a change to their configs.

I made a PPA with current kernel packages (13.10 Saucy only) and a "linux-z580" package with the two config/script files. It is offered here, of course, without any warranty of any kind. Find it here: https://launchpad.net/~sduddikunta/+archive/z580.

[Varenya (varen90)]

I am still facing the problem I am using 12.04 LTS version kernel:
3.8.0-35-generic #50~precise1-Ubuntu SMP Wed Dec 4 17:25:51 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

The issue is intermittent, i have to switch it off forcefully twice or thrice to make it work.

Please provide an permanent fix for this.

[neon1ks (neon1ks)]

Siddu,
Thank you very much!

[Alagos (alagoszim)]

Found temporary solution which works for me on my ubuntu 12.04 x64 and lenovo z580:
http://askubuntu.com/a/353999
Maybe it could be useful for someone else.

[Jochen Fahrner (jofa)]

Thank you Alagos for that link. That also did the trick for me.

[Jacob Cram (cramjaco)]

Siddhu, I'd like to try tour workaround. Can I use that that kernal with ubuntu 12.04 instead of 13.04 or is that likely to cause problems?

[Siddu (sduddikunta)]

I've meaning to support LTS for a while, so here it is. I just uploaded a build of 3.2.0-58.88 for Precise 12.04 LTS to the PPA. Give it a few hours to build before you attempt to install it. Install both the linux-z580 package (contains boot scripts) and upgrade your linux-image-3.2.0-58-generic package to version 3.2.0-58.88ppa1. Note that there's currently a slightly newer kernel in precise-proposed, so make sure you don't upgrade to that one just yet. https://launchpad.net/~sduddikunta/+archive/z580.

[Jacob Cram (cramjaco)]

Thanks Siddu,
     Forgive my ignorance, but may I ask what commands I need to run to make this happen. I am currently running 3.13.0-031300rc3-generic kernal.

I installed the ppa no problem
sudo add-apt-repository ppa:sduddikunta/z580
sudo apt-get update

but then how do I correctly install the packages from the repository?
 sudo apt-get install linux-z580

Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  linux-z580
0 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 2,300 B of archives.
After this operation, 38.9 kB of additional disk space will be used.
Get:1 http://ppa.launchpad.net/sduddikunta/z580/ubuntu/ precise/main linux-z580 all 0.1-3 [2,300 B]
Fetched 2,300 B in 0s (4,008 B/s)
Selecting previously unselected package linux-z580.
(Reading database ... 1017776 files and directories currently installed.)
Unpacking linux-z580 (from .../linux-z580_0.1-3_all.deb) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.13.0-031300rc3-generic
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169
Processing triggers for ureadahead ...
Setting up linux-z580 (0.1-3) ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.13.0-031300rc3-generic
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169

and then sudo apt-get install linux

Reading package lists... Done
Building dependency tree
Reading state information... Done
linux is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.

I presume I should perhaps delete the old linux image if I want this to work?
I'd love specific instructions if anybody could help me out.
Thanks in advance.

[Siddu (sduddikunta)]

You want to upgrade your linux packages. Run "sudo apt-get dist-upgrade"
for the upgrades to run. You should see a version with a "ppa1" suffix in
the output.

[Jacob Cram (cramjaco)]

Thanks Siddhu. I do see the version with ppa1 suffix in the output. The dist-upgrade command ends with the following two lines though
Error! Could not locate dkms.conf file.
File: does not exist.

Is this a problem or can I ignore it?

[Jacob Cram (cramjaco)]

Also, should I expect something new to show up in grub, or should I just boot from 3.2.0-58?

[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