11-19-2009
This server was working for the previous 3 years with this kernel? I think either the kernel file's been corrupted, or your computer's memory's gone bad.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
We have a Digital Unix Server with OSF.
There's a Kernel Parameter "dflssiz" on this server.
I just want to know, what it means.
Thanks (2 Replies)
Discussion started by: sameerdes
2 Replies
2. Solaris
Ok, I found this article:
https://www.unix.com/sun-solaris/19665-boot-cannot-open-kernel-sparcv9-unix.html
However it doesn't quite describe my situation.
I have created a jumpstart DVD that works great, and installs my customized Solaris-10 (Yes 10, not 8 or 9 per previous posts) . It... (6 Replies)
Discussion started by: biea
6 Replies
3. UNIX for Advanced & Expert Users
When I debug vmlinux with gdb, after it connect to the target, I got below output:
usbcore.ko: No such file or directory.
Error while mapping shared library sections:
ohci_hcd.ko: No such file or directory.
Symbol file not found for usbcore.ko
Symbol file not found for ohci_hcd.ko
Symbol... (2 Replies)
Discussion started by: yanglei_fage
2 Replies
4. Solaris
Hi All,
I have installed Solaris 10 on my AMD 64 3000+ system. I was playing with grub commands eeprom and bootadm commands. I screwed my boot-file and now am unable to boot the system. Gets error msg as "panic: cannot open /kernel/amd64/unix". I booted the system is filesafe and tried update the... (2 Replies)
Discussion started by: Manjunath K V
2 Replies
5. Programming
I was going through the Linux code, i stuck with few inline assembly language code,
I have tried online but in vain. Any help is much appreciated. Thanks.
/* how to get the thread information struct from C */
static inline struct thread_info *current_thread_info(void)
{
struct... (3 Replies)
Discussion started by: kumaran_5555
3 Replies
6. Red Hat
Hi,
I am seeing the following errors in my environment, not sure why is it happening, any ideas? Thanks.
kernel: RPC: bad TCP reclen 0x73746174 (non-terminal ) Dec 17 02:14:48 kernel: RPC: bad TCP reclen 0x63480000 (large) Dec 17 02:14:48
kernel: RPC: bad TCP reclen 0x633f0000 (large) Dec... (5 Replies)
Discussion started by: amarlinux
5 Replies
7. Solaris
I've never seen this, is it normal for 11.2? Anyway to change it back to dumping metadata or is this simply an overly verbose message I may ignore?
kernel without ZFS metadata (4 Replies)
Discussion started by: LittleLebowski
4 Replies
8. AIX
Anyone running CICS TX in a WPAR ?
In my attempts to run CICS TX 5.1.0.1 in a WPAR..... CICS fails to start due to unable to load a CICS IPC Kernel Extension. The Kernel Extension is 64 bit (so not a 32 vs 64 bit issue).
Base system/LPAR is Power8 and AIX 7.1 TL3 SP5. WPAR is versioned... (4 Replies)
Discussion started by: The Doctor
4 Replies
LEARN ABOUT OPENSOLARIS
allkmem
mem(7D) Devices mem(7D)
NAME
mem, kmem, allkmem - physical or virtual memory access
SYNOPSIS
/dev/mem
/dev/kmem
/dev/allkmem
DESCRIPTION
The file /dev/mem is a special file that provides access to the physical memory of the computer.
The file /dev/kmem is a special file that provides access to the virtual address space of the operating system kernel, excluding memory
that is associated with an I/O device.
The file /dev/allkmem is a special file that provides access to the virtual address space of the operating system kernel, including memory
that is associated with an I/O device. You can use any of these devices to examine and modify the system.
Byte addresses in /dev/mem are interpreted as physical memory addresses. Byte addresses in /dev/kmem and /dev/allkmem are interpreted as
kernel virtual memory addresses. A reference to a non-existent location returns an error. See ERRORS for more information.
The file /dev/mem accesses physical memory; the size of the file is equal to the amount of physical memory in the computer. This size may
be larger than 4GB on a system running the 32-bit operating environment. In this case, you can access memory beyond 4GB using a series of
read(2) and write(2) calls, a pread64() or pwrite64() call, or a combination of llseek(2) and read(2) or write(2).
ERRORS
EFAULT Occurs when trying to write(2) a read-only location (allkmem), read(2) a write-only location (allkmem), or read(2) or write(2) a
non-existent or unimplemented location (mem, kmem, allkmem).
EIO Occurs when trying to read(2) or write(2) a memory location that is associated with an I/O device using the /dev/kmem special
file.
ENXIO Results from attempting to mmap(2) a non-existent physical (mem) or virtual (kmem, allkmem) memory address.
FILES
/dev/mem Provides access to the computer's physical memory.
/dev/kmem Provides access to the virtual address space of the operating system kernel, excluding memory that is associated with an
I/O device.
/dev/allkmem Provides access to the virtual address space of the operating system kernel, including memory that is associated with an
I/O device.
SEE ALSO
llseek(2), mmap(2), read(2), write(2)
WARNINGS
Using these devices to modify (that is, write to) the address space of a live running operating system or to modify the state of a
hardware device is extremely dangerous and may result in a system panic if kernel data structures are damaged or if device state is
changed.
SunOS 5.11 18 Feb 2002 mem(7D)