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 FREEBSD
crashinfo
CRASHINFO(8) BSD System Manager's Manual CRASHINFO(8)
NAME
crashinfo -- analyze a core dump of the operating system
SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core]
DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as
the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX.
By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the
core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel
that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel
file can also be explicitly provided via the kernel argument.
Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8),
ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8).
The options are as follows:
-d crashdir
Specify an alternate core dump directory. The default crash dump directory is /var/crash.
-n dumpnr
Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory.
-k kernel
Specify an explicit kernel file.
SEE ALSO
textdump(4), savecore(8)
HISTORY
The crashinfo utility appeared in FreeBSD 6.4.
BSD
June 28, 2008 BSD