Re: [linux-pm] [RFC][PATCH 0/3] PM: Asynchronous suspend and resume

From: Rafael J. Wysocki
Date: Sun Aug 16 2009 - 06:29:42 EST


On Friday 14 August 2009, Rafael J. Wysocki wrote:
> On Friday 14 August 2009, Alan Stern wrote:
> > On Fri, 14 Aug 2009, Rafael J. Wysocki wrote:
> >
> > > On Friday 14 August 2009, Alan Stern wrote:
> > > > On Thu, 13 Aug 2009, Rafael J. Wysocki wrote:
> > > >
> > > > > > No, I've only tested it with a few selected drivers. I'm going to try the
> > > > > > "async everyone" scenario, though.
> > > > >
> > > > > On HP nx6325 booted with init=/bin/bash it doesn't pass the
> > > > > 'echo devices > /sys/power/pm_test && echo mem > /sys/power/state' test.
> > > > >
> > > > > The suspend part actually seems to work, but the resume part crashes
> > > > > miserably.
> > > >
> > > > Any details? Can you tell where it crashes?
> > >
> > > Unfortunately it ends up in a continuous flood of backtraces, so I can't
> > > say much.
> >
> > Same sort of thing happened with me, but it appeared to happen during
> > suspend. (I say "appeared" because the system froze for a while at the
> > start of the suspend until I hit a key. This may be related to all the
> > recent churn in the TTY layer, combined with the fact that I was using
> > a serial console. It didn't help -- none of the backtraces got sent
> > out the serial port.)
> >
> > > However, if I set async_suspend for all PCI devices, as well as for ACPI battery
> > > and i8042, everything apparently works, even with real suspend-resume.
> >
> > I think it would be worthwhile to track down these unknown problems and
> > dependencies. It won't be easy, though...
>
> Agreed.

One data point: I set async_syspend for all ACPI devices in addition to PCI
devices and that broke things.

Which isn't really strange given that PCI devices generally have ACPI
counterparts linked to them that I guess should be suspended later.

Thanks,
Rafael
--
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/