01-21-2009
Hardware error
PANIC: k_trap - Kernel mode trap type 0x0000000E
This is the standard panic response when Unix cannot access a critical piece of hardware for a process. In this case for some reason unix cannot access the /usr/data directory. When ever it trys, it fails and crases the system. Why it fails, I cannot even begin to tell you, with the limited information you gave.
Last edited by Eclectic Wave; 01-21-2009 at 10:57 AM..
Reason: Mis read statement
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
HELP is urgently required,
I run on SCO Unix 3 and this is the panic message that I get every time that I reboot 10U
k_trap - kernel mode trap type 0x0000000E
I have checked the swap already having the following results:
#swap -l
path dev swaplo blocks free... (3 Replies)
Discussion started by: alex_slb
3 Replies
2. UNIX for Dummies Questions & Answers
I've installed rh 7.3 a fewday ago and I'm trying to boot it and I get this" Kernel panic: no init found. try passing init=options to kernel" ????? What do I do.
Thanks.
F,Ruiz. (2 Replies)
Discussion started by: ruizf
2 Replies
3. UNIX for Dummies Questions & Answers
hello :-)
I have one problem with my LiLO... I installed PLD Linux on my computer but when it boots, the last thing I can see is:
request_module Root fs not mounted
VFS: Cannot open root device 03:01
Kernel panic: VFS: unable to mount root fs on 03:01
and the system stops :-(
what... (1 Reply)
Discussion started by: pgas
1 Replies
4. SCO
hi,
I am trying to install sco openserver 5.0.4 on an old system. However, l was not able to proceed after putting the bootstr
l have this panic message of
PANIC: K_trap - kernel mode trap tupe 0x00000006
will someone kindly help to decode this error
kayode (1 Reply)
Discussion started by: kayode
1 Replies
5. Linux
I have compiled kernel version 2.6.12 in my linux box mandrake 10.1. I have followed www.digitalhermit.com/linux/Kernel-Build-HOWTO.html instructions. I have copied .config file from /usr/src/linux and lightly modified it (only the processor type) by xconfig. I have compiled the source and modules.... (3 Replies)
Discussion started by: Davide71
3 Replies
6. Solaris
One of our Sun E450 machines crashed and has this message in the /var/adm/messages after it rebooted automatically. An extract of the log is below. I suspect it is memory, but I am not sure. Can anyone give me any ideas how to diagnose this correctly?
Thanks
Margaret Floyd
Apr 10 08:18:54... (1 Reply)
Discussion started by: floydm
1 Replies
7. Linux
ok so I just installed fedora core 6 on my dell inspiron 700m and I go to boot into linux and I get this error. Has anyone seen this before?
I also had XP Pro and Vista installed on this pc prior to putting fedora core 6 on the machine. I'm trying to setup a triple boot system.
Please Help... (2 Replies)
Discussion started by: dave043
2 Replies
8. SCO
hi
I've virtualized physical SCO 5.0.6 on ESX 4 according to:
Blog du DS45: HOWTO SCO P2V in the real life
SCO starts with the network, but during shutdown I'm getting this message:
PANIC: k_trap.
My /etc/default/boot:
# cat /etc/default/boot
#ScoAdminInit BOOTMNT {RO RW NO} RO... (4 Replies)
Discussion started by: ccc
4 Replies
9. SCO
I shutdown my sco 5.0.7 machine about a month and a half ago and upon bringing it back up got the following kernel panic:
Panic: k_trap - Kernel mode trap type0x0000000E
Unable to freeze processor 2, proceeding....
Cannot dump ?????? pages (I don't remember how many pages it was)
Dump not... (0 Replies)
Discussion started by: powwm
0 Replies
10. UNIX for Advanced & Expert Users
Hi, all:
How should I obtain the reason of kernel panic?
How should I debug the program which result in a kernel panic?
What can I get from the panic information?
li, kunlun (3 Replies)
Discussion started by: liklstar
3 Replies
crash(8v) crash(8v)
Name
crash - what happens when the system crashes
Description
This section explains what happens when the system crashes and shows how to analyze crash dumps.
When the system crashes voluntarily it prints a message on the console in the form:
panic: explanation
The system takes a dump on a mass storage peripheral device or the network, and then invokes an automatic reboot procedure as described in
Unless there is some unexpected inconsistency in the state of the file systems due to hardware or software failure, the system then resumes
multi-user operations. If auto-reboot is disabled, the system halts at this point.
The system has a large number of internal consistency checks; if one of these fails, it prints a short message indicating which one failed.
The most common cause of system failures is hardware failure. In all cases there is the possibility that hardware or software error pro-
duced the message in some unexpected way. These messages are the ones you are likely to encounter:
IO err in push
hard IO err in swap
The system encountered an error when trying to write to the paging device or an error in reading critical information from a disk
drive. Fix your disk if it is broken or unreliable.
timeout table overflow
Due to the current data structure, running out of entries causes a crash. If this happens, make the timeout table bigger.
Exception Condition
An unexpected system error has occurred. The exception types are as follows:
---------------------------------------------------------------
Mnemonic Description
---------------------------------------------------------------
INT External interrupt
MOD TLB modification exception
TLBL TLB miss exception (load or instruction fetch)
TLBS TLB miss exception (store)
AdEL Address error exception (load or instruction fetch)
AdES Address error exception (store)
IBE Bus error exception (for an instruction fetch)
DBE Bus error exception (for a data load or store)
Sys Sys call exception
Bp Breakpoint exception
CpU Coprocessor unusable exception
Ovf Arithmetic overflow exception
---------------------------------------------------------------
KSP not valid
This indicates either a problem in the system or failing hardware.
init died
The system initialization process has exited. The only solution is the automatic reboot procedure described in Until this is done,
new users cannot log in.
When the system crashes, it attempts to write an image of memory into the back end of the primary swap area. After the system is rebooted,
the program runs and preserves a copy of this core image and the current system in a specified directory for later access. See for
details.
To analyze a dump, you should begin by running with the flag on the core dump.
See Also
dbx(1), reboot(8), savecore(8)
RISC crash(8v)