Skip to contentSkip to conversation

swsusp APIC oopsen (was Re: swsusp ooms)

DISCUSSION Pavel Machek 2 participants 6 messages Oct 14, 2006 – Oct 28, 2006 6 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#6 lore raw

Hi!

(cc-ed to public list)

Quoted 9 lines
Quoted 4 lines · Andrew Morton

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

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#7 lore raw
Quoted 11 lines · Pavel Machek

Hi!

(cc-ed to public list)

Quoted 7 lines
Quoted 4 lines · Andrew Morton

and I'm not having much luck. See

http://userweb.kernel.org/~akpm/s5000340.jpg and
http://userweb.kernel.org/~akpm/s5000339.jpg

Quoted 8 lines
Quoted 2 lines

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

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#8 lore raw
Quoted 17 lines · On Sat, 14 Oct 2006 10:32:27 +0200 Pavel Machek <[email protected]> wrote:
Quoted 16 lines · Pavel Machek

Hi!

(cc-ed to public list)

Quoted 9 lines
Quoted 4 lines · Andrew Morton

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?

Quoted 7 lines
Quoted 3 lines

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?

#9 lore raw

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

Hi!

Quoted 18 lines
Quoted 18 lines
Quoted 17 lines

(cc-ed to public list)

Quoted 9 lines
Quoted 4 lines · Andrew Morton

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.

Quoted 5 lines
Quoted 3 lines

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

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#10 lore raw

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

Quoted 25 lines · On Wed, 25 Oct 2006 12:43:18 +0200 Pavel Machek <[email protected]> wrote:

Hi!

Quoted 22 lines
Quoted 21 lines
Quoted 9 lines

(cc-ed to public list)

Quoted 7 lines
Quoted 4 lines · Andrew Morton

and I'm not having much luck. See

http://userweb.kernel.org/~akpm/s5000340.jpg and
http://userweb.kernel.org/~akpm/s5000339.jpg

Quoted 8 lines
Quoted 2 lines

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".

Quoted 7 lines
Quoted 1 line

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.

#11 lore raw

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

Hi!

Quoted 9 lines
Quoted 9 lines
Quoted 5 lines
Quoted 3 lines

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.

Quoted 6 lines
Quoted 2 lines

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

Signature · 1 line
Thanks for all the (sleeping) penguins.