public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* node_to_cpumask  x86_64 broken
@ 2005-02-17  5:40 YhLu
  0 siblings, 0 replies; 4+ messages in thread
From: YhLu @ 2005-02-17  5:40 UTC (permalink / raw)
  To: Andi Kleen; +Cc: linux-kernel

I add some printk in k8_bus.c

node id = 0, node_to_cpumask = f
i= 0 ldtbus = 0
i= 1 ldtbus = 40100
i= 2 ldtbus = 0
node id = 1, node_to_cpumask = 0
i= 0 ldtbus = 0
i= 1 ldtbus = 0
i= 2 ldtbus = 70500
node id = 2, node_to_cpumask = 0
i= 0 ldtbus = 0
i= 1 ldtbus = 0
i= 2 ldtbus = 0
node id = 3, node_to_cpumask = 0
i= 0 ldtbus = 0
i= 1 ldtbus = 0
i= 2 ldtbus = 0
k8-bus.c: bus 5 has empty cpu mask
k8-bus.c: bus 6 has empty cpu mask
k8-bus.c: bus 7 has empty cpu mask

it seems node_to_cpu_mask broken.

I'm using 2.6.11-RC4.

YH

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: node_to_cpumask  x86_64 broken
  2005-02-17  6:30 node_to_cpumask x86_64 broken YhLu
@ 2005-02-17  6:21 ` Andi Kleen
  0 siblings, 0 replies; 4+ messages in thread
From: Andi Kleen @ 2005-02-17  6:21 UTC (permalink / raw)
  To: YhLu; +Cc: linux-kernel

On Wed, Feb 16, 2005 at 10:30:51PM -0800, YhLu wrote:
> forget about it. I found the reason:  I only put node 0 has RAM installed.

There is some problem with this code - it complains on a few machines.
However it's relatively harmless when this happens, so I haven't looked
it yet. Should perhaps take out the printk.

-Andi

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: node_to_cpumask  x86_64 broken
@ 2005-02-17  6:30 YhLu
  2005-02-17  6:21 ` Andi Kleen
  0 siblings, 1 reply; 4+ messages in thread
From: YhLu @ 2005-02-17  6:30 UTC (permalink / raw)
  To: YhLu, Andi Kleen; +Cc: linux-kernel

forget about it. I found the reason:  I only put node 0 has RAM installed.

YH 

> -----Original Message-----
> From: YhLu 
> Sent: Wednesday, February 16, 2005 9:40 PM
> To: Andi Kleen
> Cc: linux-kernel@vger.kernel.org
> Subject: node_to_cpumask x86_64 broken
> 
> I add some printk in k8_bus.c
> 
> node id = 0, node_to_cpumask = f
> i= 0 ldtbus = 0
> i= 1 ldtbus = 40100
> i= 2 ldtbus = 0
> node id = 1, node_to_cpumask = 0
> i= 0 ldtbus = 0
> i= 1 ldtbus = 0
> i= 2 ldtbus = 70500
> node id = 2, node_to_cpumask = 0
> i= 0 ldtbus = 0
> i= 1 ldtbus = 0
> i= 2 ldtbus = 0
> node id = 3, node_to_cpumask = 0
> i= 0 ldtbus = 0
> i= 1 ldtbus = 0
> i= 2 ldtbus = 0
> k8-bus.c: bus 5 has empty cpu mask
> k8-bus.c: bus 6 has empty cpu mask
> k8-bus.c: bus 7 has empty cpu mask
> 
> it seems node_to_cpu_mask broken.
> 
> I'm using 2.6.11-RC4.
> 
> YH
> -
> 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/
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

* RE: node_to_cpumask  x86_64 broken
@ 2005-02-17  6:37 YhLu
  0 siblings, 0 replies; 4+ messages in thread
From: YhLu @ 2005-02-17  6:37 UTC (permalink / raw)
  To: Andi Kleen; +Cc: linux-kernel

Yes. should not use prink(ERR.... 

YH

> -----Original Message-----
> From: Andi Kleen [mailto:ak@muc.de] 
> Sent: Wednesday, February 16, 2005 10:22 PM
> To: YhLu
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: node_to_cpumask x86_64 broken
> 
> On Wed, Feb 16, 2005 at 10:30:51PM -0800, YhLu wrote:
> > forget about it. I found the reason:  I only put node 0 has 
> RAM installed.
> 
> There is some problem with this code - it complains on a few machines.
> However it's relatively harmless when this happens, so I 
> haven't looked it yet. Should perhaps take out the printk.
> 
> -Andi
> 

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2005-02-17  6:24 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-17  6:30 node_to_cpumask x86_64 broken YhLu
2005-02-17  6:21 ` Andi Kleen
  -- strict thread matches above, loose matches on Subject: below --
2005-02-17  6:37 YhLu
2005-02-17  5:40 YhLu

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox