Mark Haywood wrote: >> Rafael Vanoni wrote: >>> Hi folks >>> >>> On a system that does not support deep c-states, are these warnings >>> expected ? >> >> From reading the code, I'd expect them because we always assume that >> the system supports deep c-states and print these messages if no _CST >> is exported. But, no. It is a bad idea to print these messages on >> systems that aren't supporting deep c-states. It is a bug.
Yeah, these messages should be put into the log instead of on the screen. > > We should probably do something similar to what Anup did for T-states. > He used dtrace probes for these type of errors. > What do the dtrace probes mean here? These messages only output during the boot, right? so dtrace probes will never be hitted after boot? -Aubrey >> >>> >>> >>> NOTICE: cpu_acpi: _CST evaluate failure >>> WARNING: cpu_acpi: error parsing _CST for CPU 1 >>> NOTICE: cpu_idle_init: Failed to cache ACPI C-state data >>> >>> WARNING: cpupm_init: processor 1: unable to initialize C-state >>> support NOTICE: cpu_acpi: _CST evaluate failure >>> WARNING: cpu_acpi: error parsing _CST for CPU 2 >>> NOTICE: cpu_idle_init: Failed to cache ACPI C-state data >>> >>> WARNING: cpupm_init: processor 2: unable to initialize C-state >>> support .. >>> >>> >>> Thanks, >>> Rafael >>> _______________________________________________ >>> tesla-dev mailing list >>> tesla-dev at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/tesla-dev >> >> _______________________________________________ >> tesla-dev mailing list >> tesla-dev at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/tesla-dev > > _______________________________________________ > tesla-dev mailing list > tesla-dev at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/tesla-dev
