[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070305133221.GA28780@elte.hu>
Date: Mon, 5 Mar 2007 14:32:21 +0100
From: Ingo Molnar <mingo@...e.hu>
To: "Michael S. Tsirkin" <mst@...lanox.co.il>
Cc: Avi Kivity <avi@...ranet.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Jens Axboe <jens.axboe@...cle.com>,
Pavel Machek <pavel@....cz>, Adrian Bunk <bunk@...sta.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>, linux-pm@...ts.osdl.org,
Michal Piotrowski <michal.k.k.piotrowski@...il.com>,
Daniel Walker <dwalker@...sta.com>, Len Brown <lenb@...nel.org>
Subject: Re: [patch] KVM: T60 resume fix
* Michael S. Tsirkin <mst@...lanox.co.il> wrote:
> > could you try 's2ram' from http://suspend.sf.net ? It's basically
> > equivalent to 'echo mem > /sys/power/state', but you can usually also
> > see the reason why it doesnt resume, on the vga console. (by default the
> > kernel doesnt resume the t60's vga properly)
>
> OK, I'll give it a try. Do I have to shut down X or is it enough to
> switch to another VT?
s2ram takes care of that on your behalf.
> > on my box resume works, but it's incredibly slow.
>
> I guess it is possible that what I mistook for a hang was actually an
> incredibly slow system, and that it would resume, eventually. I waited
> for 5 min and gave up.
5 min should be enough to have the box pingable again.
> However, after resume was completed, system would hang on the *next*
> suspend to ram.
>
> Ingo, do you see this behaviour, or can you suspend/resume any number
> of times?
havent tried that yet - first trying to figure out why the first resume
misbehaves ;)
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists