system takes exactly five minutes to wake from suspend

Bug #1575250 reported by Alistair Buxton on 2016-04-26
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linux
Unknown
Unknown
linux (Ubuntu)
Low
Alistair Buxton

Bug Description

To reproduce:
1. Close laptop lid.
2. Wait a couple of minutes.
3. Open laptop lid.

Result: the screen remains powered off and the system will not respond in any way. Pressing keys does nothing. Pressing the power button does nothing. There is no disk activity but the power light is lit. After exactly five minutes (to the second) the system resumes.

Regression commit:
https://github.com/torvalds/linux/commit/a8d46b9e4e487301affe84fa53de40b890898604

WORKAROUND: Use kernel boot parameter:
noapictimer

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37 [modified: boot/vmlinuz-4.4.0-21-generic]
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: al 1892 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue Apr 26 16:46:08 2016
HibernationDevice: RESUME=UUID=8623f57e-2fc2-4a9a-bd35-73f33e1aeb59
InstallationDate: Installed on 2016-04-21 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: LENOVO 20040M18
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=0f83fbb5-4903-4610-9f32-1ab22c935bb0 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 24CN61WW
dmi.board.name: Caucasus2
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Lenovo
dmi.chassis.version: Rev 1.0
dmi.modalias: dmi:bvnLENOVO:bvr24CN61WW:bd08/11/2010:svnLENOVO:pn20040M18:pvrLenovoIdeapadS10-3t:rvnLENOVO:rnCaucasus2:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
dmi.product.name: 20040M18
dmi.product.version: Lenovo Ideapad S10-3t
dmi.sys.vendor: LENOVO

Alistair Buxton (a-j-buxton) wrote :

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc6-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: bios-outdated-24cn62ww
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :

This is a regression since 14.04. Out of date bios is irrelevant. Please provide a citation for your claims of "buggy" and "insecure."

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :

None of the links you provided support your claim that my BIOS is insecure or buggy. Have you tried actually reading the stuff you copy and paste every day?

I would further point out that the last update for this system was released in 2010, at least four years before this bug was introduced.

On top of that, no method for reflashing the BIOS of this system without installing Windows 7 or Windows XP exists, for which my system does not have a license.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :
Download full text (9.0 KiB)

If one actually reads the release notes (as I did yesterday) one will notice that there are no references to security fixes and the only two changes listed are described as a workaround and a fix for Windows XP respectively.

Regardless, I have now obtained a copy of Windows and updated to the newest BIOS. As expected, it made absolutely no difference at all. Here is the output of the commands as requested:

24CN62WW
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.5 present.
28 structures occupying 1356 bytes.
Table at 0x000DF010.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
 Vendor: LENOVO
 Version: 24CN62WW
 Release Date: 08/30/2010
 Address: 0xE6950
 Runtime Size: 104112 bytes
 ROM Size: 1024 kB
 Characteristics:
  ISA is supported
  PCI is supported
  PC Card (PCMCIA) is supported
  PNP is supported
  BIOS is upgradeable
  BIOS shadowing is allowed
  ESCD support is available
  Boot from CD is supported
  Selectable boot is supported
  Print screen service is supported (int 5h)
  8042 keyboard services are supported (int 9h)
  Serial services are supported (int 14h)
  Printer services are supported (int 17h)
  ACPI is supported
  USB legacy is supported
  Smart battery is supported
  BIOS boot specification is supported
  Targeted content distribution is supported
 BIOS Revision: 0.62

Handle 0x0001, DMI type 1, 27 bytes
System Information
 Manufacturer: LENOVO
 Product Name: 20040M18
 Version: Lenovo Ideapad S10-3t
 Serial Number: 11S11012681ZZ0LR09H1AL
 UUID: 186CED41-A92F-6842-50AF-203040506099
 Wake-up Type: Power Switch
 SKU Number: Not Specified
 Family: Not Specified

Handle 0x0002, DMI type 2, 8 bytes
Base Board Information
 Manufacturer: LENOVO
 Product Name: Caucasus2
 Version: Rev 1.0
 Serial Number: QB01774374

