[Dell VOSTRO 5560] Suspend will cause system failed to wake up from hibernate automatically.

Bug #1182818 reported by Po-Hsu Lin
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Po-Hsu Lin

Bug Description

CID: 201303-13110 Dell VOSTRO 5560

Steps:
Case A-
1. Reboot, suspend, and wake the system up.
2. Running hibernate test in Checkbox (tick only "Hibernation tests" and "power-management/rtc")

Case B-
1. Reboot, running hibernate test in Checkbox (tick only "Hibernate tests" and "power-management/rtc")

Expected Results:
The system should wake up from hibernate automatically.

Actual Results:
For case A, the system is failed to wake up from hibernate automatically,
but if you don't suspend it first (case B), then it will wake itself up and everything seems fine.

There is no error message in hibernate-single.log (Please find attachment)

Note: Not sure if it's hardware related or checkbox related.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.5.0-28-generic 3.5.0-28.48~precise1
ProcVersionSignature: Ubuntu 3.5.0-28.48~precise1-generic 3.5.7.9
Uname: Linux 3.5.0-28-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC290 Analog [ALC290 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1527 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xb2610000 irq 45'
   Mixer name : 'Intel PantherPoint HDMI'
   Components : 'HDA:10ec0290,102805e8,00100003 HDA:80862806,80860101,00100000'
   Controls : 28
   Simple ctrls : 12
Date: Wed May 22 15:44:33 2013
HibernationDevice: RESUME=UUID=c3cbfcf7-fd98-498d-adf3-a2b99a7a1041
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213)
MachineType: Dell Inc. Vostro 5560
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-28-generic root=UUID=f72f6ee1-f642-4d5e-87da-46a78e4cba5c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-28-generic N/A
 linux-backports-modules-3.5.0-28-generic N/A
 linux-firmware 1.79.4
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/05/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: X12
dmi.board.name: T5E3C1
dmi.board.vendor: Dell Inc.
dmi.board.version: X01
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrX12:bd03/05/2013:svnDellInc.:pnVostro5560:pvr:rvnDellInc.:rnT5E3C1:rvrX01:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Vostro 5560
dmi.sys.vendor: Dell Inc.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Po-Hsu Lin (cypressyew)
description: updated
Changed in linux (Ubuntu):
assignee: Anthony Wong (anthonywong) → Keng-Yu Lin (lexical)
importance: Undecided → Medium
Revision history for this message
Keng-Yu Lin (lexical) wrote : Re: Suspend will cause system failed to wake up from hibernate automatically.

@Po-Hsu, does s3 work well? I am kind of confused by the bug title and description.

  Is it the s3 or s4 that failed?

  To be simple, execute

    "sudo pm-suspend"

  and

    "sudo pm-hibernate"

and post here which fails.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello Keng-Yu

Suspend and hibernate both works fine with the command.

But if we use RTC to let it wake itself up from hibernate:
1. System can wake itself up if we didn't suspend it first.
2. System cannot wake itself up if we did suspend it before hibernate.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
summary: - Suspend will cause system failed to wake up from hibernate
- automatically.
+ [Dell VOSTRO 5560] Suspend will cause system failed to wake up from
+ hibernate automatically.
Revision history for this message
penalvch (penalvch) wrote :

Po-Hsu Lin as per your :
[ 0.288022] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored

Hence, as per http://www.dell.com/support/drivers/us/en/04/Product/vostro-5560 an update is available for your BIOS (A05). If you update to this following https://help.ubuntu.com/community/BiosUpdate , does it change anything? If it doesn't, could you please both specify what happened, and just provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Keng-Yu Lin (lexical) wrote :

Per comment 4 I think this is a BIOS issue.

Revision history for this message
Keng-Yu Lin (lexical) wrote :

Assign the bug to Cert for verifying comment #5.

Changed in linux (Ubuntu):
assignee: Keng-Yu Lin (lexical) → Po-Hsu Lin (cypressyew)
status: Incomplete → Triaged
Revision history for this message
penalvch (penalvch) wrote :

Pending BIOS updated (now A06).

tags: added: bios-outdated-a06
Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Sorry,
we don't have access to this hardware now.
Will get back on this after we have access.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Verified with 3.13.0-32, this cannot be reproduced.
Hibernate works fine after S3, it will wake itself up automatically.

Changed in linux (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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