Comment 13 for bug 1726061

Kai-Heng

> On 13 Nov 2017, at 10:23 AM, Aaron Peromsik <email address hidden> wrote:
>
> But that bisection may be leading toward a dead end or at least a moot
> point. The behavior which I am calling "bad" there is different from
> what I am currently seeing in later RCs and in 4.14.0.
>
> In, for example, my last "bad" commit 126f760ca94, upon suspend the
> machine does actually suspend but can't wake.
>
> In 4.14rc6, 4.14rc8, and 4.14, now upon suspend I am seeing the display
> power off and everything spins down but only for a moment -- then it
> immediately resumes. wifi and graphics seem to work OK at that point.
> The main remaining problem is just failure to remain suspended.

Can you attach `cat /sys/kernel/debug/wakeup_sources` after the immediate resume?

>
> That is true at least upon first suspend. In one of those builds I did
> see a case where a second suspend would spin down, try to spin up, but
> although the display backlight did come back on the machine remained
> unresponsive.
>
> I am not sure why the later RCs and in particular rc6 switched to this
> new failure mode. In my earlier notes it's clear that they used to be
> failing more like the way 126f760ca94 still behaves.
>
> --
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1726061
>
> Title:
> Inspiron 5565 suspend issues after 17.10 upgrade
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
> suspend. Suspend shuts off the display but doesn't seem to actually
> shut off the CPU -- fans still run. When I move the mouse the display
> comes back on but upon entering my password sometimes the session
> crashes and I am dumped back to the login screen; sometimes the
> session is still there but wifi is either disabled (all wifi-related
> menu items gone) or visible (with question mark) but non-functional.
> In any case once I have suspended I cannot shut down or reboot any way
> other than the hard way, by holding the power button for several
> seconds. Doesn't seem to matter whether I am using X or Wayland.
>
> Suspend works mostly fine if I choose the 4.10 kernel from GRUB...
> although I am prompted for login more times than necessary on resume.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 17.10
> Package: linux-image-4.13.0-16-generic 4.13.0-16.19
> ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
> Uname: Linux 4.10.0-37-generic x86_64
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: aaron 2489 F.... pulseaudio
> /dev/snd/controlC1: aaron 2489 F.... pulseaudio
> CurrentDesktop: ubuntu:GNOME
> Date: Sun Oct 22 12:22:13 2017
> HibernationDevice: RESUME=UUID=3cc55560-1886-446c-8d60-15136ee14d32
> InstallationDate: Installed on 2016-12-25 (301 days ago)
> InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
> MachineType: Dell Inc. Inspiron 5565
> ProcFB: 0 amdgpudrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=c30eb880-24e4-41af-9203-feff0ab69c8c ro quiet splash vt.handoff=7
> RelatedPackageVersions:
> linux-restricted-modules-4.10.0-37-generic N/A
> linux-backports-modules-4.10.0-37-generic N/A
> linux-firmware 1.169
> SourcePackage: linux
> UpgradeStatus: Upgraded to artful on 2017-10-22 (0 days ago)
> dmi.bios.date: 07/20/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.0.2
> dmi.board.name: 0RVKF9
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A00
> dmi.chassis.type: 10
> dmi.chassis.vendor: Dell Inc.
> dmi.chassis.version: 1.0.2
> dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd07/20/2016:svnDellInc.:pnInspiron5565:pvr1.0.2:rvnDellInc.:rn0RVKF9:rvrA00:cvnDellInc.:ct10:cvr1.0.2:
> dmi.product.name: Inspiron 5565
> dmi.product.version: 1.0.2
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+subscriptions