Mailinglist Archive: opensuse-factory (904 mails)

[Felix Miata <mrmazda@xxxxxx>]

On 2008/04/07 12:11 (GMT+0200) Dominique Leuenberger apparently typed:

> > > > On 4/7/2008 at 02:11, Felix Miata <mrmazda@xxxxxx> wrote:

> > This seems solved by including maxcpus=1 on cmdline.

> I would never dare to call maxcpus=1 being a 'solution' to any problem. 
> Everybody going out to buy some C2d, 3core, 4 core cpus and then use 
> maxcpus=1? I hope not!

Do you know the meaning of "seems"? Did you see anyone using multiple CPUs or 
multicore CPU reply in thread that he sees the same problem? Did you see anyone 
reply in thread that he sees the same problem? Did you see
anyone but me still using 2.6.24 kernels? Don't you suppose anyone who might 
see this problem on a multiple core system would rather have a suboptimal 
system than a non-functional system?

I believe "seems solved" is a clue that this could be a problem only for those 
with single core/single CPUs, and maybe only for those whose hardware closely 
matches mine Also it's better than the many threads where
problems are described but never have any confirmation or solution or 
workaround of any kind noted for Googlers who encounter the same or similar 
problem.
-- 
"Either the constitution controls the judges, or the
judges rewrite the constitution." Judge Robert Bork

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx