Messages in this thread | | | Subject | borked sysfs system devices in 2.5.72 | From | Dave Hansen <> | Date | 17 Jun 2003 15:12:09 -0700 |
| |
The per-node numa meminfo files in 2.5.72 are broken, the only display node0's information. The devices are being properly registered: Registering sys device 'node0':c0423844 id:0 kobj:c042384c Registering sys device 'node1':c0423888 id:1 kobj:c0423890 Registering sys device 'node2':c04238cc id:2 kobj:c04238d4 Registering sys device 'node3':c0423910 id:3 kobj:c0423918
When I look at the 4 nodes files with: "cat /sys/devices/system/node/*/meminfo", I printed out some information: subsys_attr_show(kobj: c042384c, attr: c033ea30, page: e76ba000) subsys_attr_show(kobj: c0423890, attr: c033ea30, page: e76ba000) subsys_attr_show(kobj: c04238d4, attr: c033ea30, page: e76ba000) subsys_attr_show(kobj: c0423918, attr: c033ea30, page: e76ba000)
As you can see, the kobj is the one which belongs to the sys device, yet you do a to_subsys() on it. Why? struct subsystem * s = to_subsys(kobj);
I'm getting a 0 as the node ID out of pure dumb luck. Is the NUMA code broken or is sysfs?
-- Dave Hansen haveblue@us.ibm.com
- 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/
| |