[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070425163145.GA6630@redhat.com>
Date: Wed, 25 Apr 2007 12:31:45 -0400
From: Dave Jones <davej@...hat.com>
To: "Antonino A. Daplas" <adaplas@...il.com>
Cc: Adrian Bunk <bunk@...sta.de>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
pavel@...e.cz, linux-pm@...ts.linux-foundation.org,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Rafael J. Wysocki" <rjw@...k.pl>,
James Simmons <jsimmons@...radead.org>, gregkh@...e.de,
linux-pci@...ey.karlin.mff.cuni.cz,
Jeremy Fitzhardinge <jeremy@...p.org>,
Richard Purdie <rpurdie@...ys.net>
Subject: Re: [3/3] 2.6.21-rc7: known regressions (v2)
On Wed, Apr 25, 2007 at 11:24:42PM +0800, Antonino A. Daplas wrote:
> On Wed, 2007-04-25 at 10:33 -0400, Dave Jones wrote:
> > On Wed, Apr 25, 2007 at 09:52:16PM +0800, Antonino A. Daplas wrote:
> > > > And have you tried the following settings:
> > > > FB_BACKLIGHT=y
> > > > ACPI_IBM=n
> > > > ACPI_VIDEO=n
> >
>
> BTW, there was one report where resume from RAM resulted in a screen
> full of garbage. It seems that the option acpi_sleep= (or s2ram -a3)
> did not work for him anymore. But it worked with s2ram and other
> options. So if you have s2ram, try:
>
> s2ram -f -s -a3
> s2ram -f -m -a3
> s2ram -f -p -m
> s2ram -f -p -s
I just did a pull of linus' tree, and it now works for me fine.
Adrian, I think we can remove this from the list.
I can't explain what fixed it (or even what caused it in the first place),
but it seems to be behaving itself.
Dave
--
http://www.codemonkey.org.uk
-
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