lkml.org 
[lkml]   [2006]   [Jun]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [2.6.17-rc5-mm2] crash when doing second suspend: BUG in arch/i386/kernel/nmi.c:174
Hi!

> But the problem is that there's nothing which keeps
> track of whether the re-plugged cpus 1-N are the "same"
> as the unplugged 1-N, and so nothing can apply the same
> per-cpu settings to them. In the suspend/resume case
> they clearly are, but in the general remove/add case, do
> you really want 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?)

It works for some people, but it certainly falls into unsupported
category.

--
Thanks for all the (sleeping) penguins.
-
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/

\
 
 \ /
  Last update: 2006-06-08 22:16    [W:0.059 / U:2.780 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site