Re: [CentOS] smp falls back to up mode on quad core

2008-05-28 Thread Julian Echave
Solved it!
After quite a lot of messing around...
It turns out i was booting with the acpi=off option, but for the BIOS to see
the 4 processors acpi has to be on.
The problem was that with acpi=on, boot hangs, unless pci=nommconf is added
to the boot options.

To summarize,

I now boot using the options

acpi = on pci=nommconf

Thanks.

Julian.


On Tue, May 27, 2008 at 6:29 PM, MHR <[EMAIL PROTECTED]> wrote:

> On Tue, May 27, 2008 at 1:41 PM, John R Pierce <[EMAIL PROTECTED]>
> wrote:
> > Julian Echave wrote:
> >>
> >> Sure, find below, I add other stuff as well. Note that there is some bug
> >> in the Bios. This does not prevent Centos to boot, and, since Windows
> sees
> >> all four processors, I reckon it shouldn't be the problem...?
> >
> >
> > yeah, looks like its probably broken ACPI data in the BIOS.  see if the
> > mainboard or system vendor has a BIOS update to fix this.   just because
> > operating system "X" works, doesn't mean its 'right'.
> >
>
> You can try adding 'noacpi' to your boot string in your grub.conf file
> and see if that helps.
>
> I have an AMD Athlon 64 x2 on an ECS mobo that is known to have a
> problem with acpi.  If I try to run without the noacpi switch, it runs
> very poorly and crashes or halts within minutes of booting, if it
> boots at all.  With the flag, it runs smooth as silk.
>
> mhr
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smp falls back to up mode on quad core

2008-05-27 Thread Julian Echave
Thanks. I'll try the acpi thing.
Regarding the Bios, I've got the last version.
Kubuntu has no problems either to see the 4 cores...
I'll see what I can do tomorrow.


On Tue, May 27, 2008 at 6:29 PM, MHR <[EMAIL PROTECTED]> wrote:

> On Tue, May 27, 2008 at 1:41 PM, John R Pierce <[EMAIL PROTECTED]>
> wrote:
> > Julian Echave wrote:
> >>
> >> Sure, find below, I add other stuff as well. Note that there is some bug
> >> in the Bios. This does not prevent Centos to boot, and, since Windows
> sees
> >> all four processors, I reckon it shouldn't be the problem...?
> >
> >
> > yeah, looks like its probably broken ACPI data in the BIOS.  see if the
> > mainboard or system vendor has a BIOS update to fix this.   just because
> > operating system "X" works, doesn't mean its 'right'.
> >
>
> You can try adding 'noacpi' to your boot string in your grub.conf file
> and see if that helps.
>
> I have an AMD Athlon 64 x2 on an ECS mobo that is known to have a
> problem with acpi.  If I try to run without the noacpi switch, it runs
> very poorly and crashes or halts within minutes of booting, if it
> boots at all.  With the flag, it runs smooth as silk.
>
> mhr
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smp falls back to up mode on quad core

2008-05-27 Thread MHR
On Tue, May 27, 2008 at 1:41 PM, John R Pierce <[EMAIL PROTECTED]> wrote:
> Julian Echave wrote:
>>
>> Sure, find below, I add other stuff as well. Note that there is some bug
>> in the Bios. This does not prevent Centos to boot, and, since Windows sees
>> all four processors, I reckon it shouldn't be the problem...?
>
>
> yeah, looks like its probably broken ACPI data in the BIOS.  see if the
> mainboard or system vendor has a BIOS update to fix this.   just because
> operating system "X" works, doesn't mean its 'right'.
>

You can try adding 'noacpi' to your boot string in your grub.conf file
and see if that helps.

I have an AMD Athlon 64 x2 on an ECS mobo that is known to have a
problem with acpi.  If I try to run without the noacpi switch, it runs
very poorly and crashes or halts within minutes of booting, if it
boots at all.  With the flag, it runs smooth as silk.

mhr
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smp falls back to up mode on quad core

2008-05-27 Thread John R Pierce

Julian Echave wrote:
Sure, find below, I add other stuff as well. Note that there is some 
bug in the Bios. This does not prevent Centos to boot, and, since 
Windows sees all four processors, I reckon it shouldn't be the problem...?



yeah, looks like its probably broken ACPI data in the BIOS.  see if the 
mainboard or system vendor has a BIOS update to fix this.   just because 
operating system "X" works, doesn't mean its 'right'.





___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] smp falls back to up mode on quad core

2008-05-27 Thread Julian Echave
Sure, find below, I add other stuff as well. Note that there is some bug in
the Bios. This does not prevent Centos to boot, and, since Windows sees all
four processors, I reckon it shouldn't be the problem...?



uname -a


Linux localhost.localdomain 2.6.18-53.1.21.el5PAE #1 SMP Tue May 20 10:03:06
EDT 2008 i686 i686 i386 GNU/Linux


cat  /proc/cpuinfo


processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 15
model name: Intel(R) Core(TM)2 Quad CPUQ6600  @ 2.40GHz
stepping: 11
cpu MHz: 2400.184
cache size: 4096 KB
physical id: 0
siblings: 1
core id: 0
cpu cores: 1
fdiv_bug: no
hlt_bug: no
f00f_bug: no
coma_bug: no
fpu: yes
fpu_exception: yes
cpuid level: 10
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx lm constant_tsc
up pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
bogomips: 4802.08

