On Sun, Mar 15, 2009 at 8:26 AM, Andre Lue <sik3...@yahoo.com> wrote:
> Still only 1 cpu showing with snv_109 on intel badaxe 2 with quad core? Can 
> anyone offer any guidance on this. This occurs in the EON RAM based image 
> list above. Any help is greatly appreciated.

Hi Andre, sorry, after a night of reading the first 400 pages of
"Learning Shell Programming in 24 hours" I am exhausted now and power
myself down in a minute, I just saw your msg. before I closed my mail
session. So I don't check any detail. But in a quick guess I would say
chances are it might be remotely related to what I wrote about last
year:

http://mail.opensolaris.org/pipermail/xwin-discuss/2008-August/002159.html

?

UPDATE: NO! It looks like a pretty different issue.
In your case it appears, as if the 2nd core has not been correctly
initialized indeed (or as if the 2nd core has been shut down /
disabled).
Could it be that the CPUID of your CoreDuo2 2.4GHz chip is just too
brand new, and hence not in the kernel's cpu-identification code yet?

The CPU identification detection mechanism code code can be tricky, I
recall that it has been a bit difficult to make qemu-system-x86_64 be
recognized as AMD64-capable 64bit cpu at first (by any Solaris 10 /11
kernel), Solaris only saw it as 32 bit 686. The Linux kernel does not
have so sophisticated checks and recognized it from the outset on
(also due to the fact, that most qemu.org developers still use linUX
as their primary devel platform).
But Juergen Keil soon found a fix for Solaris, back in October 2006
(for exact details and the files involved see qemu-discuss archives).

 Regards,
%martin

>
> uname -a
> SunOS eon 5.11 snv_109 i86pc i386 i86pc
>
> grep cpu /var/adm/messages
> Mar 14 22:21:52 eon unix: [ID 126719 kern.info] features: 
> 635f7fff<ssse3,cpuid,mwait,cmp,cx16,sse3,nx,asysc,sse2,sse,sep,pat,cx8,pae,mca,mmx,cmov,de,pge,mtrr,msr,tsc,lgpg>
> Mar 14 22:21:52 eon genunix: [ID 408114 kern.info] /cpus (cpunex0) online
> Mar 14 22:21:52 eon cpudrv: [ID 569748 kern.info] NOTICE: cpu_acpi: _TSS 
> package not found.
> Mar 14 22:21:52 eon cpudrv: [ID 227567 kern.warning] WARNING: cpu_acpi: error 
> parsing _TSS for CPU instance 0
> Mar 14 22:21:52 eon cpudrv: [ID 888440 kern.warning] WARNING: 
> cpudrv_mach_pm_init: instance 0: unable to initialize T-state support
> Mar 14 22:21:52 eon cpunex: [ID 114370 kern.info] cpu0 at cpus0
> Mar 14 22:21:52 eon genunix: [ID 408114 kern.info] /cpus/c...@0 (cpudrv0) 
> online
> Mar 14 22:21:53 eon unix: [ID 950921 kern.info] cpu0: x86 (chipid 0x0 
> GenuineIntel 6FB family 6 model 15 step 11 clock 2400 MHz)
> Mar 14 22:21:53 eon unix: [ID 950921 kern.info] cpu0: Intel(r) Core(tm)2 Quad 
> CPU    Q6600  @ 2.40GHz
>
> kstat -m cpu_info
> module: cpu_info                        instance: 0
> name:   cpu_info0                       class:    misc
>        brand                           Intel(r) Core(tm)2 Quad CPU    Q6600  
> @ 2.40GHz
>        chip_id                         0
>        clock_MHz                       2400
>        clog_id                         0
>        core_id                         0
>        cpu_type                        i386
>        crtime                          79.075183264
>        current_clock_Hz                2394000000
>        family                          6
>        fpu_type                        i387 compatible
>        implementation                  x86 (chipid 0x0 GenuineIntel 6FB 
> family 6 model 15 step 11 clock 2400 MHz)
>        model                           15
>        ncore_per_chip                  4
>        ncpu_per_chip                   4
>        pkg_core_id                     0
>        snaptime                        7322.708390132
>        state                           on-line
>        state_begin                     1237094512
>        stepping                        11
>        supported_frequencies_Hz        1596000000:2394000000
>        vendor_id                       GenuineIntel
>
> note ncore_per_chip looks right but psrinfo out ???
>
> psrinfo -v
> Status of virtual processor 0 as of: 03/15/2009 00:23:28
>  on-line since 03/14/2009 22:21:52.
>  The i386 processor operates at 2400 MHz,
>        and has an i387 compatible floating point processor.
> --
> This message posted from opensolaris.org
> _______________________________________________
> opensolaris-discuss mailing list
> opensolaris-discuss@opensolaris.org
>
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org

Reply via email to