On Thu, 1 Oct 2009, Tom Chen wrote:

> Randy,
> 
> Thank you very much! 
> 

> On a Ultra45 Sparc desktop workstation with nevada 121, the "uadmin 
> 3 7" command seems working but crashed. See the attached message 
> log. I do not know which device driver cause the panic.
> 
> What confused me also is that command "uadmin 3 22" can really 
> suspend the Ultra45 Sparc work station and resume to its previous 
> state(see the messages in the test log at Sep 30 18:02:08).

  Ahhh yes, I see why.  This is technically a bug (though, it is 
actually a feature in the "new" code).

> While "uadmin 3 7" would cause a crash and reboot the system(see the 
> test log at Oct 1 12:58:15). Are you sure "uadmin 3 7" is the right 
> command for Sparc?

  Yes, this is the proper test point for Sparc.  It would be useful to 
know if 'uadmin 3 8' has the same results, but the difference is 
compressing the image (I would have expected an uncompressed statefile 
would have had less issues).  If you enable kmdb (either by adding the 
'-k' option at boot, or by running 'mdb -K' followed by a ":c" at the 
next prompt), it should stop at the problem point, and it would useful 
to get the most recent crash information (as I doubt a corefile will 
happen - but if it does, I would prefer this instead).

> 
> I do not know why suspend is not supported on T5240 Sparc server 
> which works somewhat on Ultra45 station? see my question on another 
> thread: 
> http://www.opensolaris.org/jive/thread.jspa?messageID=421409#421409

  Not a supported machine.  But I did send you something that will 
enable it, should you wish to try,


  I am still awaiting a U45 (interestingly enough, it is scarce around 
here) to test on my own, but once I do, I would have more information 
to help here.

  Cheers!

        ---- Randy
> 
> 
> Tom
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> networking-discuss mailing list
> [email protected]
> 
_______________________________________________
networking-discuss mailing list
[email protected]

Reply via email to