Solaris 10 kernel params w/10.1.2.2.0 ?
We migrated from 5.4 under Solaris 9, to a new box, Solaris 10 and 10.1.2.2.0. - We run calendar Standalone.
Problem is we are hitting a limit at 127 concurrent users. eng.log shows a problem with no message queue resources available. But the kernel setting for this, is now obsolete.
I do have a case open with Oracle, but it's taking forever... I'm trying adjusting project.max-sem-ids project.max-shm-memory and project.max-shm-ids. process.max-sem-nsems doesn't exist..
TIA...
Moderator Action:
This inquiry was initially posted to the Predictive Self Healing forum for some unfathomable reason.
It has now been moved to the Oracle VM and Virtualization forum for closer topic alignment.
Advice to original poster:
If you couldn't read enough posts to figure out which forum was appropriate, how are you going to be able to read replies to your question? You should go back to wherever you found Virtualbox and Solaris and read the product documenteation. Installation instructions are already there.
Similar Messages
-
I've been assigned to put oracle on a Dell installed RED Hat 6.0
box.
The Kernel Params are driving me nutty.
First of all, the docs are saying that SHMMAX needs to be
4294967295. I can't understand why Oracle can't just tell you
what to enter into the header straight and simple in HEX. My
hex calculator can't manipulate this magnitude. Is this
documentation even correct? It seems 2 digits too large from
everything else I'm looking at.
The rest of the kernel code is largley defined dynamically:
It looks like this.
Should I over ride all this?
#define SHMID_BITS 7
#define SHM_ID_MASK ((1<<_SHM_ID_BITS)-1)
#define SHM_IDX_SHIFT (_SHM_ID_BITS)
#define SHMIDX_BITS 15
#define SHM_IDX_MASK ((1<<_SHM_IDX_BITS)-1)
* SHMID_BITS + SHMIDX_BITS must be <= 24 on the i386 and
* SHMMAX <= (PAGE_SIZE << SHMIDX_BITS).
#define SHMMAX 0x2000000 /* max shared seg size
(bytes) */
/* Try not to change the default shipped SHMMAX - people rely on
it */
#define SHMMIN 1 /* really PAGE_SIZE */ /* min shared seg size
(bytes) */
#define SHMMNI (1<<_SHM_ID_BITS) /* max num of segs system
wide */
#define SHMALL /* max shm system wide
(pages) */ \
(1<<(_SHM_IDX_BITS+SHMID_BITS))
#define SHMLBA PAGE_SIZE /* attach addr a multiple
of this */
#define SHMSEG SHMMNI /* max shared segs per
process */
#endif /* ASMI386SHMPARAM_H */
nullIf the system cats back -1 (or -273 etc) for inputs that big, I
don't how we are going to obtain a positive outcome.
The hex is not the point. The point is that 4 gig ints echoed
into the /proc directory return negitive integers.
Ruben
Mladen Gogala (guest) wrote:
: Hexcalculator is for wimps. The real programmers use bc,
: with scale, ibase and obase options. As bc is doing
: packed decimal arithmetics, it can do calculations with
: the numbers > 4GB. Increase SHMMAX to 0x4000000, relink
: the kernel (make bzImage), restart & enjoy.
: Ruben I Safir (guest) wrote:
: : Thanks Robson
: : That translates to -1 when you cat it back. That was the
same
: : thing the kde hexcalculator did. It seems that using that
many
: : bytes triggers a signed variable.
: : Ruben
: : Robson Miranda (guest) wrote:
: : : You only need to do
: : : echo 4294967295 > /proc/sys/kernel/shmmax (I think, I'm not
: on
: : : my Linux box, so can't check now).
: : : With kernel > 2.2.x, there's no need to recompile it to
: change
: : : the maximum amount of shared memory.
: : : Robson.
: : : Ruben I Safir (guest) wrote:
: : : : I've been assigned to put oracle on a Dell installed RED
: Hat
: : : 6.0
: : : : box.
: : : : The Kernel Params are driving me nutty.
: : : : First of all, the docs are saying that SHMMAX needs to be
: : : : 4294967295. I can't understand why Oracle can't just
tell
: : you
: : : : what to enter into the header straight and simple in
HEX.
: My
: : : : hex calculator can't manipulate this magnitude. Is this
: : : : documentation even correct? It seems 2 digits too large
: from
: : : : everything else I'm looking at.
: : : : The rest of the kernel code is largley defined
dynamically:
: : : : It looks like this.
: : : : Should I over ride all this?
: : : : #define SHMID_BITS 7
: : : : #define SHM_ID_MASK ((1<<_SHM_ID_BITS)-1)
: : : : #define SHM_IDX_SHIFT (_SHM_ID_BITS)
: : : : #define SHMIDX_BITS 15
: : : : #define SHM_IDX_MASK ((1<<_SHM_IDX_BITS)-1)
: : : : * SHMID_BITS + SHMIDX_BITS must be <= 24 on the i386
: and
: : : : * SHMMAX <= (PAGE_SIZE << SHMIDX_BITS).
: : : : #define SHMMAX 0x2000000 /* max shared seg
: : size
: : : : (bytes) */
: : : : /* Try not to change the default shipped SHMMAX - people
: rely
: : : on
: : : : it */
: : : : #define SHMMIN 1 /* really PAGE_SIZE */ /* min shared seg
: : size
: : : : (bytes) */
: : : : #define SHMMNI (1<<_SHM_ID_BITS) /* max num of
segs
: : : system
: : : : wide */
: : : : #define SHMALL /* max shm system
: : wide
: : : : (pages) */ \
: : : : (1<<(_SHM_IDX_BITS+SHMID_BITS))
: : : : #define SHMLBA PAGE_SIZE /* attach addr a
: : : multiple
: : : : of this */
: : : : #define SHMSEG SHMMNI /* max shared
segs
: : per
: : : : process */
: : : : #endif /* ASMI386SHMPARAM_H */
null -
How to recompile the Intel Solaris kernel
HI,
I installed Intel solaris on x86 system. As per the manual U should change parameters in /etc/system file to configure semaphores and kernel memory . After updating the /etc/system file ,restart is required to take parameters in effect. But even after reboot the system is not getting configured as per the /etc/system settings.
Is there any other way to recompile the kernel?
Please let me know on [email protected]
Thanks in Advance,
SagarYou never recompile the Solaris kernel. Exactly what are you putting in /etc/system? How are you determining whether or not the changes took effect? What release of Solaris?
-
Why are Solaris kernel Developers/Engineers so hard to find?
Hi all,
I'm a recruiter trying to staff a high level Solaris Kernel Developer job in MA (110K+/year) - It's turned out to be one of the most hopeless persuits of my career. Are you guys a dying breed, since so amny people have switched to linux?
In an case, if anybody is looking for work and interested, knows anybody, or can point me in the right direction I'd appreciate it.
Thanks,
EmmaApple (and no one else) can not assist (with serial number or iCloud) in finding a lost or stolen iPad.
Report to police along with serial number. Change all your passwords.
These links may be helpful.
How to Track and Report Stolen iPad
http://www.ipadastic.com/tutorials/how-to-track-and-report-stolen-ipad
Reporting a lost or stolen Apple product
http://support.apple.com/kb/ht2526
iCloud: Locate your device on a map
http://support.apple.com/kb/PH2698
Report Stolen iPad Tips and iPad Theft Prevention
http://www.stolen-property.com/report-stolen-ipad.php
How to recover a lost or stolen iPad
http://ipadhelp.com/ipad-help/how-to-recover-a-lost-or-stolen-ipad/
iCloud: Locate your device on a map
http://support.apple.com/kb/PH2698
How to Find a Stolen iPad
http://www.ehow.com/how_7586429_stolen-ipad.html
What NOT to do if your iPhone or iPad is lost or stolen
http://www.tomahaiku.com/what-not-to-do-if-your-iphone-or-ipad-lost-or-stolen/
Apple Product Lost or Stolen
http://sites.google.com/site/appleclubfhs/support/advice-and-articles/lost-or-st olen
Oops! iForgot My New iPad On the Plane; Now What?
http://online.wsj.com/article/SB10001424052702303459004577362194012634000.html
If you don't know your lost/stolen iPad's serial number, use the instructions below. The S/N is also on the iPad's box.
How to Find Your iPad Serial Number
http://www.ipadastic.com/tutorials/how-to-find-your-ipad-serial-number
iOS: How to find the serial number, IMEI, MEID, CDN, and ICCID number
http://support.apple.com/kb/HT4061
Cheers, Tom -
Static library not accessed properly after Solaris Kernel patch update !
Hi,
We are facing a sever issue in our application after our customer updated the Solaris 10 kernel patch u9 to u10.
We have two static libraries libdlib.a and libDLIB.a, with exactly same code base, but these two libraries are scattered across the code base and linked by many shared objects in our application.
However, one of the shared objects that links to "libdlib.a" library tries to access a function from "libDLIB.a". This behavior is causing a crash at a later point, since that shared object is supposed to access the function from "libdlib.a". Moreover, we found this is happening through the use of dbx.
I'm unable to understand why this problem surfaced after kernel patch update, though still the shared object works fine on Solaris 10 u9 patch.
Flow is something like this :
1. syslogrecorder.so gets loaded by one of the processes.
2. syslogrecorder.so is linked to "libdlib.a" at compile time, so it uses "libdlib.a" function DLIB_LoadLibrary and gets a handle to all the function pointers of the loaded library ( The purpose of DLIB_LoadLibrary is to load a shared library dynamically using dlopen )
3. syslogrecorder.so tries to do a "dlsym" and to do that it needs access to the library handle which we got in previous call DLIB_LoadLibrary. So syslogrecorder.so calls another function from DLIB_ProcAddress, which actually gives back the access to the loaded shared library.
Here is a catch in step 3, it is supposed to call DLIB_ProcAddress from the libdlib.a but as we observed from dbx output it does so by calling DLIB_ProcAddress from libDLIB.a and hence fails to give back the access to loaded shared library, causing crash at a later point in code.
Can someone put some light here that why this could happen ??
Thanks
KuldeepTo clarify: You did not modify or rebuild any of your binaries, but after installing a kernel patch, the application stopped working. Most likely, something about your application depended on a accidental behavior of the runtime loader. That accidental behavior changed due to the patch, and your application failed.
For example, if there is a circular dependency among shared libraries, the loader will break the cycle at an arbitrary point to establish an initialization order. By accident, that order might work, in the sense of not causing a problem. A change to the loader could cause the cycle to be broken at a different point, and the resulting initialization order could cause a now-uninitialized object to be accessed. I'm not saying this is what is wrong, but this is an example of a dependency on accidental loader behavior.
Finding your actual problem will require tracing the sequence of operations leading up to the failure. You are more likely to find help in a Solaris linker forum. AFAIK, there are currently no Oracle forums for Solaris, and the old OpenSolaris forums have been converted to mailing lists. You can try the "tools-linking" list found on this page:
http://mail.opensolaris.org/mailman/listinfo
I also suggest you review the paper on best practices for using shared libraries written by Darryl Gove and myself:
http://www.oracle.com/technetwork/articles/servers-storage-admin/linkinglibraries-396782.html
If you have a service contract with Oracle, you can use your support channel to get more help.
Edited by: Steve_Clamage on May 18, 2012 3:21 PM -
Solaris Kernel and TCP/IP Tuning Parameters (Continued)
This page describes some configuration optimizations for Solaris hosts running ATG Page Serving instances (application servers) that will increase server efficiency.
Note that these changes are specific to Solaris systems running ATG application servers (+page serving+ instances). Do not use these on a web server or database server. Those systems require entirely different settings.
h3. Solaris 10 Kernel
Adjust /etc/system (parameters below) and reboot the system.
set rlim_fd_cur=4096
set rlim_fd_max=4096
set tcp:tcp_conn_hash_size=32768
set shmsys:shminfo_shmmax=4294967295
set autoup=900
set tune_t_fsflushr=1h4. Set limits on file descriptors
{color:blue}set rlim_fd_max = 4096{color}
{color:blue}set rlim_fd_cur = 4096{color}
Raise the file-descriptor limits to a maximum of 4096. Note that this tuning option was not mentioned in the "Sun Performance And Tuning" book.
[http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-32/index.html]
h4. Increase the connection hash table size
{color:blue}set tcp:tcp_conn_hash_size=8192{color}
Increase the connection hash table size to make look-up's more efficient. The connection hash table size can be set only once, at boot time.
[http://download.oracle.com/docs/cd/E19455-01/816-0607/chapter4-63/index.html]
h4. Increase maximum shared memory segment size
{color:blue}set shmsys:shminfo_shmmax=4294967295{color}
Increase the maximum size of a system V shared memory segment that can be created from roughly 8MB to 4GB.
This provides an adequate ceiling; it does not imply that shared memory segments of this size will be created.
[http://download.oracle.com/docs/cd/E19683-01/816-7137/chapter2-74/index.html]
h4. Increase memory allocated for dirty pages
{color:blue}set autoup=900{color}
Increase the amount of memory examined for dirty pages in each invocation and frequency of file system synchronizing operations.
The value of autoup is also used to control whether a buffer is written out from the free list. Buffers marked with the B_DELWRI flag (which identifies file content pages that have changed) are written out whenever the buffer has been on the list for longer than autoup seconds. Increasing the value of autoup keeps the buffers in memory for a longer time.
[http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-16/index.html]
h4. Specify the time between fsflush invocations
Specifies the number of seconds between fsflush invocations.
{color:blue}set tune_t_fsflushr=1{color}
[http://download.oracle.com/docs/cd/E19082-01/819-2724/chapter2-105/index.html]
Again, note that after adjusting any of the preceding kernel parameters you will need to reboot the Solaris server.
h3. TCP
ndd -set /dev/tcp tcp_time_wait_interval 60000
ndd -set /dev/tcp tcp_conn_req_max_q 16384
ndd -set /dev/tcp tcp_conn_req_max_q0 16384
ndd -set /dev/tcp tcp_ip_abort_interval 60000
ndd -set /dev/tcp tcp_keepalive_interval 7200000
ndd -set /dev/tcp tcp_rexmit_interval_initial 4000
ndd -set /dev/tcp tcp_rexmit_interval_max 10000
ndd -set /dev/tcp tcp_rexmit_interval_min 3000
ndd -set /dev/tcp tcp_smallest_anon_port 32768
ndd -set /dev/tcp tcp_xmit_hiwat 131072
ndd -set /dev/tcp tcp_recv_hiwat 131072
ndd -set /dev/tcp tcp_naglim_def 1h4. Tuning the Time Wait Interval and TCP Connection Hash Table Size
{color:blue}/usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000{color}
The tcp_time_wait_interval is how long a connection stays in the TIME_WAIT state after it has been closed (default value 240000 ms or 4 minutes). With the default setting, this socket will remain for 4 minutes after you have closed the FTP connection. This is normal operating behavior. It is done to ensure that any slow packets on the network will arrive before the socket is completely shutdown. As a result, a future program that uses the same socket number won't get confused upon receipt of packets that were intended for the previous program.
On a busy Web server a large backlog of connections waiting to close could build up and the kernel can become inefficient in locating an available TCP data structure. Therefore it is recommended to change this value to 60000 ms or 1 minute.
h4. Tuning the maximum number of requests per IP address per port
{color:blue}ndd -set /dev/tcp tcp_conn_req_max_q 16384{color}
{color:blue}ndd -set /dev/tcp tcp_conn_req_max_q0 16384{color}
The {color:blue}tcp_conn_req_max_q{color} and {color:blue}tcp_conn_req_max_q0{color} parameters are associated with the maximum number of requests that can be accepted per IP address per port. tcp_conn_req_max_q is the maximum number of incoming connections that can be accepted on a port. tcp_conn_req_max_q0 is the maximum number of “half-open” TCP connections that can exist for a port. The parameters are separated in order to allow the administrator to have a mechanism to block SYN segment denial of service attacks on Solaris.
The default values are be too low for a non-trivial web server, messaging server or directory server installation or any server that expects more than 128 concurrent accepts or 4096 concurrent half-opens. Since the ATG application servers are behind a DMZ firewall, we needn't starve these values to ensure against DOS attack.
h4. Tuning the total retransmission timeout value
{color:blue}ndd -set /dev/tcp tcp_ip_abort_interval 60000{color}
{color:blue}tcp_ip_abort_interval{color} specifies the default total retransmission timeout value for a TCP connection. For a given TCP connection, if TCP has been retransmitting for tcp_ip_abort_interval period of time and it has not received any acknowledgment from the other endpoint during this period, TCP closes this connection.
h4. Tuning the Keep Alive interval value
{color:blue}ndd -set /dev/tcp tcp_keepalive_interval 7200000{color}
{color:blue}tcp_keepalive_interval{color} sets a probe interval that is first sent out after a TCP connection is idle on a system-wide basis.
If SO_KEEPALIVE is enabled for a socket, the first keep-alive probe is sent out after a TCP connection is idle for two hours, the default value of the {color:blue}tcp_keepalive_interval{color} parameter. If the peer does not respond to the probe after eight minutes, the TCP connection is aborted.
The {color:blue}tcp_rexmit_interval_*{color} values set the initial, minimum, and maximum retransmission timeout (RTO) values for a TCP connections, in milliseconds.
h4. Tuning the TCP Window Size
{color:blue}/usr/sbin/ndd -set /dev/tcp tcp_xmit_hiwat 65535{color}
{color:blue}/usr/sbin/ndd -set /dev/tcp tcp_recv_hiwat 65535{color}
Setting these two parameters controls the transmit buffer and receive window. We are tuning the kernel to set each window to 65535 bytes. If you set it to 65536 bytes (64K bytes) or more with Solaris 2.6, you trigger the TCP window scale option (RFC1323).
h4. Tuning TCP Slow Start
{color:blue}/usr/sinb/ndd -set /dev/tcp tcp_slow_start_initial 4{color}
tcp_slow_start_initial is the number of packets initially sent until acknowledgment, the congestion window limit.
h4. Tuning the default bytes to buffer
{color:blue}ndd -set /dev/tcp tcp_naglim_def 1{color}
{color:blue}tcp_naglim_def{color} is the default number of bytes to buffer. Each connection has its own copy of this value, which is set to the minimum of the MSS for the connection and the default value. When the application sets the TCP_NODELAY socket option, it changes the connection's copy of this value to 1. The idea behind this algorithm is to reduce the number of small packets transmitted across the wire by introducing a short (100ms) delay for packets smaller than some minimum.
Changing the value of tcp_naglim_def to 1 will have the same effect (on connections established after the change) as if each application set the TCP_NODELAY option.
{note}
The current value of any of the TCP parameters can be displayed with the command ndd get. So to retrieve the current setting of the {color:blue}tcp_naglim_def parameter{color}, simply execute the command:\\
{color:blue}ndd -get /dev/tcp tcp_naglim_def{color}
{note}
h3. References
Solaris Tunable Parameters Reference Manual
[http://download.oracle.com/docs/cd/E19455-01/816-0607/index.html]
WebLogic Server Performance and Tuning
[http://download.oracle.com/docs/cd/E11035_01/wls100/perform/OSTuning.html]For example,
Socket.setSoTimeout() sets SO_TIMEOUT option and I
want to what TCP parameter this option corresponds in
the underlying TCP connection.This doesn't correspond to anything in the connection, it is an attribute of the API.
The same questions
arises fro other options from SocketOptions class.setTcpNoDelay() controls the Nagle algorithm. set{Send,Receive}BufferSize() controls the local socket buffers.
Most of this is quite adequately described in the javadoc actually. -
Hello Experts,
Kindly provide the steps to do the Kernel upgrade on Solaris/oracle -Abap + Java
My system is (Abap + Java). I downloaded the Abap kernel files from the service market places.
note :(I know the kernel upgrade on windows operating system)
1. If we apply Abap kernel is enough or i have to separtely apply kernel for Java?.
2. I see that /sapmnt/<SID>/exe - Owner is <SID>adm and group sapsys except saposcol file.
Thanks
ThirumalMy new kernel extracted file size is 557 MB. (New kernel donot have BRtools files).
Thats ok.. you can copy brtools from your current kernel to the new one or download them from SAP Marketplace.
I guess Now I have to overwrite the kernel.
Never overwrite the kernel... always move the kernel to a new directory so you can keep it as a backup. basically just rename the directory... you can do the in solaris by using comand "mv"
2. Shall i give the command like
"cp -r -p <kernel_patch_extract> <sapmnt>/<SAPSID>/exe"
NO... create a new directory in <sapmnt>/<SAPSID>/ for example "exe_new" the copy all extracted files to <sapmnt>/<SAPSID>/exe_new and the copy brtools from exe to exe_new. Once your happy with it... stop the system then rename the exe directory to for example exe_old, finally rename exe_new to exe and start the system
Easy... huh?
Regards
Juan -
Where can I find some solaris kernel structure intro
Now I'm working at implementing a client filesystem module in Solaris, I want to know where could I find somthing helpful. Such as how to create a socket, connect to server, send/recv msg under kernel... Pls help me if you could && want. Thanks for all.
Best regards.
/yfYou should read this document http://docs.sun.com/db/doc/806-1017.
-
I have engineers asking for a particular kernel patch level to be installed on machines.
Is there anywhere that lists the kernel patch level on releases and hardware updates for Solaris 8-10?
Thanks,
DuanePlease start with Sunsolve (http://sunsolve.sun.com) and Sun documentation (http://docs.sun.com) web sites.
-
Performance Problem For Sun Solaris Kernel
Hello,
I have DB version 10.2.0.2 On Sun Solaris 5.10, when a run top utility i see that 20-25 % of CPU takes Kernel.
Then i Truss DB writer and in out file i see error likes this: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
On metalink i read that it's bu using direct I/O on Solaris UFS file system. Then I change init parameter filesystemio_options from setall to asynch. now value of this parameter is asynch, but when i truss DB writer i saw same error: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
has anyone same problem?file system is UFS. mount option is forcefirectio.
This is example:
14051/169: pwrite(341, "06A2\0\01505D1 <8797 DBA".., 8192, 0xBA278000) = 8192
14051/1: lwp_unpark(171) = 0
14051/171: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(172) = 0
14051/172: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(173) = 0
14051/170: pwrite(367, "06A2\0\01BAA .BA8797 C #".., 8192, 0x545D74000) = 8192
14051/173: lwp_park(0x00000000, 0) = 0
14051/172: pwrite(369, "06A2\0\01C 88DE68797 DBA".., 8192, 0x711BCC000) = 8192
14051/173: pwrite(370, " $A2\0\01C p07 z8797 D13".., 8192, 25785483264) = 8192
14051/1: lwp_unpark(174) = 0
14051/174: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(175) = 0
14051/175: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(176) = 0
14051/176: lwp_park(0x00000000, 0) = 0
14051/171: pwrite(367, "06A2\0\01BABB6 p8797 C #".., 8192, 0x576CE0000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/174: pwrite(370, "06A2\0\01C } # W8797 =B6".., 106496, 0x7A46AE000) = 106496
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/175: pwrite(374, "06A2\0\01D E - 28797 C #".., 8192, 0xA5A64000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/176: pwrite(375, "06A2\0\01D8B 7 Z8796 J96".., 8192, 0x166EB4000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/156: lwp_park(0x00000000, 0) (sleeping...)
14051/153: lwp_park(0x00000000, 0) (sleeping...)
14051/152: lwp_park(0x00000000, 0) (sleeping...)
14051/157: lwp_park(0x00000000, 0) (sleeping...)
14051/154: lwp_park(0x00000000, 0) (sleeping...)
14051/155: lwp_park(0x00000000, 0) (sleeping...)
14051/161: lwp_park(0x00000000, 0) (sleeping...)
14051/160: lwp_park(0x00000000, 0) (sleeping...)
14051/158: lwp_park(0x00000000, 0) (sleeping...)
14051/163: lwp_park(0x00000000, 0) (sleeping...)
14051/162: lwp_park(0x00000000, 0) (sleeping...)
14051/159: lwp_park(0x00000000, 0) (sleeping...)
14051/164: lwp_park(0x00000000, 0) (sleeping...)
14051/165: lwp_park(0x00000000, 0) (sleeping...)
14051/166: lwp_park(0x00000000, 0) (sleeping...)
14051/167: lwp_park(0x00000000, 0) (sleeping...)
14051/168: lwp_park(0x00000000, 0) (sleeping...)
14051/169: lwp_park(0x00000000, 0) (sleeping...)
14051/173: lwp_park(0x00000000, 0) (sleeping...)
14051/170: lwp_park(0x00000000, 0) (sleeping...)
14051/172: lwp_park(0x00000000, 0) (sleeping...)
14051/174: lwp_park(0x00000000, 0) (sleeping...)
14051/175: lwp_park(0x00000000, 0) (sleeping...)
14051/171: lwp_park(0x00000000, 0) (sleeping...)
14051/1: semtimedop(16777258, 0xFFFFFFFF7FFFDEB4, 1, 0xFFFFFFFF7FFFDEA0) (sleeping...)
14051/176: lwp_park(0x00000000, 0) (sleeping...)
14051/1: semtimedop(16777258, 0xFFFFFFFF7FFFDEB4, 1, 0xFFFFFFFF7FFFDEA0) = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: lwp_unpark(177) = 0
14051/177: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(178) = 0
14051/178: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(179) = 0
14051/179: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(180) = 0
14051/180: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(181) = 0
14051/181: lwp_park(0x00000000, 0) = 0
14051/182: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(182) = 0
14051/1: lwp_unpark(183) = 0
14051/183: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(184) = 0
14051/184: lwp_park(0x00000000, 0) = 0
14051/177: pwrite(258, "06A2\0\0\0 @0602879719EA".., 8192, 12599296) = 8192
14051/1: lwp_unpark(185) = 0
14051/185: lwp_park(0x00000000, 0) = 0
14051/181: pwrite(259, " &A2\0\0\080\09987977F P".., 8192, 1253376) = 8192
14051/186: lwp_park(0x00000000, 0) = 0
14051/182: pwrite(259, " &A2\0\0\0800189879783\t".., 8192, 3219456) = 8192
14051/184: pwrite(259, " &A2\0\0\08002C987978114".., 8192, 5840896) = 8192
14051/180: pwrite(259, " &A2\0\0\080\0 )879782F9".., 8192, 335872) = 8192
14051/1: lwp_unpark(186) = 0
14051/185: pwrite(259, " &A2\0\0\08004A98797 x ~".., 8192, 9773056) = 8192
14051/1: lwp_unpark(187) = 0
14051/187: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(188) = 0
14051/1: yield() = 0
14051/188: lwp_park(0x00000000, 0) = 0
14051/186: pwrite(259, " &A2\0\0\08005 98796 pA4".., 8192, 10952704) = 8192
14051/1: lwp_unpark(189) = 0
14051/187: pwrite(259, " &A2\0\0\08005998797 {FF".., 8192, 11739136) = 8192
14051/1: lwp_unpark(190) = 0
14051/188: pwrite(259, " &A2\0\0\08006 987977F95".., 8192, 13049856) = 8192
14051/1: lwp_unpark(191) = 0
14051/169: pwrite(341, "06A2\0\01505D1 <8797 DBA".., 8192, 0xBA278000) = 8192
14051/1: lwp_unpark(171) = 0
14051/171: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(172) = 0
14051/172: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(173) = 0
14051/170: pwrite(367, "06A2\0\01BAA .BA8797 C #".., 8192, 0x545D74000) = 8192
14051/173: lwp_park(0x00000000, 0) = 0
14051/172: pwrite(369, "06A2\0\01C 88DE68797 DBA".., 8192, 0x711BCC000) = 8192
14051/173: pwrite(370, " $A2\0\01C p07 z8797 D13".., 8192, 25785483264) = 8192
14051/1: lwp_unpark(174) = 0
14051/174: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(175) = 0
14051/175: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(176) = 0
14051/176: lwp_park(0x00000000, 0) = 0
14051/171: pwrite(367, "06A2\0\01BABB6 p8797 C #".., 8192, 0x576CE0000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/174: pwrite(370, "06A2\0\01C } # W8797 =B6".., 106496, 0x7A46AE000) = 106496
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/175: pwrite(374, "06A2\0\01D E - 28797 C #".., 8192, 0xA5A64000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/176: pwrite(375, "06A2\0\01D8B 7 Z8796 J96".., 8192, 0x166EB4000) = 8192
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/1: kaio(AIOWAIT, 0xFFFFFFFFFFFFFFFF) Err#22 EINVAL
14051/156: lwp_park(0x00000000, 0) (sleeping...)
14051/153: lwp_park(0x00000000, 0) (sleeping...)
14051/152: lwp_park(0x00000000, 0) (sleeping...)
14051/157: lwp_park(0x00000000, 0) (sleeping...)
14051/154: lwp_park(0x00000000, 0) (sleeping...)
14051/155: lwp_park(0x00000000, 0) (sleeping...)
14051/161: lwp_park(0x00000000, 0) (sleeping...)
14051/160: lwp_park(0x00000000, 0) (sleeping...)
14051/158: lwp_park(0x00000000, 0) (sleeping...)
14051/163: lwp_park(0x00000000, 0) (sleeping...)
14051/162: lwp_park(0x00000000, 0) (sleeping...)
14051/159: lwp_park(0x00000000, 0) (sleeping...)
14051/164: lwp_park(0x00000000, 0) (sleeping...)
14051/165: lwp_park(0x00000000, 0) (sleeping...)
14051/166: lwp_park(0x00000000, 0) (sleeping...)
14051/167: lwp_park(0x00000000, 0) (sleeping...)
14051/168: lwp_park(0x00000000, 0) (sleeping...)
14051/169: lwp_park(0x00000000, 0) (sleeping...)
14051/173: lwp_park(0x00000000, 0) (sleeping...)
14051/170: lwp_park(0x00000000, 0) (sleeping...)
14051/172: lwp_park(0x00000000, 0) (sleeping...)
14051/174: lwp_park(0x00000000, 0) (sleeping...)
14051/175: lwp_park(0x00000000, 0) (sleeping...)
14051/171: lwp_park(0x00000000, 0) (sleeping...)
14051/1: semtimedop(16777258, 0xFFFFFFFF7FFFDEB4, 1, 0xFFFFFFFF7FFFDEA0) (sleeping...)
14051/176: lwp_park(0x00000000, 0) (sleeping...)
14051/1: semtimedop(16777258, 0xFFFFFFFF7FFFDEB4, 1, 0xFFFFFFFF7FFFDEA0) = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: yield() = 0
14051/1: lwp_unpark(177) = 0
14051/177: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(178) = 0
14051/178: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(179) = 0
14051/179: lwp_park(0x00000000, 0) = 0
14051/1: yield() = 0
14051/1: lwp_unpark(180) = 0
14051/180: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(181) = 0
14051/181: lwp_park(0x00000000, 0) = 0
14051/182: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(182) = 0
14051/1: lwp_unpark(183) = 0
14051/183: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(184) = 0
14051/184: lwp_park(0x00000000, 0) = 0
14051/177: pwrite(258, "06A2\0\0\0 @0602879719EA".., 8192, 12599296) = 8192
14051/1: lwp_unpark(185) = 0
14051/185: lwp_park(0x00000000, 0) = 0
14051/181: pwrite(259, " &A2\0\0\080\09987977F P".., 8192, 1253376) = 8192
14051/186: lwp_park(0x00000000, 0) = 0
14051/182: pwrite(259, " &A2\0\0\0800189879783\t".., 8192, 3219456) = 8192
14051/184: pwrite(259, " &A2\0\0\08002C987978114".., 8192, 5840896) = 8192
14051/180: pwrite(259, " &A2\0\0\080\0 )879782F9".., 8192, 335872) = 8192
14051/1: lwp_unpark(186) = 0
14051/185: pwrite(259, " &A2\0\0\08004A98797 x ~".., 8192, 9773056) = 8192
14051/1: lwp_unpark(187) = 0
14051/187: lwp_park(0x00000000, 0) = 0
14051/1: lwp_unpark(188) = 0
14051/1: yield() = 0
14051/188: lwp_park(0x00000000, 0) = 0
14051/186: pwrite(259, " &A2\0\0\08005 98796 pA4".., 8192, 10952704) = 8192
14051/1: lwp_unpark(189) = 0
14051/187: pwrite(259, " &A2\0\0\08005998797 {FF".., 8192, 11739136) = 8192
14051/1: lwp_unpark(190) = 0
14051/188: pwrite(259, " &A2\0\0\08006 987977F95".., 8192, 13049856) = 8192
14051/1: lwp_unpark(191) = 0 -
Dynamic linking of libraries to solaris kernel
Hi all,
Is it possible to link a library dynamically to device driver
If possible what are the functions to do so. Any help will be greatly
appreciated.
Regards
Kiran Kumar KasturiHi,
You cannot dynamically link a library to a driver. In fact most library functions are not actually available to a driver as they are userland and result in system calls. Hence the ddi/dki calls.
Also, as I'm sure you are aware, drivers and modules in Solaris are themselves dynamically loadable. If you want to save the non-pageable kernel memory, you can unload a driver that is not open and in use. The system will do this automatically if it comes under heavy memory pressure.
Hope that helps,
Ralph
SUN DTS -
HP-UX Kernel Params for WLS 6.0SP2 Cluster to Avoid java.lang.outofmemory and/or thread death
I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing heap and
thread issues on start-up or invocation of my application as I deploy EJB's and create
DB connection pools. These are fairly trivial tasks that don't give me any issues
when starting the first node. It's only when I invoke the second node.
I'm pretty sure that my issue is tied to the following kernel areas:
1. Thread allocation
2. Heap allocation
3. Max Processes per user
Can anyone make some kernel recommendations that might be beneficial to my deployment?
My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I typically
allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and allocate about
1GB of RAM per node on a 4GB machine...
Regards,
Steve
I'm running a WLS 6.0 SP2 clustered application on HP-UX 11i. I'm seeing heap and
> thread issues on start-up or invocation of my application as I deploy
EJB's and create
> DB connection pools. These are fairly trivial tasks that don't give me any
issues
> when starting the first node. It's only when I invoke the second node.
>
> I'm pretty sure that my issue is tied to the following kernel areas:
>
> 1. Thread allocation
> 2. Heap allocation
> 3. Max Processes per user
>
> Can anyone make some kernel recommendations that might be beneficial to my
deployment?
> My app runs on NT/2000 and Sun as well, and I haven't seen these issues. I
typically
> allocate 50 to 100 threads per node (3 nodes on a 4 CPU machine) and
allocate about
> 1GB of RAM per node on a 4GB machine...
HP has some kernel tuning guidelines for Java server apps on their web site,
and BEA has some notes as well in their platform support page.
What issues specifically are you seeing?
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"Steve Feldman" <[email protected]> wrote in message
news:3cdc046e$[email protected]..
>
-
Need information regarding Solaris kernel Delayed write operation
Hello Friends,
I need information regarding the delayed write operation in Solaris.
Would be thankful if anyone can give me some details.
Thanks in advance1) When you post code, please use[code] and [/code] tags as described in Formatting tips on the message entry page. It makes it much easier to read.
2) Don't just post a huge pile of code and ask, "How do I make this work?" Ask a specific question, and post just enough code to demonstrate the problem you're having.
3) Don't just write a huge pile of code and then test it. Write a tiny piece, test it. Then write the piece that will work with or use the first piece. Test that by itself--without the first piece. Then put the two together and test that. Only move on to the next step after the current step produces the correct results. Continue this process until you have a complete, working program. -
[Solved] Kernel params for suspend - overheating(?)
I had long since given up on getting my Lenovo S10-3 to suspend - or should I say resume from suspend.
But with all the kernel updates I figured it might be time to give it another shot. The traditional methods had the traditional failings, but I found a new suggestion on the Lenovo S10 page of the arch wiki to add these three kernel parameters
hpet=disable highres=off nohz=off
I had tried the first previously, but not all three. I gave it a shot with all three and suspend and resume work perfectly.
I quickly noticed a disturbing side effect though. My netbook got notably hotter; I didn't take any sensor data, but I could feel how hot it was getting. The cpu fan remained on high continuously at idle, where without those three kernel parameters the fan almost never has to run.
I removed and replaced the parameters a few times to verify that this was the cause. Every time they were on the kernel line I had the fan/heat problems; everytime they weren't these problems didn't exist, but I couldn't resume from suspend.
Has anyone had similar issues or know of any way to get the suspend/resume benefit of these parameters without the (seemingly dangerous) side effect?
Google has not helped much on learning about these parameters. I found dozens of pages that limit their explanation to saying that "nohz=off" turns off nohz. Well thats f^%#ing helpful *sarcasm*.
Last edited by Trilby (2012-05-24 23:04:54)Gusar wrote:They're on a wiki. Which everyone can edit. I'm sure this is not the only bad advice there.
Undoubtedly true. But I've seen them on many wiki's and forums for various distros. I have no delusion that it is good advice, but it is a technique that many are using. I'd be surprised if anyone used it if they got results like I did. Right from powering up I had a "WTF is wrong with my computer" reaction.
But that does answer my question. I'll still try the vanilla kernel tomorrow just in case, as I do still have it installed, but for now I'll put suspend back on the back-burner until I have time to look for better solutions. Working on a quick boot time has made suspending a low priority, but as it's the one thing on this machine that isn't working right I'm like a moth to a flame: "must fix irrelevant problem".
Thanks again for the insight.
UPDATE: Using the vanilla kernel makes no difference: the parameters needed for suspend cause a nasty side effect.
Last edited by Trilby (2012-05-25 15:44:42) -
Copliling Solaris kernel module code in 64bit for AMD64
Hi,
I have solaris10 OS in my HP ProLiant DL-145 server machine
I m using SunStudio C compiler (cc) for compling my kernel module source code. My code is successfully work in 32bit kernel mode. But when i boot the OS in 64bit mode & complile the same code , then no error during compliaion & linking. but my module doesn't work. When i add two flags
-xarch=amd64 -xmodel=kernel , then also no error during compilation, but module still not work.
I want to know , how i can complie my soruce code successfully in 64bit kernel for AMD64, so that it can be loaded successfully through modload command.
I think i need some other flags for that, pls help.from
http://docs.sun.com/app/docs/doc/817-5789/6ml7kh1b4?q=amd64&a=view
Compiling with Sun Studio
Use the -D_KERNEL option to indicate that this code defines a kernel module.
If you are compiling for a 64-bit x86 architecture, use both the -xarch=amd64 option and the -xmodel=kernel option:
% cc -D_KERNEL -xarch=amd64 -xmodel=kernel -c mydriver.c
% ld -r -o mydriver mydriver.o
tim
Maybe you are looking for
-
Iphoto 11/Part of Ilife does not display all photos in "photos" or "events"
I am running latest version of everything, just loaded ILife. Iphoto 11 does not show "ALL" photos when I use "photo" or "event" view. It shows some....when I cycle down through the Blank images in these views, it will often show the pictures as I mo
-
I have two FCP Studio licenses. I understand that the crossgrade is a universal edition, and that 5.1 has features not found in the previous version. I have sent disks in and upgraded one license since I just upgraded on computer to the new Intel iMa
-
Error Message to be displayed in Two Languages
Hi, I am writing my code in an User Exit. My requirement is that when ever an error message is displayed it should be displayed in Two languages i.e in English and Portuguese. Can I do this... if yes then how. Thanks and Regards Suraj
-
Revision: 4195 Author: [email protected] Date: 2008-11-26 13:08:23 -0800 (Wed, 26 Nov 2008) Log Message: Bug: LCDS-517 - Reliable messaging destinations created using runtime configuration (bootstrap service) not working. QA: Yes Doc: No Checkintests
-
hi all is there a way to fully customize the basic search portlet? how can i change the name of the "search" button - i want it to be in my native language, and the portal doens have a translation for it can anyone help?