<p> I've loaded up my brand new HP Pavilion dv5 (dv5t-1100, to be precise) with 2008.11. And suspend/resume isn't working as expected. Thought I'd be able to at least make an effort, but everything I've tried has hit a dead end so far. <br/> <p> After reading the 2008.11 suspend/resume FAQ, ensuring that suspend/resume was activated, and failing to suspend, I turned to <a href=http://blogs.sun.com/randyf/entry/testing_suspend_and_resume_for>this</a> blog entry to try and debug it. <br/> <p> The problem I'm having is that any attempt to test Suspend-to-RAM for <i>any</i> driver module using this command:
<p> <pre> uadmin 3 25 <b><i>driver-module-id</i></b> </pre> <p> Ends up garbling the screen and hanging the system. Even loading kmdb with the -k option to the kernel doesn't seem to help me to break into the system by pressing F1-A or Ctrl-Pause, once the hang has occurred. And laptops don't have serial console access nowadays... <p> So what approaches can I take to: <ul> <li>Determine which devices in the tree to <i>start</i> Suspend-to-RAM testing on? So I can work my way up the device tree to find the real culprit. <li>Have some kind of debugging capability when I end up suspending the "suspect" devices? </ul> <p> Would providing the output of prtconf -vD help in this case? <p> Thanks for any advice. -- This message posted from opensolaris.org
