2.4.21-rc2-ac3/CPU

From: Lukasz Trabinski (lukasz@wsisiz.edu.pl)
Date: Tue May 27 2003 - 03:20:49 EST


Hello

I would like to ask, that why kernel 2.4.21-rc2-ac3 can't find all CPU?
It's look like this:

On 2.4.21-rc3:

May 26 20:31:04 oceanic kernel: CPU0<T0:1329040,T1:1063232,D:0,S:265808,C:1329040>
May 26 20:31:04 oceanic kernel: CPU2<T0:1329040,T1:531616,D:0,S:265808,C:1329040>
May 26 20:31:04 oceanic kernel: CPU3<T0:1329040,T1:265808,D:0,S:265808,C:1329040>
May 26 20:31:04 oceanic kernel: CPU1<T0:1329040,T1:797424,D:0,S:265808,C:1329040>
May 26 22:11:55 oceanic kernel: CPU 0 (0x0000) enabledProcessor #0 Pentium 4(tm)XEON(tm) APIC version 16
May 26 22:11:55 oceanic kernel: CPU 1 (0x0600) enabledProcessor #6 Pentium 4(tm)XEON(tm) APIC version 16
May 26 22:11:55 oceanic kernel: CPU 2 (0x0100) enabledProcessor #1 Pentium 4(tm)XEON(tm) APIC version 16
May 26 22:11:55 oceanic kernel: CPU 3 (0x0700) enabledProcessor #7 Pentium 4(tm)XEON(tm) APIC version 16
May 26 22:11:55 oceanic kernel: 4 CPUs total
[...]
May 26 20:31:04 oceanic kernel: Total of 4 processors activated (21233.66 BogoMIPS).


On 2.4.21-rc2-ac3:

May 27 01:08:38 oceanic kernel: CPU0<T0:1329088,T1:886048,D:8,S:443032,C:1329096>
May 27 01:08:38 oceanic kernel: cpu: 1, clocks: 1329096, slice: 443032
May 27 01:08:38 oceanic kernel: CPU1<T0:1329088,T1:443024,D:0,S:443032,C:1329096>
May 27 01:08:38 oceanic kernel: migration_task 0 on cpu=0
May 27 01:08:38 oceanic kernel: migration_task 1 on cpu=1
[...]
May 27 01:08:38 oceanic kernel: WARNING: No sibling found for CPU 0.
May 27 01:08:38 oceanic kernel: WARNING: No sibling found for CPU 1.
May 27 01:08:38 oceanic kernel: Total of 2 processors activated (10616.83 BogoMIPS).


I'm using the same .config file except that
2.4.21-rc2-ac3:
CONFIG_MPENTIUM4=y
2.4.21-rc3:
CONFIG_MPENTIUMIII=y
Anyway, I don't know, that which one is better choice? :)

If You want, I can send to you full dmesg or full .config file

--
lt
-
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/