From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Pavel Machek <pavel@suse.cz>, Patrick Mochel <mochel@osdl.org>
Subject: swsusp resume doesn't sysdev_resume
Date: Mon, 11 Oct 2004 16:59:16 -0600
User-Agent: KMail/1.7
Cc: linux-kernel@vger.kernel.org
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200410111659.16373.bjorn.helgaas@hp.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 845
Lines: 20

Swsusp often fails on -mm kernels because sysdev_resume doesn't
get called in the resume path.  So things like ACPI IRQ links
used by modular drivers don't get restored.

We can work around this by using "pci=routeirq", so all the IRQ
setup gets done at boot-time, but that's an ugly hack, and I
expect that we'll trip over other sysdevs that need to be resumed
anyway.

I don't understand swsusp well enough to fix this.  It's not enough
to just call device_power_up() before device_resume(), because it
relies on sysdev_suspend() having been called before the suspend
image was created.

Any hints?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/