Bill Nesheim wrote:
Detlef [email protected] wrote:
Hi,
with b111a now I can boot again my Toshiba M9.
1.I discoverred that Power Management seems no longer to work.
(The fan is blowing like hell and "kstat -m cpu_info" shows in
currentClock_Hz 2001000000
but
supported_frequencies_Hz
800000000:1200000000:1600000000:2000000000:2001000000
New Bug with b111a ?
My R600 now boots as well with 101a, but I see much the same thing.
System is idle, on battery power, but seems to be running at full speed:
nesh...@billn:~$ mpstat 5
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys
wt idl
0 179 0 8 328 113 237 5 18 5 0 970 2 2
0 96
1 165 0 12 137 67 243 8 18 5 0 979 2 2
0 97
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys
wt idl
0 1170 0 6 468 228 482 5 50 23 0 3519 3 5
0 93
1 811 0 35 141 67 526 7 45 23 0 1358 2 4
0 93
CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys
wt idl
0 0 0 2 308 103 163 1 16 2 0 394 1 1
0 98
1 0 0 5 125 65 191 3 16 2 0 2066 1 1
0 99
^C
nesh...@billn:~$ pfexec kstat -m cpu_info | grep _Hz
current_clock_Hz 1401000000
supported_frequencies_Hz
800000000:1200000000:1400000000:1401000000
current_clock_Hz 1401000000
supported_frequencies_Hz
800000000:1200000000:1400000000:1401000000
nesh...@billn:~$ uname -a
SunOS billn 5.11 snv_111a i86pc i386 i86pc Solaris
nesh...@billn:~$
nesh...@billn:~$ prtdiag
System Configuration: TOSHIBA PORTEGE R600
BIOS Configuration: TOSHIBA Version 1.80 02/20/2009
The current_clock_Hz is a little deceiving. The Power Aware Dispatcher
results in much more frequent P-State transitions. Try running
/usr/bin/powertop for better information.
Mark
...
2. I also have the impression that the boot up is much more disk-io
intensiv and takes much more time (can't identify yet directly)
3. Also: After the boot I see dhcpagent/1 consuming 50 % CPU (looks like
1 core) and the nwam applet will not show up in the gnome panel. I first
have to "kill -9" the dhcpagent, then the nwam applet comes up and the
cpu consuming goes away.
(Ok, that looks like a known bug)
Any comments ? Anyone else seeing this too.
Thanks
Detlef
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
_______________________________________________
indiana-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
