From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: rjw@sisk.pl, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms))
Date: Wed, 25 Oct 2006 16:51:17 +0000 [thread overview]
Message-ID: <20061025165117.GD5675@ucw.cz> (raw)
In-Reply-To: <20061025084613.4776ef76.akpm@osdl.org>
Hi!
> > > > Sorry, I meant:
> > > >
> > > > "sata is initialized *after* swsusp => bad".
> > >
> > > Which patch made this change, and why?
> >
> > CONFIG_PCI_MULTITHREAD_PROBE is the setting responsible, and IIRC
> > that's Greg's code.
> >
> > Now... what is the recommended way to wait for hard disks to become
> > online?
>
> The multithreaded probing is breaking (or at least altering) the initcall
> ordering guarantees. We should wait for all the probing kernel threads to
> terminate after processing each initcall level.
Can I read that as 'problem is bigger than swsusp, so someone else
(not Pavel :-) will solve it'?
Pavel
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-10-28 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20061009213359.7f2806b6.akpm@osdl.org>
[not found] ` <200610132231.08643.rjw@sisk.pl>
[not found] ` <20061013140000.329e8854.akpm@osdl.org>
[not found] ` <200610132307.47162.rjw@sisk.pl>
[not found] ` <20061014002504.1ab10ee9.akpm@osdl.org>
[not found] ` <20061014004046.670ddd76.akpm@osdl.org>
2006-10-14 8:22 ` swsusp APIC oopsen (was Re: swsusp ooms) Pavel Machek
2006-10-14 8:32 ` Pavel Machek
2006-10-14 8:51 ` Andrew Morton
2006-10-25 10:43 ` swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) Pavel Machek
2006-10-25 15:46 ` Andrew Morton
2006-10-25 16:51 ` Pavel Machek [this message]
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=20061025165117.GD5675@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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