17.10 - suspend/resume failure

Bug #1730762 reported by venturia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I'm experiencing a failure in the resume process after the suspend. When I try to resume the system start, but the screen stay black while the disk seem be really busy.

The only way to exit from this status is unplug the system before restart it.

Let me know how to collect additional info (if necessary).

Alessandro-

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: alessandro 1948 F.... pulseaudio
 /dev/snd/controlC0: alessandro 1948 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Nov 7 22:59:45 2017
HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
InstallationDate: Installed on 2016-07-09 (486 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IwConfig:
 lo no wireless extensions.

 enp2s5 no wireless extensions.
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Packard Bell NEC IMEDIA 5204
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/14/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: GA-8TRC410M-NF
dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
dmi.chassis.type: 3
dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
dmi.product.name: IMEDIA 5204
dmi.product.version: PB34310106
dmi.sys.vendor: Packard Bell NEC

Revision history for this message
venturia (alessandro-venturini) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
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.14 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.14

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
summary: - 17.10 - suspend/resume failure
+ 17.10 - suspend/resume failure - kernel-bug-exists-upstream
tags: added: kernel-bug-exists-upstream
Revision history for this message
venturia (alessandro-venturini) wrote : Re: 17.10 - suspend/resume failure - kernel-bug-exists-upstream

I've done the test as described but this didn't fix the issue.

While booting I've seen some ACPI error as per the attached image https://photos.app.goo.gl/YTZxkq7T2N4SiBGb2

I've tried all the different 4.14.0-041400 kernels: all of them fail in handling correctly the resume step.

The main difference with the previous kernel is that the mouse seem to resume - I sow the red of the leds, but having the screeen black I've no idea about the correct functionality.

Suspend/resume was working correctly in 14.04, 14.10, 15.04 32 bit version.

Let me know how I can assist you.

Thanks for taking care of this issue.
Alessandro-

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote : Re: [Bug 1730762] 17.10 - suspend/resume failure - kernel-bug-exists-upstream
Download full text (3.8 KiB)

> On 17 Nov 2017, at 5:14 AM, venturia <email address hidden> wrote:
>
> I've done the test as described but this didn't fix the issue.
>
> While booting I've seen some ACPI error as per the attached image
> https://photos.app.goo.gl/YTZxkq7T2N4SiBGb2
>
>
> I've tried all the different 4.14.0-041400 kernels: all of them fail in handling correctly the resume step.
>
> The main difference with the previous kernel is that the mouse seem to
> resume - I sow the red of the leds, but having the screeen black I've no
> idea about the correct functionality.
>
> Suspend/resume was working correctly in 14.04, 14.10, 15.04 32 bit
> version.

What about 15.10 to 17.04?

>
> Let me know how I can assist you.
>
> Thanks for taking care of this issue.
> Alessandro-
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1730762
>
> Title:
> 17.10 - suspend/resume failure - kernel-bug-exists-upstream
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I'm experiencing a failure in the resume process after the suspend.
> When I try to resume the system start, but the screen stay black while
> the disk seem be really busy.
>
> The only way to exit from this status is unplug the system before
> restart it.
>
> Let me know how to collect additional info (if necessary).
>
> Alessandro-
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-16-generic 4.13.0-16.19
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: alessandro 1948 F.... pulseaudio
> /dev/snd/controlC0: alessandro 1948 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Nov 7 22:59:45 2017
> HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
> InstallationDate: Installed on 2016-07-09 (486 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> IwConfig:
> lo no wireless extensions.
>
> enp2s5 no wireless extensions.
> Lsusb:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: Packard Bell NEC IMEDIA 5204
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=it_IT.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-16-generic N/A
> linux-backports-modules-4.13.0-16-generic N/A
> linux-firmware 1.169
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 02/14/2006
> dmi.bios.vendor: P...

Read more...

Revision history for this message
venturia (alessandro-venturini) wrote : Re: 17.10 - suspend/resume failure - kernel-bug-exists-upstream

The two versions were not working.

A-

summary: - 17.10 - suspend/resume failure - kernel-bug-exists-upstream
+ 17.10 - suspend/resume failure
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please find the last working kernel and first non-working kernel in http://kernel.ubuntu.com/~kernel-ppa/mainline/.

You don't need to try stable releases (vX.Y.Z). You only need to try vX.Y or vX.Y-rc* releases.

Revision history for this message
venturia (alessandro-venturini) wrote :

I've tested all the following 64bit versions:

version before 3.13 were not starting
version 3.14 and 3.15 were starting only with x.org
for 3.16 and above start with wayland or xorg.

That said, all the 64 bit version fail in managing the suspend resume.

Using the old 14.04.1 32 bit from CD works fine. I don't how to test all the other 32 bit version. The bios is not able to start from USB and that make everything hard to test.

How I can support you?

A-

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote : Re: [Bug 1730762] Re: 17.10 - suspend/resume failure
Download full text (3.7 KiB)

> On 21 Nov 2017, at 6:41 AM, venturia <email address hidden> wrote:
>
> I've tested all the following 64bit versions:
>
> version before 3.13 were not starting
> version 3.14 and 3.15 were starting only with x.org
> for 3.16 and above start with wayland or xorg.
>
> That said, all the 64 bit version fail in managing the suspend resume.
>
>
> Using the old 14.04.1 32 bit from CD works fine. I don't how to test all the other 32 bit version. The bios is not able to start from USB and that make everything hard to test.

IIRC, you were using i386 and suspend worked fine.

Now you want to use amd64 instead, but suspend doesn’t work, correct?

>
> How I can support you?
>
> A-
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1730762
>
> Title:
> 17.10 - suspend/resume failure
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I'm experiencing a failure in the resume process after the suspend.
> When I try to resume the system start, but the screen stay black while
> the disk seem be really busy.
>
> The only way to exit from this status is unplug the system before
> restart it.
>
> Let me know how to collect additional info (if necessary).
>
> Alessandro-
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-16-generic 4.13.0-16.19
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: alessandro 1948 F.... pulseaudio
> /dev/snd/controlC0: alessandro 1948 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Nov 7 22:59:45 2017
> HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
> InstallationDate: Installed on 2016-07-09 (486 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> IwConfig:
> lo no wireless extensions.
>
> enp2s5 no wireless extensions.
> Lsusb:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: Packard Bell NEC IMEDIA 5204
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=it_IT.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-16-generic N/A
> linux-backports-modules-4.13.0-16-generic N/A
> linux-firmware 1.169
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 02/14/2006
> dmi.bios.vendor: Phoenix Technologies, LTD
> dmi.bios.version: 6.00 PG
> dmi.board.name: GA-8TRC410M-NF
> dmi.board.vendor: N...

Read more...

Revision history for this message
venturia (alessandro-venturini) wrote :

Correct.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

> On 23 Nov 2017, at 8:23 PM, venturia <email address hidden> wrote:
>
> Correct.

Is the system alive after resume? Can you ssh into the system?

>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1730762
>
> Title:
> 17.10 - suspend/resume failure
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> I'm experiencing a failure in the resume process after the suspend.
> When I try to resume the system start, but the screen stay black while
> the disk seem be really busy.
>
> The only way to exit from this status is unplug the system before
> restart it.
>
> Let me know how to collect additional info (if necessary).
>
> Alessandro-
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-16-generic 4.13.0-16.19
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3.1
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC1: alessandro 1948 F.... pulseaudio
> /dev/snd/controlC0: alessandro 1948 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> Date: Tue Nov 7 22:59:45 2017
> HibernationDevice: RESUME=UUID=e43cf651-e870-4c57-826f-54017ec51f13
> InstallationDate: Installed on 2016-07-09 (486 days ago)
> InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> IwConfig:
> lo no wireless extensions.
>
> enp2s5 no wireless extensions.
> Lsusb:
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> MachineType: Packard Bell NEC IMEDIA 5204
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=it_IT.UTF-8
> SHELL=/bin/bash
> ProcFB: 0 nouveaufb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=50ada02b-678c-4b91-96b4-65bcdeaf645c ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.13.0-16-generic N/A
> linux-backports-modules-4.13.0-16-generic N/A
> linux-firmware 1.169
> RfKill:
>
> SourcePackage: linux
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 02/14/2006
> dmi.bios.vendor: Phoenix Technologies, LTD
> dmi.bios.version: 6.00 PG
> dmi.board.name: GA-8TRC410M-NF
> dmi.board.vendor: NEC COMPUTERS INTERNATIONAL
> dmi.chassis.type: 3
> dmi.chassis.vendor: NEC COMPUTERS INTERNATIONAL
> dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/14/2006:svnPackardBellNEC:pnIMEDIA5204:pvrPB34310106:rvnNECCOMPUTERSINTERNATIONAL:rnGA-8TRC410M-NF:rvr:cvnNECCOMPUTERSINTERNATIONAL:ct3:cvr:
> dmi.product.name: IMEDIA 5204
> dmi.product.version: PB34310106
> dmi.sys.vendor: Packard Bell NEC
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730762/+subscriptions

Revision history for this message
venturia (alessandro-venturini) wrote :

No you cannot: the system dead evenif the HD is spinning. The only way to restart the desktop is to unplug and then replug the power cable from the socket.

I'm still curious to understand the reason for the 12 ACPI errors that I'm experiency at any bootstrap: Should this be linked to my issue?

Wait for your next test request.

A-

Revision history for this message
venturia (alessandro-venturini) wrote :

Hello, there is still someone looking for this issue?
Thanks, Alessandro-

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Yes,

Please follow instructions in [1], ask see if all pm_test work.
[1] https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibernate-issues

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.