Friday Feb 06, 2009

new release of Solaris CAT available

We just released the latest version of the Solaris Crash Analysis Tool.  For more information, see the Solaris CAT Blog. Many folks have asked why we are developing and supporting Solaris CAT when Solaris provides mdb. There's several reasons: mdb kind of assumes the user has some knowledge of the Solaris kernel, mdb is more of a debugger than an analysis tool, Solaris CAT provides aggregation features (thread scanners, device aggregaters, streams checkers, etc) that mdb does not provide, and, frankly, Solaris CAT makes analyzing Solaris crashes easier. I look at it like the editor wars for the 80's and 90's - I prefer vi but have no problem with folks using Emacs. Use what you like but don't complain about those who use something different.  

Tuesday Jan 13, 2009

new build of SL 1.20

Well I have yet to get a successful build from SL 1.21 or 1.22.  I just haven't had the time to dive into the new build environment.   Luckily, Linden Lab released a bunch of updates for SL 1.20.17.  Therefore, you can download updated packages using the links Solaris 10 and OpenSolaris/Nevada.

I'll try to work on the newer versions of the viewer as soon as I get the next release of Solaris CAT out the door.

Wednesday Oct 15, 2008

Second Life Viewer Security Builds (1.20.17) Now Available

Since Linden Lab released security patches for their viewer, Clark has made builds available to everyone.  Those URLs are: 1.20.17 for Solaris 10 & 1.20.17 for Nevada/OpenSolaris.  Since this is a security-related build, all prior versions have been removed.

I've also seen updates on all the Solaris related PJira issues saying they are now pending!  Sweet! That means that we'll soon have the Solaris patches integrated into the viewer trunk.

Lastly, I have yet to start on the port of 1.21.  I just haven't had the time to dive into the cmake changes.  If anyone has a set of Viewer related cmake patches for Solaris, please share.



Friday Jul 18, 2008

Solaris version of the SL viewer 1.20.14.0

I've had a few requests for SL 1.20.14.0 since it includes the "skinning project" and of course, Clark was anxious for the patches so here's the packages (thanks Clark!):  Solaris 10 and Nevada/OpenSolaris.  I've been working hard to free up enough time to update the jira issues with my latest patches and promise I'll get them up there ASAP.

Wednesday Jul 16, 2008

Solaris Crash Analysis Tool 5.0 released

Well it's been five long years since an update of Solaris Crash Analysis Tool (CAT) was released to the public and I'm happy to report that the Solaris CAT Development Team (John, Paul, and I) were finally given the time to work through the red tape and get a new release out. Yes!  Solaris CAT 5.0 is available for immediate download from here.  This new version not only supports the newer releases of Solaris, namely Solaris 10 and OpenSolaris/Nevada, it also suports both SPARC and x86/x64 architectures and includes commands that support zones, the Solaris Volume Manager, ZFS, Sun Cluster, plus many more features.  I'd recommend reading the Release Notes (/opt/SUNWscat/docs/index.html) for both this release and Release 4.2 to get yourself up to date on everything that has been changed, fixed, and added in 5.0.  Enjoy and please let the Solaris CAT Team know how you like the tool by commenting on our blog or sending email to SolarisCAT_Feedback@Sun.COM.  I'm also happy to report that we'll be trying to  release  versions once every six months.

What is Solaris CAT?  It's a Solaris kernel crash dump (and live kernel) access tool that provides simple intuitive commands which can be used to quickly analyze crash dumps.  It's developed by Sun kernel engineers  (those who support customers) who analyze kernel core files for a living.  It's different from mdb because its geared more towards analysis instead of debugging.  It's also different from mdb because it's development is done as a hobby by a handful of people and is officially an "unsupported" tool (though if one finds a bug and let's us know, we likely fix it quickly.)  And so you are confident,  SolarisCAT is used thousands of times a month here at Sun.  Therefore, it gets plenty of testing :)

