[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.1.00.0802200922590.7833@woody.linux-foundation.org>
Date: Wed, 20 Feb 2008 09:28:54 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Jeff Chua <jeff.chua.linux@...il.com>
cc: Jesse Barnes <jesse.barnes@...el.com>,
lkml <linux-kernel@...r.kernel.org>,
Dave Airlie <airlied@...ux.ie>,
"Rafael J. Wysocki" <rjw@...k.pl>, linux-acpi@...r.kernel.org,
suspend-devel List <suspend-devel@...ts.sourceforge.net>,
Greg KH <gregkh@...e.de>
Subject: Re: 2.6.25-rc2 System no longer powers off after suspend-to-disk.
Screen becomes green.
On Thu, 21 Feb 2008, Jeff Chua wrote:
>
> After inserting "return 0;" right at the top of those two functions, suspend
> (and power-off properly), and resume (without green screen) works just fine.
>
> I would like to know what they're for.
Try suspend-and-resume without X.
Also, try it on one of the more modern laptops - even *with* X.
Basically, the kernel wants to be able to do what X does, because it means
that when it works, it works _so_ much better than doing it in X. So
getting it working is definitely worth it.
That said, before you do anything else, try if suspend-to-RAM works.
That's the primary goal for this code anyway, and if it works that gives a
good hint. Suspend-to-disk is fundamentally different, and it's entirely
possible that for the suspend-to-disk case we should just say "screw
trying to suspend/resume graphics", since you'll have the BIOS resuming
text-mode anyway, and there are no performance or debugging advantages.
Linus
--
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