suspend not working with latest xenial and kernel 4.4.0

[Paulo Dias]

suspend stops but never finishes and needs a reboot

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Mar 20 22:45:50 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-10-04 (168 days ago)
InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcEnviron:
 LANGUAGE=
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Anton Sudak (anton-sudak)]

I have same bug. After closing lid system going to suspend but never woke up. here is suspend log

Апр 16 21:08:50 LissAmour systemd-logind[648]: Lid closed.
Апр 16 21:08:50 LissAmour systemd-logind[648]: Suspending...
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2340] manager: sleep requested (sleeping: no enabled: yes)
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2340] manager: sleeping...
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2341] device (wlan0): state change: activated -> unmanaged (reason 'sleeping') [100
Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep
Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]: gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal
Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal: PrepareForSleep
Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep signal
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2519] dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 1003
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for 192.168.0.104 on wlan0.
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2520] dhcp4 (wlan0): state changed bound -> done
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.104.
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv4 no longer relevant for mDNS.
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record for fe80::9ead:97ff:fe36:bf45 on wlan0.
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::9ead:97ff:fe36:bf45.
Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv6 no longer relevant for mDNS.
Апр 16 21:08:50 LissAmour kernel: wlan0: deauthenticating from c0:4a:00:56:d8:56 by local choice (Reason: 3=DEAUTH_LEAVING)
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2596] dns-mgr: Writing DNS information to /sbin/resolvconf
Апр 16 21:08:50 LissAmour dnsmasq[1014]: setting upstream servers from DBus
Апр 16 21:08:50 LissAmour wpa_supplicant[935]: wlan0: CTRL-EVENT-DISCONNECTED bssid=c0:4a:00:56:d8:56 reason=3 locally_generated=1
Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com
Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] offline
Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2906] manager: NetworkManager state is now ASLEEP
Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach: https://daisy.ubuntu.com
Апр 16 21:08:50 LissAmour kernel: cfg80211: World regulatory domain updated:
Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: unset
Апр 16 21:08:50 LissAmour kernel: cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
Апр 16 21:08:50 LissAmour kernel: cfg80211: (2402000 KHz - 2472000 KHz @ 4...

[Paulo Dias (paulo-miguel-dias)]

fixed in 4.6.0 rc2
On Apr 16, 2016 15:35, "Anton Sudak" <email address hidden> wrote:

> I have same bug. After closing lid system going to suspend but never
> woke up. here is suspend log
>
> Апр 16 21:08:50 LissAmour systemd-logind[648]: Lid closed.
> Апр 16 21:08:50 LissAmour systemd-logind[648]: Suspending...
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2340]
> manager: sleep requested (sleeping: no enabled: yes)
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2340]
> manager: sleeping...
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2341]
> device (wlan0): state change: activated -> unmanaged (reason 'sleeping')
> [100
> Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]:
> gnome-session-binary[1653]: DEBUG(+): GsmSystemd: received logind signal:
> PrepareForSleep
> Апр 16 21:08:50 LissAmour /usr/lib/gdm3/gdm-x-session[1643]:
> gnome-session-binary[1653]: DEBUG(+): GsmSystemd: ignoring PrepareForSleep
> signal
> Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+):
> GsmSystemd: received logind signal: PrepareForSleep
> Апр 16 21:08:50 LissAmour gnome-session-binary[1653]: DEBUG(+):
> GsmSystemd: ignoring PrepareForSleep signal
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2519]
> dhcp4 (wlan0): canceled DHCP transaction, DHCP client pid 1003
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record
> for 192.168.0.104 on wlan0.
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2520]
> dhcp4 (wlan0): state changed bound -> done
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group
> on interface wlan0.IPv4 with address 192.168.0.104.
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv4 no
> longer relevant for mDNS.
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Withdrawing address record
> for fe80::9ead:97ff:fe36:bf45 on wlan0.
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Leaving mDNS multicast group
> on interface wlan0.IPv6 with address fe80::9ead:97ff:fe36:bf45.
> Апр 16 21:08:50 LissAmour avahi-daemon[1150]: Interface wlan0.IPv6 no
> longer relevant for mDNS.
> Апр 16 21:08:50 LissAmour kernel: wlan0: deauthenticating from
> c0:4a:00:56:d8:56 by local choice (Reason: 3=DEAUTH_LEAVING)
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2596]
> dns-mgr: Writing DNS information to /sbin/resolvconf
> Апр 16 21:08:50 LissAmour dnsmasq[1014]: setting upstream servers from DBus
> Апр 16 21:08:50 LissAmour wpa_supplicant[935]: wlan0:
> CTRL-EVENT-DISCONNECTED bssid=c0:4a:00:56:d8:56 reason=3 locally_generated=1
> Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach:
> https://daisy.ubuntu.com
> Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] offline
> Апр 16 21:08:50 LissAmour NetworkManager[658]: <info> [1460830130.2906]
> manager: NetworkManager state is now ASLEEP
> Апр 16 21:08:50 LissAmour whoopsie[653]: [21:08:50] Cannot reach:
> https://daisy.ubuntu.com
> Апр 16 21:08:50 LissAmour kernel: cfg80211: World regulatory domain
> updated:
> Апр 16 21:08:50 LissAmour kernel: cfg80211: DFS Master region: unset
> Апр 1...

[Anton Sudak (anton-sudak)]

Confirming that new kernel fix this issue. Tested on 4.6-rc3

[brett hassall (brett-hassall)]

I have the same problem - hanging during a suspend.

I've tracked the problem to the driver for the Radeon HD8690M card in my Dell E6440 laptop.

If I rmmod the driver, the suspend/resume works ok. Only problem I have noticed is that without the driver loaded, the power consumption goes up by 4W.

So, as a workaround, I unload the driver before the suspend and reload it after. A small script in the directory /lib/systemd/system-sleep/ will take care of it automagically.

This my first post - can I insert the script here?

[penalvch (penalvch)]

Paulo Dias, thank you for reporting this and helping make Ubuntu better.

Could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1559805

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[brett hassall (brett-hassall)]

ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompositorRunning: None
DistUpgraded: Fresh install
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd]
MachineType: Dell Inc. Latitude E6440
Package: xorg (not installed)
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=33d1172e-10e6-48c8-b8b6-124083301aac ro splash quiet
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Tags: xenial ubuntu
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 02/02/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0K9GNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA10:bd02/02/2015:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn0K9GNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

apport information

[brett hassall (brett-hassall)]

Thanks Christopher.

I just gave it a go (had to install xdiagnose, apport & python-apport).

Had a few problems:
first run crashed when i asked to view the report
second run was still pushing out dots after 15 min so I killed it
third run ran to completion

How do I tell if it worked?

Regards
Brett
0417 215 931

On 11 June 2016 at 23:10, Christopher M. Penalver <
<email address hidden>> wrote:

> Paulo Dias, thank you for reporting this and helping make Ubuntu better.
>
> Could you please run the following command once from a terminal by
> ensuring you have the package xdiagnose installed, and that you click the
> Yes button for attaching additional debugging information:
> apport-collect -p xorg 1559805
>
> When reporting xorg related bugs in the future, please do so via the
> above method. You can learn more about this functionality at
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Changed in: xorg (Ubuntu)
> Importance: High => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1559805
>
> Title:
> suspend not working with latest xenial and kernel 4.4.0
>
> Status in xorg package in Ubuntu:
> Incomplete
>
> Bug description:
> suspend stops but never finishes and needs a reboot
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: xorg 1:7.7+13ubuntu3
> ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
> Uname: Linux 4.4.0-15-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> CurrentDesktop: KDE
> Date: Sun Mar 20 22:45:50 2016
> EcryptfsInUse: Yes
> InstallationDate: Installed on 2015-10-04 (168 days ago)
> InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
> ProcEnviron:
> LANGUAGE=
> TERM=xterm
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> SHELL=/bin/bash
> SourcePackage: xorg
> Symptom: display
> UpgradeStatus: Upgraded to xenial on 2016-03-17 (3 days ago)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+subscriptions
>

[penalvch (penalvch)]

brett hassall, it will help immensely if you filed a new report (not apport-collect to this one) with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

[brett hassall (brett-hassall)]

Chris

Is this still helpful given the move from xorg -> linux by Timo?

It seems more link a linux driver problem. I don't think I even have the
xorg radeon/ati driver installed. I did try installing it to see if it
helped but the suspend would still hang.

Thanks
Brett
0417 215 931

On 19 June 2016 at 04:47, Christopher M. Penalver <
<email address hidden>> wrote:

> brett hassall, it will help immensely if you filed a new report (not
> apport-collect to this one) with Ubuntu by ensuring you have the package
> xdiagnose installed, and that you click the Yes button for attaching
> additional debugging information running the following from a terminal:
> ubuntu-bug xorg
>
> Also, please feel free to subscribe me to it.
>
> For more on why this is helpful, please see
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Attachment removed: "xdpyinfo.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684644/+files/xdpyinfo.txt
>
> ** Attachment removed: "XorgLogOld.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684643/+files/XorgLogOld.txt
>
> ** Attachment removed: "XorgLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684642/+files/XorgLog.txt
>
> ** Attachment removed: "ProcModules.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684640/+files/ProcModules.txt
>
> ** Attachment removed: "UdevDb.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684641/+files/UdevDb.txt
>
> ** Attachment removed: "ProcCpuinfo.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684638/+files/ProcCpuinfo.txt
>
> ** Attachment removed: "ProcInterrupts.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684639/+files/ProcInterrupts.txt
>
> ** Attachment removed: "Lsusb.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684637/+files/Lsusb.txt
>
> ** Attachment removed: "Lspci.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684636/+files/Lspci.txt
>
> ** Attachment removed: "LightdmLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684635/+files/LightdmLog.txt
>
> ** Attachment removed: "LightdmGreeterLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684634/+files/LightdmGreeterLog.txt
>
> ** Attachment removed: "LightdmDisplayLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684633/+files/LightdmDisplayLog.txt
>
> ** Attachment removed: "JournalErrors.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684632/+files/JournalErrors.txt
>
> ** Attachment removed: "BootLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684629/+files/BootLog.txt
>
> ** Attachment removed: "DpkgLog.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684631/+files/DpkgLog.txt
>
> ** Attachment removed: "CurrentDmesg.txt"
>
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1559805/+attachment/4684...

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]