Stephen, to clarify, do you have to do both of the following to WORKAROUND the
suspend issue, or only one:
/etc/init.d/tvheadend stop
modprobe -r dvb_usb_dib0700
** Description changed:
I'm running a fresh installation of 16.04 running the latest updates.
When I `pm-suspend` the computer
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Christopher,
I found the culprit and can confirm this is not a bug with the kernel
4.4.0.38. I attached a Sony PlayTV usb dvb tuner (dib0700) a little
while ago. I use it with TVHeadend which is installed as a background
service. After disconnecting it the system suspend/resume was working
Btw I booted a livecd of Ubuntu 16.04.1 with kernel 4.4.0-31 and that
can sleep/resume fine. So the issue seems to be with 4.4.0-38, at least
with me.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Christopher,
I'm happy to re-attempt the 6 pm-test commands again but to be clear on
how the resume trace is generated can you please confirm if the steps
below will suffice?
sudo su
echo freezer > /sys/power/pm_test
exit
sudo sh -c "sync && echo 1 > /sys/power/pm_trace &&
Slither, the article has been updated to better reflect what is
requested. To advise, one is to attach a resume trace after each of
those steps, not just run all the commands requested and then provide
one dmesg at the end.
--
You received this bug notification because you are a member of Kernel
Please provide the output of the following terminal command:
cat /sys/kernel/debug/suspend_stats
See attached file
** Attachment added: "suspend_stats"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629197/+attachment/4757919/+files/suspend_stats
--
You received this bug
In answer to the first 3 questions:
1. Which part of the process does the issue occur with, the suspend to
ram, or resuming from? Instantly after suspend from gui or terminal is
issued.
2. Please advise how you suspended specifically. For example:
Executing at a terminal pm-suspend
I've executed all the commands below and then attempted to create the
resume trace this command as per the instructions :
sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"
As expected my system froze. Display stilled showed my X11 session with
browser and terminal open but the
While booted into the latest non-daily mainline kernel, execute at a
terminal:
cat /proc/acpi/wakeup > wakeup
See attached file.
** Attachment added: "wakeup"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629197/+attachment/4757918/+files/wakeup
--
You received this bug
Slither, could you please provide the missing information following
https://wiki.ubuntu.com/DebuggingKernelSuspend ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1629197
Title:
It may have been 4.4.0.31 but booting to that via grub showed the same
issue so i think it may a change in more than just the kernel that's
caused this. Please note the only kernels installed on my machine now
are 4.4.0.38. I went down a path of elimination a week ago trying to
determine which was
Slither, to clarify, which good kernel did you update from, to get to
4.4.0.38?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1629197
Title:
Suspend not working
Status in linux
This issue didnt occur on an earlier kernel of never had an issue on
14.04 and an earlier kernel official of 16.04. I don't know which one.
I've only ever updated through the official ubuntu repos. After I
updated to kernel 4.4.0.38 I started having the suspend issue.
Trying to boot into all the
Slither, to clarify, did this issue not occur in a Ubuntu release prior
to 16.04?
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.8.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Christopher,
I installed the latest mainline upstream kernel 4.8.1
Still have the same issue.
nas@NAS:/tmp$ sudo dpkg -i *.deb
[sudo] password for nas:
Selecting previously unselected package linux-headers-4.8.1-040801.
(Reading database ... 400410 files and directories currently installed.)
Slither, thank you for reporting this and helping make Ubuntu better.
In order to allow additional upstream developers to examine the issue, at your
earliest convenience, could you please test the latest upstream kernel
available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ?
17 matches
Mail list logo