*
dmesg

Linux version 2.6.18-53.1.21.el5PAE ([EMAIL PROTECTED]) (gcc
version 4.1.2 20070626 (Red Hat 4.1.2-14)) #1 SMP Tue May 20 10:03:06 EDT
2008
BIOS-provided physical RAM map:
 BIOS-e820:  - 0009fc00 (usable)
 BIOS-e820: 0009fc00 - 000a (reserved)
 BIOS-e820: 000e - 0010 (reserved)
 BIOS-e820: 0010 - cf213000 (usable)
 BIOS-e820: cf213000 - cf215000 (reserved)
 BIOS-e820: cf215000 - cf2c8000 (usable)
 BIOS-e820: cf2c8000 - cf3e5000 (ACPI NVS)
 BIOS-e820: cf3e5000 - cf3e8000 (usable)
 BIOS-e820: cf3e8000 - cf3f3000 (ACPI data)
 BIOS-e820: cf3f3000 - cf3f4000 (usable)
 BIOS-e820: cf3f4000 - cf3ff000 (ACPI data)
 BIOS-e820: cf3ff000 - cf40 (usable)
 BIOS-e820: cf40 - d000 (reserved)
 BIOS-e820: f000 - f800 (reserved)
 BIOS-e820: fff0 - 0001 (reserved)
 BIOS-e820: 0001 - 00012c00 (usable)
3904MB HIGHMEM available.
896MB LOWMEM available.
found SMP MP-table at 000fe200
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
disabling kdump
NX (Execute Disable) protection: active
On node 0 totalpages: 1228800
  DMA zone: 4096 pages, LIFO batch:0
  Normal zone: 225280 pages, LIFO batch:31
  HighMem zone: 999424 pages, LIFO batch:31
DMI 2.4 present.
Using APIC driver default
Intel MultiProcessor Specification v1.4
Virtual Wire compatibility mode.
OEM ID:  Product ID:  APIC at: 0xFEE0
Processor #0 6:15 APIC version 20
Enabling APIC mode:  Flat.  Using 0 I/O APICs
BIOS bug, no explicit IRQ entries, using default mptable. (tell your hw
vendor)
Processors: 1
Allocating PCI resources starting at d200 (gap: d000:2000)
Detected 2400.184 MHz processor.
Built 1 zonelists.  Total pages: 1228800
Kernel command line: ro root=/dev/VolGroup00/LogVol00 acpi=off rhgb quiet
mapped APIC to d000 (fee0)
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Initializing CPU#0
CPU 0 irqstacks, hard=c074 soft=c072
PID hash table entries: 4096 (order: 12, 16384 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 4067796k/4915200k available (2078k kernel code, 46260k reserved,
859k data, 220k init, 3197740k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 4802.08 BogoMIPS
(lpj=2401041)
Security Framework v1.0.0 initialized
SELinux:  Initializing.
SELinux:  Starting in permissive mode
selinux_register_security:  Registering secondary module capability
Capability LSM initialized as secondary
Mount-cache hash table entries: 512
CPU: After generic identify, caps: bfebfbff 2010  
e3bd  0001
CPU: After vendor identify, caps: bfebfbff 2010  
e3bd  0001
monitor/mwait feature present.
using mwait in idle threads.
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 4096K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
CPU: After all inits, caps: bfebfbff 2010  0940 e3bd
 0001
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
Checking 'hlt' instruction... OK.
SMP alternatives: switching to UP code
Freeing SMP alternatives: 13k freed
CPU0: Intel(R) Core(TM)2 Quad CPUQ66

Re: [CentOS] smp falls back to up mode on quad core

2008-05-27 Thread John R Pierce

Julian Echave wrote:

Hi,
 
I'm running Centos 5.1 on an Intel Quad 2 Core with four Q6600 processors.
Despite Centos 5 supporting multiple cores (SPM), it doesn't seem to 
work for me:

1) a dmesg shows that only one processor is seen:
 "SPM alternatives: switching to UP code", etc.
2) file /proc/cpuinfo shows only one processor
3) top with option 1 (to toggle between seeing all processors or an 
average) shows only 1 processor.
 
I've googled this, and other people have found this kind of trouble, 
but I was not able to find any solutions.



it might help diagnose this if you paste the output of  'dmesg' at least 
up to that "SMP Alternatives" message and maybe a couple more lines 
after it...





___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] smp falls back to up mode on quad core

2008-05-27 Thread Julian Echave
Hi,

I'm running Centos 5.1 on an Intel Quad 2 Core with four Q6600 processors.
Despite Centos 5 supporting multiple cores (SPM), it doesn't seem to work
for me:
1) a dmesg shows that only one processor is seen:
 "SPM alternatives: switching to UP code", etc.
2) file /proc/cpuinfo shows only one processor
3) top with option 1 (to toggle between seeing all processors or an average)
shows only 1 processor.

I've googled this, and other people have found this kind of trouble, but I
was not able to find any solutions.

By the way: I've installed windows xp to see if it was a bios problem, but
windows sees the 4 processors just fine.

Any ideas?

Thanks,

Julian.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos