Sorry, I'm not sure I follow; which of the two issues were you asking
about regarding function before Precise?
I've really only been a user since Precise, if I remember correctly.
Suspend and Hibernate have never both functioned. At various points,
using scripts and tricks (mostly kernel module
I have been keeping current on kernel and OS upgrades; the nature of
failure in both suspend and hibernate has shifted occasionally, but
neither has regained function since regressing around the beginning of
2013.
Details below; please advise on whether you would prefer a status change
here to
As of today, still tracking with the latest updates:
Hibernate appears to be functioning (re: bug 1153323).
The suspend failure has reverted to something that looks like this
original bug report. The machine enters what appears to be a suspend
power state (e.g., pulsing orange power light).
Public bug reported:
This is an ongoing problem that I have had ever since 12.04. Hibernate
and suspend have never both worked properly; at the moment, suspend in
Saucy puts the machine into sleep mode, but on wakeup, it kicks down to
boot from BIOS and never recovers the session.
I know, I know
Okay, here are some mainline kernel testing results. I tested
3.12.0-031200rc4.201310080738 and 3.12.0-999.201310090426
Additional note: this was a fresh install of Saucy; I did not upgrade
directly from Raring.
rc4 - suspend fails to make machine go down. Screen blinks, network
disconnects,
*** This bug is a duplicate of bug 1238097 ***
https://bugs.launchpad.net/bugs/1238097
** This bug has been marked a duplicate of bug 1238097
Sony Corporation VPCF119HX suspend/resume failure non-free: nvidia
--
You received this bug notification because you are a member of Kernel
*** This bug is a duplicate of bug 1238097 ***
https://bugs.launchpad.net/bugs/1238097
** This bug has been marked a duplicate of bug 1238097
Sony Corporation VPCF119HX suspend/resume failure non-free: nvidia
--
You received this bug notification because you are a member of Kernel
** Tags added: kernel-bug-exists-upstream
** Tags added: hibernate
--
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/1238097
Title:
Sony Corporation VPCF119HX suspend/resume failure
** Also affects: hibernate (Ubuntu)
Importance: Undecided
Status: New
--
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/1238097
Title:
Sony Corporation VPCF119HX suspend/resume
@jsalisbury - unfortunately (as usual), the testing process has
completely wrecked my display driver setup, so I'm now at the stage of
clearing out the upstream kernels and spend time trying to get back a
working X session. I'm afraid I won't be able to provide the additional
information described
As there has been no mailing list activity on this bug since it appeared
on 2014-01-21, would there be any use in cross-reporting it to the
kernel bugzilla? Or would that still be redundant?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu)
Status: Expired = New
--
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/1154867
Title:
[Sony VAIO VPCF119HX] suspend/resume failure non-free: nvidia
The problem has occurred in various forms since I started using Ubuntu
during Precise. There was a brief period in which it did work correctly;
I think that may have been during the Raring cycle. So technically it
may be a regression, but it isn't a new one, and I don't think I can
pinpoint the
Please do let me know if there is anything further that I can do to move
the bug off of incomplete.
--
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/1154867
Title:
[Sony VAIO VPCF119HX]
I have now re-run the full reporting process on the latest kernel from
today. That report is attached here. I have also truncated the report to
get it under 100 000 characters and sent that to the mailing list. I
will update here if it makes the list and therefore has a URL to which I
can link
**
And here is the URL:
http://thread.gmane.org/gmane.linux.power-management.general/42208
--
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/1154867
Title:
[Sony VAIO VPCF119HX]
** Description changed:
I have now reproduced this bug with suspend using only Xorg video
drivers and the latest kernel. The issue is that upon resume from
suspend, the computer kicks all the way down to the boot sequence and
cannot restore a session. A Kernal Oops is reported by apport
I have removed the addition of Hibernate to the workaround description.
Hibernate is also broken on this machine. I have not had time to create
and manage the second bug report for Hibernate, however.
** Description changed:
I have now reproduced this bug with suspend using only Xorg video
I have tried to recreate this with the following two mainline kernels:
v4.2-rc6-unstable
v4.2.0-999 (201508130157)
However, it is somewhat difficult to compare the behavior apples-to-
apples the way I normally do, as cpupower is not available for those
kernels (no linux-tools packages installed
** Attachment added: kern.log from session in which cpu freq control failed on
resume from suspend
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+attachment/227/+files/kern_log_cpu_resume_bug.txt
** Also affects: pm-utils (Ubuntu)
Importance: Undecided
Status:
Public bug reported:
Behavior:
CPU frequency management fails to re-engage on resume from suspend. On
resume, the CPUs are stuck around a single frequency (usually a low idle
frequency).
I use indicator-cpufreq for manual governor control. On resume,
indicator-cpufreq indicates the low
I have not noticed this problem on later kernels; I'm going to mark it
as "fix released" for Linux and "invalid" for pm-utils. I hope that's
the right course of action.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: pm-utils (Ubuntu)
Status:
22 matches
Mail list logo