swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms))

[Pavel Machek]

Hi!

> > > (cc-ed to public list)
> > > 
> > > > Andrew Morton <akpm@xxxxxxxx> 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?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/