I am not sure why power button and lid switch are not listed in
wakeup_source.
This seems fishy though:
Nov 14 23:35:57 ernie kernel: ACPI: button: The lid device is not compliant to
SW_LID.
This requires Dell's help to investigate.
** Also affects: dell
Importance: Undecided
Status:
Yes, it continues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726061
Title:
Inspiron 5565 suspend issues after 17.10 upgrade
To manage notifications about this bug go to:
I think it's not a userspace issue. A solution/workaround should come
from kernel or BIOS/EC.
First thing first, let's confirm all sources in "wakeup" are not culprit
here.
# echo EHC1 > /proc/acpi/wakeup
# echo XHC0 > /proc/acpi/wakeup
# systemctl suspend
... and see if this issue continues to
I first had to resume from suspending this morning. I ran journalctl -b
before and after attempting to suspend again with the lid open. The
attachment includes the lines added in between.
** Attachment added: "journalctl_output"
> On 14 Nov 2017, at 10:06 PM, Aaron Peromsik <1726...@bugs.launchpad.net>
> wrote:
>
> Perhaps this is no longer a kernel issue or at least no longer a
> regression. I am getting the same behavior with 4.14 and 4.13.11 and
> even the kernel from 17.04 . Normally when I am suspending at the end
Perhaps this is no longer a kernel issue or at least no longer a
regression. I am getting the same behavior with 4.14 and 4.13.11 and
even the kernel from 17.04 . Normally when I am suspending at the end of
the day I first close the laptop lid, then choose suspend from the menu
on the external
Upon initially booting either 4.13.11 or 4.14.0 I see 1 in active_count for
ACAD, and zeros elsewhere. When 4.14.0 has immediately resumed from suspend and
shows additional events from the lid and the power button, I have not touched
either of those in the course of attempting to suspend.
So it may be PNP0C0D:00 (lid switch), LNXPWRBN:00 (power button), or
ACAD wakes your system up.
Can you attach output of `cat /proc/acpi/wakeup` here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "wakeup_sources_4.14.0"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726061/+attachment/5008223/+files/wakeup_sources_4.14.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Kai-Heng
> On 13 Nov 2017, at 10:23 AM, Aaron Peromsik <1726...@bugs.launchpad.net>
> 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.
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
Still a few rounds of bisect remaining but this is where I am now:
# bad: [126f760ca94dae77425695f9f9238b731de86e32] rds: Fix incorrect statistics
counting
git bisect bad 126f760ca94dae77425695f9f9238b731de86e32
# good: [98e93e968e4947cd71c2eb69e323682daa453ee7] mac80211: Complete ampdu
work
It seems to be two separate issues,
> On 7 Nov 2017, at 10:03 PM, Aaron Peromsik <1726...@bugs.launchpad.net> wrote:
>
> To summarize my earlier comments: All the below relates to
> suspend/resume of 17.10.
>
> Suspend/resume works fine if I boot with the 4.10-based Ubuntu kernel
> from 17.04,
To summarize my earlier comments: All the below relates to
suspend/resume of 17.10.
Suspend/resume works fine if I boot with the 4.10-based Ubuntu kernel
from 17.04, or any 4.13 mainline kernel starting from 4.13.5 .
The mainline kernels from 4.13 through 4.13.4, upon which the Ubuntu
kernel is
Does v4.13 (not v4.13.11) have this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726061
Title:
Inspiron 5565 suspend issues after 17.10 upgrade
To manage notifications about this bug go
Tested with newest mainline kernels. 4.3.11 still works fine. 4.14.rc7
still fails to come out of suspend.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726061
Title:
Inspiron 5565 suspend issues
sorry, meant to say 4.13.11, not 4.3.11
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726061
Title:
Inspiron 5565 suspend issues after 17.10 upgrade
To manage notifications about this bug go to:
Tested a couple more kernels and it seems that the issue I have with
4.13.4 is not present in mainline 4.13.5, nor in 4.13.9. Resume worked
fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726061
4.14-rc6 is even worse -- I can't wake the machine after suspend at all,
except by rebooting with long-press of the power button.
I tested other mainline kernels too. All 4.13-based mainline kernels I
tested behave similar to the shipped Ubuntu kernel, from 4.13.4 down
back to 4.13rc1.
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
** Summary changed:
- Inspiron 5536 suspend issues after 17.10 upgrade
+ Inspiron 5565 suspend issues after 17.10 upgrade
** Description changed:
- On my Inspiron 5536, 17.10 seems to work fairly well, unless I try to
+ On my Inspiron 5565, 17.10 seems to work fairly well, unless I try to
21 matches
Mail list logo