As an example of Solaris CAT's power, the following is from a system that was hanging and where the user interrputed the kernel with a "break".  As you can see below, the dev busy command not only isolated the devices that were "hanging", it also discovered that an interface card, /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3, is likely the culprit.  Without that analysis, the engineer working on that crash dump may waste time trying to chase "failing" devices before the interface card or  lpfc  was identified as the culprit.

SolarisCAT(vmcore.1/8U)> dev busy

Scanning for busy devices:
sd321 @ 0x3000537db30(scsi_disk), DEVICE BUSY, un_ncmds: 20
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,27
sd322 @ 0x3000537d370(scsi_disk), DEVICE BUSY, un_ncmds: 20
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,28
sd323 @ 0x3000537cbb0(scsi_disk), DEVICE BUSY, un_ncmds: 1
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,29
sd324 @ 0x3000537c3f0(scsi_disk), DEVICE BUSY, un_ncmds: 1
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,2a
sd327 @ 0x3000542cbb8(scsi_disk), DEVICE BUSY, un_ncmds: 20
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,26
sd343 @ 0x3000546abd8(scsi_disk), DEVICE BUSY, un_ncmds: 1
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,1b
sd347 @ 0x30005456be0(scsi_disk), DEVICE BUSY, un_ncmds: 3
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,1f
sd348 @ 0x30005456040(scsi_disk), DEVICE BUSY, un_ncmds: 2
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,20
sd349 @ 0x300054493a8(scsi_disk), DEVICE BUSY, un_ncmds: 4
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,21
sd351 @ 0x30005436050(scsi_disk), DEVICE BUSY, un_ncmds: 9
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,23
sd353 @ 0x300054a8fd8(scsi_disk), DEVICE BUSY, un_ncmds: 5
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,3f
sd358 @ 0x30005476450(scsi_disk), DEVICE BUSY, un_ncmds: 3
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@0,40
sd432 @ 0x300054a8818(scsi_disk), DEVICE BUSY, un_ncmds: 9
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@a,5
sd433 @ 0x300054a8058(scsi_disk), DEVICE BUSY, un_ncmds: 1
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@a,6
sd436 @ 0x30005496c00(scsi_disk), DEVICE BUSY, un_ncmds: 1
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@a,9
sd476 @ 0x30005534850(scsi_disk), DEVICE BUSY, un_ncmds: 6
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3/sd@1,5a

By aggregating "busy" device paths, the following devices 
should also be investigated:
    /SUNW,Sun-Fire/ssm@0,0/pci@1c,700000/lpfc@3

Scanning for threads in biowait:

   103 threads in biowait() found.

threads in biowait() by device:
count   device (thread: max idle time)
   36   32,2570(sd321,2) (0x3001c0a5ba0: 1 hours 35 minutes 13.49 seconds) /dev/dsk/c1t0d39s2(swap)
   25   32,2578(sd322,2) (0x2a1002cbd20: 1 hours 35 minutes 13.95 seconds) /dev/dsk/c1t0d40s2(swap)
   19   32,2618(sd327,2) (0x300979fa460: 1 hours 35 minutes 13.49 seconds) /dev/dsk/c1t0d38s2(swap)
    4   237(vxio),47006 (0x300171d9ca0: 1 hours 35 minutes 13.04 seconds) /play/oradata003
    4   237(vxio),47008 (0x30085682e60: 1 hours 35 minutes 13.26 seconds) /play/oradata005
    2   32,3812(sd476,4) (0x30015f12600: 1 hours 35 minutes 13.48 seconds) /opt/tools
    2   237(vxio),99003 (0x30014a40180: 1 hours 35 minutes 13.47 seconds) /test/archive
    2   237(vxio),10000 (0x3001c0a45a0: 1 hours 35 minutes 13.31 seconds) /appl/oradata001
    2   237(vxio),47004 (0x30099665b80: 1 hours 35 minutes 11.33 seconds) /play/oradata001
    1   237(vxio),10004 (0x3001de53900: 1 hours 35 minutes 13.31 seconds) /appl/oradata005
    1   237(vxio),51000 (0x3005c6d83c0: 1 hours 35 minutes 13.49 seconds) /bcv/prod/transfer
    1   32,3808(sd476,0) (0x3001a310c00: 49 minutes 16.60 seconds) /crash
    1   237(vxio),99001 (0x3009c625bc0: 9 minutes 4.67 seconds) /test/peace
    1   237(vxio),99002 (0x30015f36e20: 1 hours 26 minutes 42.69 seconds) /test/oracle
    1   237(vxio),8003 (0x30005fa1620: 1 hours 34 minutes 52.51 seconds) /test/redo4
    1   237(vxio),10002 (0x3001405ce40: 1 hours 35 minutes 13.31 seconds) /appl/oradata003

