Messages in this thread | | | Date | Wed, 25 Oct 2006 08:46:13 -0700 | From | Andrew Morton <> | Subject | Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) |
| |
> On Wed, 25 Oct 2006 12:43:18 +0200 Pavel Machek <pavel@ucw.cz> wrote: > Hi! > > > > > (cc-ed to public list) > > > > > > > > > Andrew Morton <akpm@osdl.org> wrote: > > > > > > > > > > > and I'm not having much luck. See > > > > > > > > > > > > http://userweb.kernel.org/~akpm/s5000340.jpg and > > > > > > http://userweb.kernel.org/~akpm/s5000339.jpg > > > > > > > > > > Running an UP kernel and disabling local APIC avoided the oopses and > > > > > allowed me to confirm that it was leaking. whoops. > > > > > > > > I wonder why everyone but me sees those APIC problems? > > > > > > > > Anyway, there's one more problem in -rc1: boot order changed, and (at > > > > least with paralel boot options), swsusp gets initialized *after* > > > > swsusp => bad, but should be easy to fix. > > > > > > 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.
- 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/
| |