On Fri, Jul 16, 2010 at 8:48 PM, Sunay Tripathi <tripathi.su...@gmail.com> wrote: > On 07/16/10 06:33 PM, Seth Goldberg wrote: >> >>> Bart/Seth, >>> >>> Yup. I double checked. Its enabled. BTW, disabling it doesn't >>> change anything. Do we keep any per thread data struct or >>> soemthing? I want to see if its one of our bugs or something >>> weird with the processor/bios (btw, its a supermicro machine >>> I think in past Solaris used to work pretty easily on them). >> >> What is the value of the boot-ncpus property? I would also dump the ACPI >> MADT to see what the BIOS is telling the OS wrt # of CPUs it can start. >> If you didn't get any warnings in the log or during boot that Solaris >> couldn't start CPUs, then it's likely that Solaris started all the CPUs >> that the BIOS specified. >> > > Good suggestion. I see this in boot logs > > Jul 16 18:42:31 orion1 unix: [ID 608849 kern.notice] NOTICE: System detected > 16 cpus, but only 8 cpu(s) were enabled during boot. > Jul 16 18:42:31 orion1 unix: [ID 458440 kern.notice] NOTICE: Use > "boot-ncpus" parameter to enable more CPU(s). See eeprom(1M). > > > BTW, for some reason when I do eeprom boot-ncpus=16, it gives > me a syntax error. Has the mechanism or syntax changed?
I think that from the grub you can add -B boot-ncpus=16 or change the existing argument to -B such that ",boot-ncpus=16" is appended. -- Mike Gerdts http://mgerdts.blogspot.com/ _______________________________________________ on-discuss mailing list on-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/on-discuss
