After I added some code to reinitialize the GTT(Graphics Translation Table) table in agptarget driver resume interface,  Solaris could resume properly from the suspend state.   Finally,  there are four components affecting Intel graphics S3 process, ie, i915 driver, vgatext driver, agptarget driver and DDX driver.  
Tips in suspend debugging. 


1)Now days, most of the laptops do not get serial ports in them.  We can only wake up kmdb in console which depends on framebuffer driver.  How can we debug the suspend process with KMDB after the framebuffer suspend?  Let me explain a bit,  each device like framebuffer in Solaris will be set to poweoff by post suspend call which can not be controlled by device driver.  So the graphics device will power off after it say "suspend success" to upper layer, then console and kmdb prompt will go away for the poweroff.   We should hack the power off code in post supsend if we need further kmdb support.


2) I should have more, let me think a while.

Comments:

Thanks for the progress report. Do we have any info regarding what laptops in which the suspend mode in Solaris (especially OpenSolaris 2008.05) works?

Posted by W. Wayne Liauh on June 05, 2008 at 02:09 AM CST #

I can tell the end user will have S3 support on Toshiba M8, M8 by next OpenSolaris release.

Posted by edward.shu on June 05, 2008 at 10:39 PM CST #

I have Toshiba M9 laptop, running Opensolaris with b94 image, S3 does not work, can you tell more what I can try?

Posted by Pasha on August 01, 2008 at 09:52 PM CST #

Post a Comment:
  • HTML Syntax: NOT allowed

This blog copyright 2009 by Ming Shu