Sponsored Content
Full Discussion: Kernal Panic
Top Forums UNIX for Dummies Questions & Answers Kernal Panic Post 36974 by jcoleman544 on Monday 9th of June 2003 10:23:48 AM
Old 06-09-2003
Network Kernal Panic

Received the following on the weekend.
Panic:k_trap kernel mode trap type 0X0000000e cannot dump 163739 pages to dumpdev hd (1/41):space for only 48640 pages

Dump not complete

Safe to power off or press any key to reboot

Any ideas how to fix this one? It also happen a month ago.
 

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
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - stopping and restarting the system SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ] /sbin/halt [ -lqndars ] /sbin/fastboot [ -lqndarsRD ] DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is necessary to read it in from disk or tape each time it is to be boot strapped. Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first. Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation. Options to reboot are: -l Don't try to tell syslogd(8) what's about to happen. -q Reboot quickly and ungracefully, without shutting down running processes first. -n Don't sync before rebooting. This can be used if a disk or the processor is on fire. -h Don't reboot, simply halt the processor. -d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic. -a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix). -r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD. -s Don't enter multi-user mode after system has rebooted - stay in single user mode. -f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt) flag. -D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program. -R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the root/swap/pipe/dump device. Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this case. Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively. Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user operations. SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8) 3rd Berkeley Distribution May 24, 1996 REBOOT(8)
All times are GMT -4. The time now is 11:21 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy