Re: [patch 3/3] clockevents: Fix resume logic - updated version

From: Rafael J. Wysocki
Date: Fri May 11 2007 - 17:04:28 EST


On Friday, 11 May 2007 23:02, Rafael J. Wysocki wrote:
> On Friday, 11 May 2007 22:28, Andrew Morton wrote:
> > On Fri, 11 May 2007 22:10:24 +0200
> > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote:
> >
> > > > > Index: linux-2.6.21/drivers/acpi/hardware/hwsleep.c
> > > > > ===================================================================
> > > > > --- linux-2.6.21.orig/drivers/acpi/hardware/hwsleep.c
> > > > > +++ linux-2.6.21/drivers/acpi/hardware/hwsleep.c
> > > > > @@ -200,10 +200,10 @@ acpi_status acpi_enter_sleep_state_prep(
> > > > > return_ACPI_STATUS(status);
> > > > > }
> > > > >
> > > > > - status = acpi_evaluate_object(NULL, METHOD_NAME__GTS, &arg_list, NULL);
> > > > > + /*status = acpi_evaluate_object(NULL, METHOD_NAME__GTS, &arg_list, NULL);
> > > > > if (ACPI_FAILURE(status) && status != AE_NOT_FOUND) {
> > > > > return_ACPI_STATUS(status);
> > > > > - }
> > > > > + }*/
> > > > >
> > > > > /* Setup the argument to _SST */
> > > > >
> > > >
> > > > I tested this against Thomas's original patch (below). Still hangs, in the
> > > > same way.
> > >
> > > Well, I'm out of ideas. :-(
> > >
> > > Could you please send me the Vaio's DSDT?
> >
> > Maybe I should send you the Vaio ;)
>
> Well, machines with so much potential of exposing problems are priceless. ;-)
>
> > I have this 1999-era pre-ACPI, pre-everything-else Dual-PIII-based
> > Supermicro machine and it just *always* works. Sigh.
> >
> >
> > hm, Fedora don't seem to want to give me an RPM which contains acpidump and
> > all the yum servers are featuring scrogged checksums. I could build it, I
> > guess, but there's a principle involved ;)
> >
> > http://userweb.kernel.org/~akpm/dsdt is /proc/acpi/dsdt. Is that OK?
>
> Yes, thanks.

Hmm, have you tried to do 'echo shutdown > /sys/power/disk' before the
hibernation?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/