Re: [osol-discuss] b111a: Power Management and nwam-issue ?
Paul Griffith writes: > I am still seeing issues with VirtualBox 2.2.2 and nwam. If you're seeing the 'dhcpagent' process spinning and consuming CPU time, then it's very likely to be the same CR that I cited. The fix for that problem was just integrated yesterday. > Running OS 2008.11, waiting for 2009.06 to hit release! 2008.11 is now ancient. Unless you really have a need to stick with that (a paid support contract would be a good reason), I'd suggest moving over to the 'http://pkg.opensolaris.org/dev' package authority. It won't help right away with this problem -- unless you're willing to build your own binaries, you'll need to wait for the fix to percolate through the system; probably around 4 weeks -- but it'll certainly allow you to pick up the fix as soon as it's available rather than waiting many months between the 'stable' releases. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b111a: Power Management and nwam-issue ?
I am still seeing issues with VirtualBox 2.2.2 and nwam. I reverted to doing the following: 1) add "e1000g0 static x.x.x.x/24" to /etc/nwam/llp 2) add "x.x.x.1" to /etc/defaultrouter 3) cp /etc/nsswitch.dns /etc/nsswitch.conf 4) add "name server ip" tpo /etc/resolv.conf pfexec restart nwam pfexec restart routing-setup I don't have time to troubleshoot right now, back to work for me. Running OS 2008.11, waiting for 2009.06 to hit release! Thanks Paul On Thu, 30 Apr 2009 08:03:51 -0400, Detlef drew...@sun.com wrote: Thanks James, I have seen that this comes from the vboxnet interface, where dhcpd and nwam has issues with. VirtualBox 2.2.2, which has been released recently fixed this. Detlef On 04/28/09 20:05, James Carlson wrote: Detlef drew...@sun.com writes: 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. This part sounds like CR 6743929. A fix for it has been code reviewed and should be integrated some time soon now. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b111a: Power Management and nwam-issue ?
Thanks James, I have seen that this comes from the vboxnet interface, where dhcpd and nwam has issues with. VirtualBox 2.2.2, which has been released recently fixed this. Detlef On 04/28/09 20:05, James Carlson wrote: Detlef drew...@sun.com writes: 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. This part sounds like CR 6743929. A fix for it has been code reviewed and should be integrated some time soon now. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b111a: Power Management and nwam-issue ?
Detlef drew...@sun.com writes: > 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. This part sounds like CR 6743929. A fix for it has been code reviewed and should be integrated some time soon now. -- James Carlson, Solaris Networking Sun Microsystems / 35 Network Drive71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b111a: Power Management and nwam-issue ?
> 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 200100 > but > supported_frequencies_Hz > 8:12:16:20:200100 > > New Bug with b111a ? Try to use powertop to check if the cpu is running at the lower speed. With the recent changes to the dispatcher, the cpu power management now defaults to "event-mode" and is much faster to return to run cpus at full cpu speed. To get back the old behaviour add "cpupm poll-mode" to /etc/power.conf. See also: http://opensolaris.org/jive/thread.jspa?messageID=319804 -- This message posted from opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
Re: [osol-discuss] b111a: Power Management and nwam-issue ?
Detlef drew...@sun.com 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 200100 but supported_frequencies_Hz 8:12:16:20:200100 New Bug with b111a ? The cpu_info kstat might be a little deceiving now that the power aware dispatcher has integrated. Try running /usr/bin/powertop. It might be more informative. 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. Any comments ? Anyone else seeing this too. Thanks Detlef ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
