RE: node_to_cpumask x86_64 broken

From: YhLu
Date: Thu Feb 17 2005 - 01:18:34 EST


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@xxxxxxxxxxxxxxx
> 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@xxxxxxxxxxxxxxx More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
-
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/