Stewart Gebbie, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066467/comments/41
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yello
Hi,
No, given that the problem is resolved in Quantal, I do not need a fix
backported to Precise or earlier.
Thanks,
Stewart.
--
Stewart Gebbie
(C) +27 84 738 2899
On Sun, Jan 06, 2013 at 06:32:26PM -, Christopher M. Penalver wrote:
> Stewart Gebbie, as you noted this problem does not occ
Stewart Gebbie, could you please test for this problem in Raring (live
or installed) via http://cdimage.ubuntu.com/daily-live/current/ ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Stewart Gebbbie, regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066467/comments/45 :
>">> [Christopher M. Penalver] Did the suspend problem not occur in Precise if
>the virtualization feature was disabled in the BIOS? The suspend problem did
>occur if the feature w
>> [Christopher M. Penalver] Did the suspend problem not occur in Precise if
>> the virtualization feature was disabled in the BIOS?
The suspend problem did occur if the feature was disabled and if the
feature was enabled.
--
You received this bug notification because you are a member of Ubuntu
Stewart Gebbie, as you noted this problem does not occur in Quantal, did
you need a backport of the fix to a release prior to Quantal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Su
I was comparing the logs on Quantal versus Precise:
Below are the full logs on Precise /var/log/syslog at the time of
suspend (there are no log entries after: "init: anacron main process
(1107) killed by TERM signal"). As metioned earlier the one consistent
behaviour is that the syslogs are not re
Stewart Gebbie, thank you for specifying the BIOS options.
Did the suspend problem not occur in Precise if the virtualization
feature was disabled in the BIOS?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
The BIOS upgrade from R4060Y0 to R4070Y0 added an additional configuration
feature:
Advanced >> Intel (R) Virtualization Technology
"When enabled, a VVM can utilize the additional hardware capabilities
provided by Intel (R) Virtualization Technology"
Following the upgrade this feature was di
Stewart Gebbie, regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066467/comments/39 :
>"This issue is, however, resovled in Ubuntu 12.10 running: Linux barefoot
>3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012 x86_64 x86_64
>x86_64 GNU/Linux This is usin
This issue is, however, resovled in Ubuntu 12.10 running:
Linux barefoot 3.5.0-21-generic #32-Ubuntu SMP Tue Dec 11 18:51:59 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
This is using the R4070Y0 BIOS version on my Sony Vaio VGN-FW57GH, but
with the new virtualisation feature still disabled in the BIO
This issue is definitely still a problem in 12.04 even with the BIOS
upgrade to (R4070Y0) on Sony Vaio VGN-FW57GH with 3.7.1 and with
3.5.0-21-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/106
Stewart Gebbie, regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066467/comments/36 :
>"Upgraded to BIOS (R4070Y0) on Sony Vaio VGN-FW57GH. It is not yet conclusive,
>but it seems that this did not resovle the problem. With 3.7.1 a
>suspend/resume cycle still resulte
** Tags removed: bios-outdated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Suspend/Resume regression from 3.2.0-31 to 3.2.0-32
To manage notifications about this bug go to:
https:/
Upgraded to BIOS (R4070Y0) on Sony Vaio VGN-FW57GH.
It is not yet conclusive, but it seems that this did not resovle the
problem. With 3.7.1 a suspend/resume cycle still resulted in instablity
and no useful logs beyond the point of suspend.
Unfortunately, and I'm not sure if is related to the BI
Stewart Gebbie, as per http://www.sony-asia.com/support/product/vgn-
fw57gh/download an update is available for your BIOS (R4070Y0). If you
update to this, does it change anything?
** Tags added: bios-outdated
** Tags removed: kernel-bug-exists-upstream
** Tags added: needs-upstream-testing
** C
If I can work out what was going wrong when I tried to build the kernel
for the kernel bisect then I might be able to still help with finding
out where the issue was introduced.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Tested with:
linux-image-3.7.1-030701-generic_3.7.1-030701.201212171620_amd64.deb
linux-image-extra-3.7.1-030701-generic_3.7.1-030701.201212171620_amd64.deb
installed.
The behaviour was once again an unstable system after resume. The first
attempt simple resulted in a system that had hung
Confirmed presence of bug in mainline kernel 3.7.1
** Tags removed: needs-upstream-testing
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.7.1
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a mem
** Description changed:
Following the upgrade from 3.2.0-31-generic to 3.2.0-32-generic I now
experience problems when resuming from suspend mode.
Behaviour:
With 3.2.0-31-generic I experience stable behaviour and used the suspend
functionality regularly. Following the upgrade the
Stewart Gebbie, could you please test the latest upstream kernel available
(v3.7.1-raring) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It
will allow additional upstream developers to examine the issue. Once you've
tested the upstream kernel, please comment on which kernel version sp
Unfortunately another test run with 3.2.0-35-generic shows that the
kernel is still sometimes hanging on resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Suspend/Resume regressio
Stewart Gebbie, regarding your comments
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066467/comments/28 :
>"This problem may now be resolved in 3.2.0-35-generic."
So you now can suspend successfully?
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You receive
This problem may now be resolved in 3.2.0-35-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Suspend/Resume regression from 3.2.0-31 to 3.2.0-32
To manage notifications about
This is still a problem in 3.2.0-34-generic, forcing me to continue to
use 3.2.0-31-generic.
Unfortunately I was not able to get the kernel to build correctly when
attempting to follow the git kernel bisect guide from3.2.0-31-generic to
3.2.0-32-generic.
When I have some more time I will try agai
[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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
T
Stewart Gebbie, thank you for reporting this and helping make Ubuntu
better. The next step is to perform a kernel bisect from
3.2.0-31-generic to 3.2.0-32-generic, in order to identify the offending
commit(s). Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
Than
Please note 'apport-collect 1066467' was run while running
3.2.0-31-generic and not while running 3.2.0-32-generic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1066467
Title:
Suspend/Resume regres
apport information
** Tags added: apport-collected running-unity
** Description changed:
Following the upgrade from 3.2.0-31-generic to 3.2.0-32-generic I now
experience problems when resuming from suspend mode.
Behaviour:
With 3.2.0-31-generic I experience stable behaviour and use
29 matches
Mail list logo