Handle 0x0003, DMI type 3, 17 bytes
Chassis Information
 Manufacturer: Lenovo
 Type: Notebook
 Lock: Not Present
 Version: Rev 1.0
 Serial Number:
 Asset Tag: No Asset Tag
 Boot-up State: Safe
 Power Supply State: Safe
 Thermal State: Safe
 Security Status: None
 OEM Information: 0x00005525

Handle 0x0004, DMI type 4, 40 bytes
Processor Information
 Socket Designation: U2E1
 Type: Central Processor
 Family: Other
 Manufacturer: Intel
 ID: CA 06 01 00 FF FB E9 BF
 Version: CPU Version
 Voltage: 3.3 V
 External Clock: 166 MHz
 Max Speed: 1666 MHz
 Current Speed: 1666 MHz
 Status: Populated, Enabled
 Upgrade: ZIF Socket
 L1 Cache Handle: 0x0005
 L2 Cache Handle: 0x0006
 L3 Cache Handle: Not Provided
 Serial Number: Not Specified
 Asset Tag: Not Specified
 Part Number: Not Specified
 Core Count: 1
 Core Enabled: 1
 Thread Count: 2
 Characteristics:
  64-bit capable

Handle 0x0005, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L1 Cache
 Configuration: Enabled, Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 24 kB
 Maximum Size: 24 kB
 Supported SRAM Types:
  Burst
  Pipeline Bur...

Read more...

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Alistair Buxton, thanks for working on that, and ruling that out. It's one less rebuttal upstream may offer with regards to addressing the issue as soon as possible for you.

Despite this, could you please test the latest mainline kernel (4.7-rc2) and advise to the results?

If this is still reproducible with the latest, the next step is a standard bisection to identify the offending regression commit.

tags: added: latest-bios-24cn62ww
removed: bios-outdated-24cn62ww
tags: added: kernel-bug-exists-upstream-4.6 regression-release
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :

4.7-rc2 does not work. The regression is somewhere between 3.9 and 4.0.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Alistair Buxton (a-j-buxton) wrote :

While messing around with this I noticed that the system does actually unsuspend on recent kernels after exactly five minutes. After unsuspending the system clock is five minutes slow, to the second. There are no useful messages in dmesg, syslog or journalctl.

summary: - close laptop lid = complete system freeze
+ system takes exactly five minutes to wake from suspend
description: updated
tags: added: kernel-bug-exists-upstream-4.7-rc2 needs-bisect
removed: kernel-bug-exists-upstream-4.6

Alistair Buxton, one may confirm how probable an upstream commit is related to the issue by testing it following https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream . Could you please advise?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :

Sure, just give me access to a build server where I can build the kernels for bisection.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

Alistair Buxton, to advise, it doesn't take a build server to test an upstream commit. Also, that isn't something any one would provide here on Launchpad.

tags: added: needs-commit-confirmation-test
Changed in linux (Ubuntu):
importance: Medium → Low
importance: Low → Medium
importance: Medium → Low
status: Confirmed → Incomplete
Alistair Buxton (a-j-buxton) wrote :

Since it looks like I am expected to fix this myself, why don't you just mark it triaged and assign it to me?

Changed in linux (Ubuntu):
status: Incomplete → In Progress
assignee: nobody → Alistair Buxton (a-j-buxton)
Alistair Buxton (a-j-buxton) wrote :

I'm working on the bisect now. I already ruled out the suspected commit - the first bisect step blew right past it. Each build takes about 2.5 hours on an i7-3770 and there's another 10 to go, so I should find the answer in about about four days or so.

Alistair Buxton (a-j-buxton) wrote :

I completed the bisection and googling the resulting commit ID revealed that this bug has already been reported upstream.

Alistair Buxton, as documented at https://wiki.ubuntu.com/Bugs/Upstream/kernel bugzilla is typically not where developers prefer bugs are reported, as it is considered legacy.

Also, given that the upstream bug is Status: NEEDS INFO, you may get better traction filing a report following the above link to the appropriate mailing list (TO Rafael J. Wysocki and Len Brown CC linux-acpi).

description: updated
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.