Randy Fishel wrote: >>>>> >>>>> >>>> There is a private method by which the firmware decides whether the host >>>> OS is >>>> alive and healthy. If so, then the host does this work. If not, then the >>>> firmware takes over. >>>> >>>> >>>> >>> I have been looking for a place to ask this quesiton, and this might be >>> it: What occurs if the machine is suspended and the NIC is still hot (maybe >>> WOL enabled). Will the ME also be running? >>> >> Yes! >> >> >>> If so, the OS is not, will it still know that OS is alive and healthy, or >>> decide it is bad and try and reboot? >>> >> Neither. The firmware is running and one can remotely reboot it using a >> management tool, but on its own, the ME takes no action. >> > > I havn't fully read the materials, and I guess what the ME > actually does is beyond the scope of this discussion. However, I > suspect that there is a mechanism in the "private method" described > above that at least lets the ME know the host is going into an S3 > state, and that the Solaris components *will* use this API, so if the > host is in this state, the ME can properly report the condition. >
Yes. > >>> Will it be able to generate a PME and resume? (and maybe a host of other >>> questions surrounding suspended machines). >>> >>> >> No. This is not a general watchdog facility. >> > > PME is not a watchdog facility, but the hardware wake mechanism. > And though again I guess what the ME actually does is beyond our > control, I am interested that it has desired capabilities (it can wake > a sleeping system), or else it needs to be documented to discourage > this combination. > It can wake the system. This is precisely one of the cases it was designed to support. It can either do an S3 resume, or a full system reset. -- Garrett > > ---- Randy > > >> -- Garrett >> >>
