On SunOS 5.8 I get an error when starting a large Java process with over 2Gb memory.
Error occurred during initialization of VM
Could not reserve enough space for object heap
When stopping several other Java processes we can start this process. This seems to indicate that we don't have... (11 Replies)
I'm not an HP-UX Admin professional, but rather a Lawson ERP installer. I'm looking for clues on how to troubleshoot this issue. I have WAS 6.1 ND running on HP-UX 11.23 PA-RISC with the Lawson ERP application . When I start the Lawson application, no errors arise. When I start WAS app server, an... (4 Replies)
Hi,
Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:-
1. Total Physical Memory in the system(total RAM).
2. Available Physical Memory(i.e. RAM Usage)
3. Total (Logical) Memory in the system
4. Available (Logical) Memory.
I know... (4 Replies)
Hi all,
I just add in new cpu/memory module into SFV480 and unable to see new module on slot B. I already try many way like only 1 new module and swap the both module and boot up but still unable to see it.
If I only install the module into slot B, then the server is unbootable at all.
I... (1 Reply)
On SunOS 10 get an error when starting a large Java process with over 2Gb memory.
Error occurred during initialization of VM
Could not reserve enough space for object heap
i have 32G memory !! , swap = 31G
Please any advice !!! (3 Replies)
Hi
I am unable to view the output of sar file using below command
sar -f sar07, it is showing below error.
Invalid system activity file: sar07 (0x920)
above file is in location /var/log/sa
wheather for memory it is creating the file at different location? (1 Reply)
Hello All,
So it goes like this...
I logged in to the HMC console , trying to change the memory of LPAR from 20 to 25 GB . It says that "your profile is configured to use maximum of only 20 GB" and not able to increase the memory.
I created a new profile and filled "maximum memory " field... (4 Replies)
Hi there.
I'm putting together a small cluster of Raspberry pis running Raspbian. They've all been setup identically from the same sd image.
They all update and install perfectly except one node which refuses to install anything. It has exactly the same login, network, user details etc,... (3 Replies)
Discussion started by: MuntyScrunt
3 Replies
LEARN ABOUT SUNOS
kstat
kstat(9S) Data Structures for Drivers kstat(9S)NAME
kstat - kernel statistics structure
SYNOPSIS
#include <sys/types.h>
#include <sys/kstat.h>
#include <sys/ddi.h>
#include <sys/sunddi.h>
INTERFACE LEVEL
Solaris DDI specific (Solaris DDI)
DESCRIPTION
Each kernel statistic (kstat) exported by device drivers consists of a header section and a data section. The kstat structure is the header
portion of the statistic.
A driver receives a pointer to a kstat structure from a successful call to kstat_create(9F). Drivers should never allocate a kstat struc-
ture in any other manner.
After allocation, the driver should perform any further initialization needed before calling kstat_install(9F) to actually export the
kstat.
STRUCTURE MEMBERS
void *ks_data; /* kstat type-specific data */
ulong_t ks_ndata; /* # of type-specific data records */
ulong_t ks_data_size; /* total size of kstat data section */
int (*ks_update)(struct kstat *, int);
void *ks_private; /* arbitrary provider-private data */
void *ks_lock; /* protects this kstat's data */
The members of the kstat structure available to examine or set by a driver are as follows:
ks_data Points to the data portion of the kstat. Either allocated by kstat_create(9F) for the drivers use, or by the driver if it
is using virtual kstats.
ks_ndata The number of data records in this kstat. Set by the ks_update(9E) routine.
ks_data_size The amount of data pointed to by ks_data. Set by the ks_update(9E) routine.
ks_update Pointer to a routine that dynamically updates kstat. This is useful for drivers where the underlying device keeps cheap
hardware statistics, but where extraction is expensive. Instead of constantly keeping the kstat data section up to date,
the driver can supply a ks_update(9E) function that updates the kstat data section on demand. To take advantage of this
feature, set the ks_update field before calling kstat_install(9F).
ks_private Is a private field for the driver's use. Often used in ks_update(9E).
ks_lock Is a pointer to a mutex that protects this kstat. kstat data sections are optionally protected by the per-kstat ks_lock. If
ks_lock is non-NULL, kstat clients (such as /dev/kstat) will acquire this lock for all of their operations on that kstat.
It is up to the kstat provider to decide whether guaranteeing consistent data to kstat clients is sufficiently important to
justify the locking cost. Note, however, that most statistic updates already occur under one of the provider's mutexes. If
the provider sets ks_lock to point to that mutex, then kstat data locking is free. ks_lock is really of type (kmutex_t*)
and is declared as (void*) in the kstat header. That way, users do not have to be exposed to all of the kernel's lock-
related data structures.
SEE ALSO kstat_create(9F)
Writing Device Drivers
SunOS 5.10 4 Apr 1994 kstat(9S)