Mailinglist Archive: opensuse (963 mails)

["R. Tyler Croy" <tyler@xxxxxxxxxxxxx>]

Moin Lars!

R. Tyler Croy schrieb am Mittwoch, den 06. April 2011:

> Moin Lars!
>
> Lars M?ller schrieb am Dienstag, den 05. April 2011:
>
> > On Tue, Apr 05, 2011 at 09:59:59AM -0700, R. Tyler Croy wrote:
> > > I'm hoping this is the appropriate list, if not, flame away :0
> > >
> > >
> > > Anywhoo, I've consulted this page thoroughly: 
> > > <http://en.opensuse.org/SDB:Suspend_to_RAM>
> > >
> > >
> > > If I execute `s2ram -f` I can suspend just fine and resume *twice*, the 
> > > third
> > > time seems to always fail to suspend properly. X11 seems to lock up and I
> > > cannot switch to a virtual terminal either.
> > >
> > > It seems fairly reproducible on the third time as well.
> > >
> > >
> > >
> > > What can I do to track down what's causing the failure to suspend? I 
> > > don't want
> > > to pull the ripchord and go back to 11.3 or prematurely jump to 
> > > Tumbleweed (not
> > > quite ready for it yet), so what are my options here?
> >
> > Report it via bugzilla and quote the bug ID later here in this thread as
> > reference.  In the bug report add a pointer to this thread in the list
> > archive.
> >
> > I fear I see the very same issue with a Thinkpad X201.  It doesn't
> > matter if I use the default or desktop kernel.  Both cases I've only
> > tested with x86_64.
> >
> > First I thought it's caused by the SD memory card I'm using.
>
>
> I've gotten something somewhat reliable (i've been testing it off and on this
> evening).
>
> Using this variation of s2ram seems to give me reliable suspend/resume:
>
>     # s2ram -f -p -m


Scratch that, after leaving the laptop on all night I was unable tos uspend
this morning.

More experimentation to follow :(

- R. Tyler Croy
--------------------------------------
    Code: http://github.com/rtyler
 Chatter: http://identi.ca/agentdero
          http://twitter.com/agentdero