"K"

kernel read error

Cause

This message appears when savecore(1M), if activated, tries to copy a debugging image of kernel memory to disk, but cannot read various kernel data structures correctly. Generally, this occurs after a system panic has corrupted the main memory. Data corruption on the system is possible.

Action

Look at the kernel error messages that preceded this one to try to determine the cause of the problem. Error messages such as BAD TRAP usually indicate faulty hardware. Until the problem that caused the kernel panic is resolved, a kernel core image cannot be saved for debugging.

killed

Cause

A process, which attempts to allocate large amounts of memory either as an array or by using malloc, fails when launched by the shell. This problem has been seen while allocating 240,000,000 elements as either an array of doubles or using malloc to allocate the 1,920,000,000 bytes of space.

Action

This can have one of two causes. Resolve it accordingly.

1. Lack of swap space

Try running the program as root on the console; if it runs, this is not the problem.

2. Stack size and data segment size are in conflict

If the stack size is set too large, this can conflict with the data segment, and the process cannot be started. Setting the stack size to the default value of 8192 resolves this problem and allows the programs to start.

Killed

Cause

This message is strictly informational. If the killed process was writing a file, some data might be lost.

Action

Continue with your work.

Technical Notes

This message from the signal handler or various shells indicates that a process has been terminated with a SIGKILL. However, if you do not see this message and cannot terminate a process with a SIGKILL, you might have to reboot the machine to remove that process.

kmem_free block already free

Cause

This is a programming error, probably from a device driver.

Action

Determine which driver is giving this message and contact the vendor for a software update, as this message indicates a bug in the driver.

Technical Notes

This message is from the DDI programming function kmem_free(9F), which releases a block of memory at address addr of size siz that was previously allocated by the DDI function kmem_alloc(9F). Both addr and siz must correspond to the original allocation. If you have source code for the driver, follow kmem_alloc(9F) and kmem_free(9F) in the code to make sure they allocate and free the same chunk of memory.