See I/OAT description here.
Solaris (at least snv_93 and and snv_95) panics if large amount of traffic is sent across the interface dedicated to a zone with exclusive TCP/IP stack. For example, start Firefox and forward the X traffic to the global zone.
Continue reading “IOAT fatal failures”
http://www.intel.com/technology/ioacceleration/
Intel® I/O Acceleration Technology (Intel® I/OAT) accelerates TCP/IP processing and reduces CPU overhead. It scales up to eight GbE and 10 10GbE ports and supported on dual- or quad-core Xeon architecture.
If after entering username/password you see a small window (with a going back and forth blue “slider”) saying:
“Completing post install setup”
most likely svc:/system/postrun/default service is not running.
Check the status:
and enable it if it’s disabled (for example, after a system upgrade)
Related system packages:
After upgrading from snv_88 to snv_92 (Solaris 11 or Nevada b92) my home server started spewing the following errors:
After upgrading to snv_93 SqueezeCenter (quite predictably) refused to start again. The error was:
The issue is related to the same Scalar::Util module. Just force install it like explained here.
The current version can be found here: http://dlc.sun.com/osol/jds/downloads/current/
Tried to install Vermillion 94 yesterday (GNOME 2.23.4) but had to fail back to nevada_92 (GNOME 2.22.2), because 94 was almost unusable (e.g. right button did not work, window manager did not want to start automatically, etc). Both installers failed to install JDS correclty (missed or incorrectly configured packages and files).
For example, libgnome-desktop-2.so.2 was missing in v94.
If you can’t login, if your GNOME session crashes, if you fonts are garbled or you see no fonts at all, check the following files:
Continue reading “Troubleshooting GNOME”
If you see no images in HTML-mail in evolution, add the following line to /etc/services:
BugID: 4511649
How to enable, disable displaying by page and change the number of lines by page in various OS’es
After hitting this bug (yes, again and again) I had to unmount the broken file system and run fsck (twice). But then I apparently hit anoter bug (or a feature?) – I could not mount the file system back.
Neither pwdx not lsof showed any processes using /export/docs. The solution was to recreate the directory: