On Mon, Feb 25, 2008 at 09:27:42PM -0800, Yinghai Lu wrote:I would suggest checking the SLIT distances -- On AMD boxes, if you have three different distances between nodes, then that system would be multiboard, and there is no way TSCs can be synced. On Intel boxes, if there are two different distances between nodes, then this would be a multi board/multi chassi box and TSCs won't be synced. This is a more generic solution and should work on Summit/Unisys boxes as well. (I am ignoring Intel CSI for now. It might need the same treatment as AMD) Comments? Kiran --
| Sam Ravnborg | Are Section mismatches out of control? |
| Karl Meyer | PROBLEM: 2.6.23-rc "NETDEV WATCHDOG: eth0: transmit timed out" |
| Bart Van Assche | Re: Is gcc thread-unsafe? |
| Adrian Bunk | Re: [Bug #10493] mips BCM47XX compile error |
git: | |
| Junio C Hamano | Re: [RFC/PATCH] git-branch: default to --track |
| Linus Torvalds | cleaner/better zlib sources? |
| Peter Stahlir | Git as a filesystem |
| Yossi Leybovich | corrupt object on git-gc |
| Manuel Wildauer | Re: Editing C with... |
| Mark Thomas | [i386/Thinkpad T41]USB mouse + Xorg obsd 4.1 |
| Stijn | Re: libiconv problem |
| Daniel Ouellet | Re: Router performance on OpenBSD and OpenBGPD |
| Felix Radensky | RE: e1000e "Detected Tx Unit Hang" |
| Johann Baudy | Packet mmap: TX RING and zero copy |
| David Miller | Re: 2.6.26/tg3 ping roundtrip times > 2000 ms on local network |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