Scanning for procs with aio:
proc             PID       fd                  dev   state       count
====           ======      ==                  ===   =====       =====
0x3001710d520   25667     408      237(vxio),99008   pending         1
SolarisCAT(vmcore.1/8U)>

Wednesday Jun 18, 2008

Solaris version of the SL viewer 1.20.10.0

I thought is was about time to let folks know about the latest Solaris build of the Second Life viewer, version 1.20.10.0.  Clark Dastardly has made them available at Package for Solaris 10  and Package for OpenSolaris. Streaming audio support returns in this release but only in Solaris Nevada/OpenSolaris because Solaris 10's GStreamer still needs to be updated.  Please let me know if you hit any bugs/problems/issues and please give me some feed back. I would love to know how the Solaris version behaves compared to Linden Lab's official builds - yes, we still need streaming video (waiting on Sun's official AAC decoder) and Voice (waiting on Linden Lab to release  a Vivox client for Solaris) so there's no need to tell me about these.

I'll try and get the patches posted to their related Second Life Jira tickets within the next few days.

Tuesday May 06, 2008

Running OpenSolaris 2008.05 under VirtualBox on OS X Leopard

I finally had time to work with VirtualBox (VBox) on my Macbook Pro the other day and since I ran into a couple snags I thought I'd post a short blog entry that provides some of the details. But first here are two other blogs that helped:

I've tested VBox with the newly released OpenSolaris 2008.05 as well as Solaris 10 Update 5 and both run well.

Here are some notes that may help:

  • If you read Alan's and Rodney's blog entries first, note that there is no need to install a newer network driver with VirtualBox 1.6. All you need to do is set the network device to "Intel PRO/1000 MT Desktop (NAT)". Also don't be caught by the mistake I made and try using ping to test the network connection. The VBox documentation clearly states that ICMP through the VBox virtual network stack is unreliable.
  • If you want a higher res screen, the default in VBox is 1024x768, before starting the VirtualBox guest run:

    VBoxManage setextradata "Solaris 10" "CustomVideoMode1" "1280x10240x24"

    Where "Solaris 10" is the name of VBox vm and I'd recommend bumping the video memory to at least 64MB. I had to do this for each vm I created.

    Note that the xorg.conf that Alan provides on his blog currently causes X to crash on the latest Nevada and OpenSolaris. I'm currently trying to figure out why.

  • Set the network device emulation to "Intel PRO/1000 MT Desktop (NAT)"
  • If you are installing Solaris for the first time, be sure to link or mount the Solaris iso image as the CDROM
  • Start the VM and run through the standard Solaris install.
  • On Solaris 10:
    • start a terminal session (not CDE or Gnome)
    • disable CDE with "/usr/dt/bin/dtconfig -d"
    • enable gnome desktop login (this gives you Xorg X11 server) with "svcadm enable gdm2-login"
    • if you want a higher resolution desktop, use the VBoxManage command above and install the attached xorg.conf into /etc/X11/xorg.conf (remember this bombs terribly on Nevada/OpenSolaris) and log out and back in to restart X

      So far I've tested X and networking with OpenSolaris 2008.05 and Solaris 10 U5.

      As proof and from the sick puppy category, here is a screen shot off my Macbook Pro 17 with OpenSolaris running in one VBox instance and Solaris 10 U5 installing in another (click the picture for a full sized version):

Wednesday Feb 27, 2008

Second Life on Solaris x86. You want it & you can have it!

It's been months since I gave everyone an update on the Second Life viewer on Solaris. So here it is...

First, you need to know that the viewer is now available outside Sun. The pre-built packages are now available off of amazonaws.com, see Jeff Barr's blog entry for the details. I want to thank these folks for putting the effort in and making the viewer available to everyone.

If you want to build the viewer yourself, please refer to my past posts on building the libraries and tweaking SConstruct. As for the patches themselves, I've submitted them under Second Life "jira" issues and, as such, I ask that you download the patches from there. The issue numbers are:

  • VWR-4800 - Use Solaris kstats when running on Solaris
  • VWR-4802 - add definitions for stricmp and strnicmp
  • VWR-4804 - Add necessary includes to llsys.h
  • VWR-4805 - add LL_SOLARIS to #if in lltimer.h
  • VWR-4806- llvfs changes
  • VWR-4807 - add Solaris to #if in llglstubs.h
  • VWR-4808 - featuretable_solaris.txt patch
  • VWR-4809 - llfloaterreporter.cpp
  • VWR-4810 - add Solaris required changes to llappviewer_linux.cpp
  • VWR-4811 - add LL_SOLARIS to #if in llfilepicker.cpp
  • VWR-4812 - include llstring.h in llfloateranimpreview.cpp
  • VWR-4813 - include llstring.h to llfloaterimagepreview.cpp
  • VWR-4814 - include llstring.h in llfloaternamedesc.cpp
  • VWR-4815 - add Solaris specific platform to llfloaterreporter.cpp
  • VWR-4816- include Solaris in llstartup.cpp
  • VWR-4817 - don't include gMovieMaker on Solaris builds
  • VWR-4818- add LL_SOLARIS to #if in llfilepicker.cpp
  • VWR-4819 - add LL_SOLARIS to linux #if in moviemaker.h
  • VWR-4820 - add solaris_tools to newview
If you want the latest audio updates, I suggest you refer to VWR-2662 for the latest patches. Be sure to read the comments included in VWR-2662 so that you get everything you need. The patches are added in the order documented in the jira issue, the result is a viewer with OpenAL supported audio as well as GStreamer supported audio streaming. However, streamed audio only works on OpenSolaris because the GStreamer support in SL requires GStreamer 0.10 (delivered in OpenSolaris) and Solaris 10 currently supports GStreamer 0.8.

Seriously, save yourself a bunch of time, and just take the pre-built packages mentioned above. Attempting a SL build can induce sleeplessness, outbursts of frustration, and possible tears.

My plans for the future work on the Second Life viewer depends priorities here at Sun. I have plenty of other work on my to-do list so we'll see. But if I do get the thumbs up, I plan on doing the following:

  • Reduce the number of libraries included in the SL package in favor of those bundled with OpenSolaris under the Project Indiana initiative.
  • Add patches to the cmake branch of the Second Life build tree. yes, that's right, SCons is no longer going to be used to build SL. I'm not sure I like cmake but it does provide a good cross-platform (Windows, OS X, Linux, and Solaris) build environment.
  • See what, if anything, can be done to get the Linux version of the Vivox client working under Solaris. I'm thinking that perhaps Project Indiana may help here.
Cheers!
About

Don't ya just love toys and taking them apart to see how they work? To me it doesn't matter if it's an iPod, a laptop, or the biggest baddest thing a company makes. And nothing makes me more happy than showing how easy it is to develop stuff on Oracle Solaris.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today