Sponsored Content
Full Discussion: Kernal Panic
Top Forums UNIX for Dummies Questions & Answers Kernal Panic Post 36975 by RTM on Monday 9th of June 2003 10:37:02 AM
Old 06-09-2003
Here is a link on Kernel Panics -

Your system attempted to do a dump of memory into a core file - the space you have allocated for this was not big enough to save it all. You should read the information in the link and then figure out where you might be able to create enough space (different for what OS you are running).

Please post the OS and version and any other information you might have. Once you have the space to save the dumps, you will have to wait until it happens again to get better information on what to do. I don't know if folks on this site can help with reading your core dump but I'm sure they will have more suggestions for you.

Getting your system up to the latest patch level might help.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

kernal log message

Hi all, we have been noticed that few of processes failed with no reason. when I chcked the log messages, I have got the following error messages writen to ktlog just a few minutes before! When the kernel writes such warning meassages? will the system sends/generates any signals like... (1 Reply)
Discussion started by: reddyb
1 Replies

2. Filesystems, Disks and Memory

kernal parameters on Linux 7.3

Hi all, I am running 7.3 Redhat Linux, I have Oracle database running on it and I have some problem with the memory. every time I startup the database, the memory was peak up to 630M of Ram out 640M ram on the entire box and I didn't specify that much of memory on my database. Oracle advise me... (2 Replies)
Discussion started by: lapnguyen
2 Replies

3. UNIX for Dummies Questions & Answers

How does the Kernal schedules Tasks?

hello all, as we know that the kernal Schedules tasks with some time slice given to each. how does the Kernal know that the time of a Task has been elapsed? does it follow the syatem Clock?or how? thanks for your time (4 Replies)
Discussion started by: compbug
4 Replies

4. UNIX for Dummies Questions & Answers

Kernal Information

Hi friends, i would like to know the kernal information (semaphores), which command do i use Thanks (4 Replies)
Discussion started by: shaan_dmp
4 Replies

5. Linux

Kernal panic error& setuproot:error mounting /proc&/sys

Hi all, I am new to redhat/fedora linux. In fedora linux 6,we created one file system(hda3 - /fs). in this mount poing we were installed mounta vista os. while booting we are getting below error messages. 1) Booting 'mountaVisat(2.6.18_pro 500_pc_target-x86_586 smp)' root(hd0,1)... (2 Replies)
Discussion started by: arjunreddy3
2 Replies

6. UNIX for Dummies Questions & Answers

Panic kernal-mode address fault on user address 0x14

:) Firstly Hi all!!, im NEW!! and on here hoping that someone might be able to offer me some help... i have a server that keeps crashing every few days with the error message: PANIC KERNAL-MODE ADDRESS FAULT ON USER ADDRESS 0X14 KERNAL PAGE FAULT FROM (CS:EIP)=(100:EF71B5BD) EAX=EF822000... (10 Replies)
Discussion started by: Twix
10 Replies

7. Solaris

kernal parameter setting

hi, can anybody tell me how to increase the parameters like project.max-shm-ids on solaris10. i have used prctl, but got reset while server reboot. thnks and regards Ajay (1 Reply)
Discussion started by: ajaysahoo
1 Replies

8. SCO

Kernal Panic questions

I am trying to restore Unixware 7.1 from a backup using RestoreEdge which is from Microline version 2. The restore is on another machine using the same RAID controller and TBU. We are retiring the other machine. Anyway, we get to disk #2 and it panics. Here is the Pic. Can anyone tell me... (13 Replies)
Discussion started by: ccd1977
13 Replies

9. Solaris

Kernal Parameters

Hi, Can you please let me know about kernal parameters? Where we can see that kernal parameters? we are using System = SunOS 5.10. Please let me know commands to see these kernal parameters file or files. (1 Reply)
Discussion started by: kancherla.sree
1 Replies

10. Red Hat

Error: kernal panic not syncing

HI All, server stopped here, we are suspecting server crash, need install new OS. Any suggestions on this. kindly help to us. Thanks Rajesh (0 Replies)
Discussion started by: Rajesh_Apple
0 Replies
SWAPCTL(8)						    BSD System Manager's Manual 						SWAPCTL(8)

