Checking usage of second CPU on a SunFire 280R
2007-12-25 1:47:00
I have just restarted a pretty new Sunfire 280 R with two 900 MHz CPUs.
I remember to have seen two % entries in the column CPU in the output
of prstat before the reboot. Now after the reboot prstat output looks
like on a single user machine
PID USERNAME SIZE RSS STATE PRI NICE TIME CPU PROCESS/NLWP
1121 root 944K 824K sleep 60 0 0:00.00 0.3% rm/1
566 root 17M 11M sleep 58 0 0:00.00 0.0% FrontBase/11
1123 root 1600K 1376K cpu0 58 0 0:00.00 0.0% prstat/1
398 majie 3864K 2784K sleep 58 0 0:00.00 0.0% imapd/1
341 root 3000K 1512K sleep 58 0 0:00.00 0.0% sshd/1
...
I checked /var/adm/messages and found
Aug 7 14:12:16 sunfire rootnex: [ID 349649 kern.info] mc-us30 at root:
SAFARI 0x0 0x400000 ...
Aug 7 14:12:16 sunfire genunix: [ID 936769 kern.info] mc-us30 is
/memory-controller at 0,400000
Aug 7 14:12:16 sunfire rootnex: [ID 349649 kern.info] mc-us31 at root:
SAFARI 0x1 0x400000 ...
Aug 7 14:12:16 sunfire genunix: [ID 936769 kern.info] mc-us31 is
/memory-controller at 1,400000
Aug 7 14:12:17 sunfire ebus: [ID 521012 kern.info] se0 at ebus0:
offset 1,400000
Aug 7 14:12:17 sunfire genunix: [ID 936769 kern.info] se0 is
/pci at 8,700000/ebus at 5/serial at 1,400000
Aug 7 14:12:17 sunfire unix: [ID 987524 kern.info] cpu0:
SUNW,UltraSPARC-III+ (upaid 0 impl 0x15 ver 0x23 clock 900 MHz)
Aug 7 14:12:17 sunfire unix: [ID 987524 kern.info] cpu1:
SUNW,UltraSPARC-III+ (upaid 1 impl 0x15 ver 0x23 clock 900 MHz)
Aug 7 14:12:17 sunfire unix: [ID 721127 kern.info] cpu 1
initialization complete - online
Aug 7 14:12:19 sunfire ebus: [ID 521012 kern.info] su0 at ebus0:
offset 1,3062f8
Aug 7 14:12:19 sunfire genunix: [ID 936769 kern.info] su0 is
/pci at 8,700000/ebus at 5/rsc-control at 1,3062f8
Aug 7 14:12:19 sunfire ebus: [ID 521012 kern.info] su1 at ebus0:
offset 1,3083f8
There is no line for CPU 0. Does this mean that only one CPU is active?
How can I check whether both CPUs are up and running fine?
Thanks a lot in advance,
Andreas
Comments
Got something to say?
You must be logged in to post a comment.
