* swsusp APIC oopsen (was Re: swsusp ooms) [not found] ` <20061014004046.670ddd76.akpm@osdl.org> @ 2006-10-14 8:22 ` Pavel Machek 2006-10-14 8:32 ` Pavel Machek 0 siblings, 1 reply; 6+ messages in thread From: Pavel Machek @ 2006-10-14 8:22 UTC (permalink / raw) To: Andrew Morton; +Cc: Rafael J. Wysocki, kernel list 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. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: swsusp APIC oopsen (was Re: swsusp ooms) 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 0 siblings, 1 reply; 6+ messages in thread From: Pavel Machek @ 2006-10-14 8:32 UTC (permalink / raw) To: Andrew Morton; +Cc: Rafael J. Wysocki, kernel list On Sat 2006-10-14 10:22:37, Pavel Machek 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". Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: swsusp APIC oopsen (was Re: swsusp ooms) 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 0 siblings, 1 reply; 6+ messages in thread From: Andrew Morton @ 2006-10-14 8:51 UTC (permalink / raw) To: Pavel Machek; +Cc: Rafael J. Wysocki, kernel list On Sat, 14 Oct 2006 10:32:27 +0200 Pavel Machek <pavel@ucw.cz> wrote: > On Sat 2006-10-14 10:22:37, Pavel Machek 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? ^ permalink raw reply [flat|nested] 6+ messages in thread
* swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) 2006-10-14 8:51 ` Andrew Morton @ 2006-10-25 10:43 ` Pavel Machek 2006-10-25 15:46 ` Andrew Morton 0 siblings, 1 reply; 6+ messages in thread From: Pavel Machek @ 2006-10-25 10:43 UTC (permalink / raw) To: Andrew Morton; +Cc: Rafael J. Wysocki, kernel list, Greg KH 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? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) 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 0 siblings, 1 reply; 6+ messages in thread From: Andrew Morton @ 2006-10-25 15:46 UTC (permalink / raw) To: Pavel Machek; +Cc: rjw, linux-kernel, greg > 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: swsusp initialized after SATA (was Re: swsusp APIC oopsen (was Re: swsusp ooms)) 2006-10-25 15:46 ` Andrew Morton @ 2006-10-25 16:51 ` Pavel Machek 0 siblings, 0 replies; 6+ messages in thread From: Pavel Machek @ 2006-10-25 16:51 UTC (permalink / raw) To: Andrew Morton; +Cc: rjw, linux-kernel, greg 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. ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-10-28 4:52 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[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 is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox