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)
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)
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)
Hi all,
I am trying to setup a program to use a device driver and am confusing buffer access between User and Kernel mode. I think all applications running in User space have to communicate with the device drivers using io control calls and then have some functions called back from the driver... (1 Reply)
Hi all i have queastion. Can anybody pease help me
what is user mode and kernel mode and the term "De-mountable volumes" means?
Thanks
Palash (2 Replies)
Hi, i'm another question:
I'm a directory /usr/data on my server sco unix 5.0.5:
# du /usr/data
4386948 /usr/data
I'm tried to connect to ftp directory /usr/data to this server and:
PANIC: k_trap - Kernel mode trap type 0x0000000E
Cannot dump 262040 pages to dumpdev hd(1/41):space... (3 Replies)
Hi,all:
I run my program which consists of one kernel module and one user mode process on a dual core server. The problem here is the kernel module consumes 100% of one core while the user mode process only consumes 10% of the other core, is there any solution that I can assign some computing... (1 Reply)
When accessing a user mode buffers from kernel space drivers what precautions must we take and how those precautions need to be implemented? (0 Replies)
Discussion started by: rupeshkp728
0 Replies
LEARN ABOUT DEBIAN
explain_write_or_die
explain_write_or_die(3) Library Functions Manual explain_write_or_die(3)NAME
explain_write_or_die - write to a file descriptor and report errors
SYNOPSIS
#include <libexplain/write.h>
void explain_write_or_die(int fildes, const void *data, long data_size);
DESCRIPTION
The explain_write_or_die function is used to call the write(2) system call. On failure an explanation will be printed to stderr, obtained
from explain_write(3), and then the process terminates by calling exit(EXIT_FAILURE).
This function is intended to be used in a fashion similar to the following example:
ssize_t result = explain_write_or_die(fildes, data, data_size);
fildes The fildes, exactly as to be passed to the write(2) system call.
data The data, exactly as to be passed to the write(2) system call.
data_size
The data_size, exactly as to be passed to the write(2) system call.
Returns:
This function only returns on success. On failure, prints an explanation and exits.
SEE ALSO write(2)
write to a file descriptor
explain_write(3)
explain write(2) errors
exit(2) terminate the calling process
COPYRIGHT
libexplain version 0.52
Copyright (C) 2008 Peter Miller
explain_write_or_die(3)