[opensuse] openSuSE 11.4: Suspend to RAM
Hi List, I recently upgraded to 11.4 (coming from 11.2), but now I'm having some major issues with S2RAM. It seems to work on first hand, but every few days it won't come up again. When I press the power button the screen goes on, and I can see some lines talking about enabling and disabling non-boot CPUs, but that is all. Doesn't react on any keypress etc, I have to hard-shut-down using the power button. This *had* been working flawlessly in 11.2, I easily got uptimes of 50-60 days with daily S2ram-resume cycles, and never ever had this problem. Today I tried several sleep/resume cycles in a row. I saw some message PM: Device 1-5.1 failed to resume async: error -110 but thing were working. However, related or not, when working with the machine (gimp) it seemed to fall dead. I could move the mouse, but that was it. No keypress/click accepted. Remote login showed X was at 100%CPU. I tried killing X, which did work, but left the system unusable (just black screen). Needed another reboot. Anyone having similar trouble? Or an idea what to look for? Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 12.05.2011 09:09, schrieb Peter Suetterlin:
I recently upgraded to 11.4 (coming from 11.2), but now I'm having some major issues with S2RAM.
It seems to work on first hand, but every few days it won't come up again. When I press the power button the screen goes on, and I can see some lines talking about enabling and disabling non-boot CPUs, but that is all. Doesn't react on any keypress etc, I have to hard-shut-down using the power button.
This *had* been working flawlessly in 11.2, I easily got uptimes of 50-60 days with daily S2ram-resume cycles, and never ever had this problem.
Today I tried several sleep/resume cycles in a row. I saw some message PM: Device 1-5.1 failed to resume async: error -110 but thing were working. However, related or not, when working with the machine (gimp) it seemed to fall dead. I could move the mouse, but that was it. No keypress/click accepted. Remote login showed X was at 100%CPU. I tried killing X, which did work, but left the system unusable (just black screen). Needed another reboot.
Anyone having similar trouble? Or an idea what to look for?
Not similar, just not being able to do any suspend to ram or disk at all. kind regards Kai-Uwe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 12 of May 2011 16:09:10 Peter Suetterlin wrote:
Hi List,
Hi,
I recently upgraded to 11.4 (coming from 11.2), but now I'm having some major issues with S2RAM.
It seems to work on first hand, but every few days it won't come up again. When I press the power button the screen goes on, and I can see some lines talking about enabling and disabling non-boot CPUs, but that is all. Doesn't react on any keypress etc, I have to hard-shut-down using the power button.
Suspend to RAM works here on 11.4 exactly once. If I try to suspend once again, the system hangs during resume. I have no idea how to debug this.
Pit Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Peter, auxsvr@gmail.com wrote:
Suspend to RAM works here on 11.4 exactly once. If I try to suspend once again, the system hangs during resume. I have no idea how to debug this.
Did you have 11.2/3 installed before? Did it work there? Pit -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 13 of May 2011 18:48:05 Peter Suetterlin wrote:
Hi Peter, Hi,
Did you have 11.2/3 installed before? Did it work there? This system was upgraded from 11.2-> 11.3 -> 11.4. In earlier versions suspend to RAM didn't even suspend, so the current situation is an improvement.
Pit Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, some update on this. I found a suspicious line in the syslog after some X lockups: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context Googling for that guided me to some launchpad discussion that traced this issue back to the nvidia driver and also mentioned that at the same time this bug causes suspend/resume trouble that (sometimes) can be resolved by adding "acpi_sleep=nonvs" to the kernel boot options. I'm trying this now, let's see how things go. Pit auxsvr@gmail.com wrote:
On Friday 13 of May 2011 18:48:05 Peter Suetterlin wrote:
Hi Peter, Hi,
Did you have 11.2/3 installed before? Did it work there? This system was upgraded from 11.2-> 11.3 -> 11.4. In earlier versions suspend to RAM didn't even suspend, so the current situation is an improvement.
Pit Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin@royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin@astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
auxsvr@gmail.com
-
Kai-Uwe Behrmann
-
Peter Suetterlin