From: Stefan Seyfried <seife@suse.de>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-kernel@vger.kernel.org, pavel@ucw.cz, kevin-linux-kernel@scrye.com
Subject: Re: FYI: my current bigdiff
Date: Sat, 11 Sep 2004 18:41:56 +0200 [thread overview]
Message-ID: <41432AD4.2090003@suse.de> (raw)
In-Reply-To: <200409101646.01558.bjorn.helgaas@hp.com>
Bjorn Helgaas wrote:
> I'm completely ignorant about how swsusp works; I guess this is my
> chance to learn. "pci=routeirq" just causes us to do all the PCI
> ACPI IRQ routing at boot-time, before the drivers start up. This
> happens in pci_acpi_init(), which is a subsys_initcall that is run
> at initial boot-time, but (I assume) not during a resume.
a resume is basically a fresh boot, including hardware initialization by
the compiled-in drivers (but not modules) but before starting init /
entering initrd, the old system state is read from swap, copied back and
somehow we continue where we left off at suspend time. Now the resume
methods of all device drivers are called, processes are restarted and we
are back in the game. (At least this is how i understood it all :-)
I can easily imagine that a driver with a slightly broken suspend /
resume method may fail without pci=routeirq if it does not do the irq
routing correctly during resume. It may work with pci=routeirq since
then everything is prepared for it before the resume actually happens.
Kevin may get away with unloading the usb host controller and the
prism54 drivers before suspend and reloading them after resume.
Stefan
next prev parent reply other threads:[~2004-09-11 16:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-09 13:44 FYI: my current bigdiff Pavel Machek
2004-09-10 4:13 ` Kevin Fenzi
2004-09-10 9:44 ` Pavel Machek
2004-09-10 17:27 ` Kevin Fenzi
2004-09-10 22:46 ` Bjorn Helgaas
2004-09-11 16:41 ` Stefan Seyfried [this message]
2004-09-11 18:55 ` Kevin Fenzi
2004-09-11 18:50 ` Kevin Fenzi
2004-09-13 22:06 ` Bjorn Helgaas
2004-09-12 8:54 ` Stefan Schweizer
2004-09-12 9:23 ` Stefan Seyfried
2004-09-12 9:32 ` Stefan Schweizer
2004-09-12 11:39 ` Stefan Seyfried
2004-09-12 21:03 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41432AD4.2090003@suse.de \
--to=seife@suse.de \
--cc=bjorn.helgaas@hp.com \
--cc=kevin-linux-kernel@scrye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox