Re: [2.6.17-rc5-mm2] crash when doing second suspend: BUG inarch/i386/kernel/nmi.c:174

[Andrew Morton]

On Wed, 7 Jun 2006 10:13:49 +1000
Nigel Cunningham <ncunningham@xxxxxxxxxxxxx> wrote:

> > the new CPU to get the same state as the old one just because it ends up
> > with the same logical CPU number?  Perhaps, but what if it doesn't even
> > have the same capabilities?  (Do we support heterogeneous CPUs anyway?)
> 
> Indeed. I'm also not sure that there's necessarily a guarantee that cpus will 
> be hotplugged in the same order. Perhaps those with more knowledge can 
> clarify there.

It all depends on what we mean by "per-cpu state".  If we were to remember
that "CPU 7 needs 0x1234 in register 44" then that would be wrong.  But
remembering some high-level functional thing like "CPU 7 needs to run the
NMI watchdog" is fine.  The CPU bringup code can work out whether that is
possible, and how to do it.


-
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/