NAME
swapctl, swapon -- system swap management tool SYNOPSIS
swapctl -A [-f | -o] [-n] [-p priority] [-t blk|noblk|auto] swapctl -D dumpdev|none swapctl -U [-n] [-t blk|noblk|auto] swapctl -a [-p priority] path swapctl -c -p priority path swapctl -d path swapctl -l | -s [-k | -m | -g | -h] swapctl -q swapctl -z swapon -a [-t blk|noblk] swapon path DESCRIPTION
The swapctl program adds, removes, lists, and prioritizes swap devices and files for the system. The swapon program acts the same as the swapctl program as if called with the -a option, except if swapon itself is called with -a in which case swapon acts as swapctl with the -A option. The following options are available: -A This option causes swapctl to read the /etc/fstab file for devices and files with a ``sw'' or ``dp'' type, and adds all ``sw'' type entries as swap devices and sets the last ``dp'' type entry as the dump device. If no swap devices are configured, swapctl will exit with an error code. If used together with -t auto this option will not read /etc/fstab but query the kernel for all swap partitions on local hard disks. -a The -a option requires that a path also be in the argument list. The path is added to the kernel's list of swap devices using the swapctl(2) system call. When using the swapon form of this command, the -a option is treated the same as the -A option, for back- wards compatibility. -c The -c option changes the priority of the listed swap device or file. -D The -D option requires that a dumpdev also be in the argument list. The kernel dump device is set to dumpdev. The word ``none'' can be used instead of a dumpdev to disable the currently set dump device. This change is made via the swapctl(2) system call. The dump device is used when the system crashes to write a current snapshot of real memory, to be saved later with savecore(8) at system reboot, and analyzed to determine the problem. -d The -d option removes the listed path from the kernel's list of swap devices or files. -f Used in combination with the -A command and -t auto flag this option makes swapctl use the first discovered swap device to also become the dump device. The -f option is mutually exclusive with the -o option. -g The -g option uses (1024 * 1024 * 1024) byte blocks instead of the default 512 byte. -h The -h option uses humanize_number(3) to display the sizes. -k The -k option uses 1024 byte blocks instead of the default 512 byte. -l The -l option lists the current swap devices and files, and their usage statistics. -m The -m option uses (1024 * 1024) byte blocks instead of the default 512 byte. -n Used with the -A or -U command, the -n option makes swapctl print the action it would take, but not actually change any swap or dump devices. -o Similar to the -f flag, this ``Dump Only'' option makes swapctl find the first swap device and configure it as dump device. No swap device is changed. This option needs to be used in combination with -A -t auto and is mutually exclusive with -f. -p The -p option sets the priority of swap devices or files to the priority argument. This works with the -a, -c, and -l options. -q Query /etc/fstab, checking for any defined swap or dump devices. If any are found, swapctl returns with an exit status of 0, if none are found the exit status will be 1. -s The -s option displays a single line summary of current swap statistics. -t This flag modifies the function of the -A and -U options. The -t option allows the type of device to add to be specified. An argu- ment of blk causes all block devices in /etc/fstab to be added. An argument of noblk causes all non-block devices in /etc/fstab to be added. An argument of auto causes all swap partitions on local hard disks to be used. This option is useful in early system startup, where swapping may be needed before all file systems are available, such as during disk checks of large file systems. -U This option causes swapctl to read the /etc/fstab file for devices and files with a ``sw'' type, and remove all these entries as swap devices. If no swap devices are unconfigured, swapctl will exit with an error code. If used together with -t auto this option will not read /etc/fstab but unconfigure all local swap partitions. -z The -z option displays the current dump device. SWAP PRIORITY
The NetBSD swap system allows different swap devices and files to be assigned different priorities, to allow the faster resources to be used first. Swap devices at the same priority are used in a round-robin fashion until there is no more space available at this priority, when the next priority level will be used. The default priority is 0, the highest. This value can be any valid integer, with higher values receiving less priority. SWAP OPTIONS
When parsing the /etc/fstab file for swap devices, the following options are recognized: priority=N This option sets the priority of the specified swap device to N. nfsmntpt=/path This option is useful for swapping to NFS files. It specifies the local mount point to mount an NFS filesystem. The mount point must exist as a directory. Typically, once this mount has succeeded, the file to be used for swapping on will be available under this point mount. For example: server:/export/swap/client none swap sw,nfsmntpt=/swap EXIT STATUS
If the requested operation was successful, the swapctl utility exits with status 0. If an error occurred, the exit status is 1. The -A and -U operations (add or remove swap devices listed in fstab(5)) return an exit status of 2 to report that no suitable swap devices were found. The -z operation (query dump device) and -l (list swap partitions) return an exit status of 1 if no dump device or swap partition has been configured. If any swap partition is available or a dump device is set, the respective query returns 0. SEE ALSO
swapctl(2), fstab(5), mount_nfs(8) HISTORY
The swapctl program was first made available in NetBSD 1.3. The original swapon program, provided for backwards compatibility, appeared in 4.0BSD. AUTHORS
The swapctl program was written by Matthew R. Green <mrg@eterna.com.au>. CAVEATS
Using the automatic swap partition detection done by the -A -t auto option may be dangereous. Depending on the on-disk partitioning scheme used, the type of a partition may not be accurately recognizable as a swap partition. The autodetection might recognize and use partitions on removable media like USB sticks. An easy way to test the autoconfiguration is to use swapctl with the -n option. BUGS
If no swap information is specified in /etc/fstab, the system startup scripts (see rc(8)) will configure no swap space and your machine will behave very badly if (more likely when) it runs out of real memory. Local and remote swap files cannot be configured until after the file systems they reside on are mounted read/write. The system startup scripts need to fsck(8) all local file systems before this can happen. This process requires substantial amounts of memory on some systems. If you configure no local block swap devices on a machine that has local file systems to check and rely only on swap files, the machine will have no swap space at all during system fsck(8) and may run out of real memory, causing fsck to abnormally exit and startup scripts to fail. BSD
June 1, 2011 BSD
All times are GMT -4. The time now is 07:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy