08-03-2007
Can you copy the 30 lines or so of text before the error message. It sounds like the kernel panicked, but we will not be able to determine what is causing it without seeing what the system was trying to do before the panic.
10 More Discussions You Might Find Interesting
1. Linux
These are not my desktop (I am still using FC1), they are from Internet forum.
http://gator.dt.uh.edu/~yangm001/snapshot1.jpg
http://gator.dt.uh.edu/~yangm001/snapshot2.jpg (0 Replies)
Discussion started by: HOUSCOUS
0 Replies
2. Linux
I have done some research on the Fedora Project and trying to find clear cut answer on how to migrate from current OS - RH 8.0 Pro to Fedora Core 2. Can anybody help me with this and does Fedora Core 2 include OpenOffice and Ximian Evolution like with my RH 8.0 Pro. (3 Replies)
Discussion started by: Mark McWilliams
3 Replies
3. Linux
I've been using FC2, but my sound card doesn't work
I'm new with linux systems..
but there says that needs to recompile kernel
how can i do it with a kernel 2.6.5 i386 ?
by the way,. my sound card chipset is an ESS 1869F, with a compaq deskpro Smal Form Factor. but i have not found a... (4 Replies)
Discussion started by: Quake
4 Replies
4. Linux
in fedora core 2 with enforcing mode in selinux , why even as a root OS doesnt give permission to create any directory or file in /home ? (1 Reply)
Discussion started by: the.last.soul
1 Replies
5. UNIX for Dummies Questions & Answers
Hello,
I am about to install Fedora on a partition on my hard drive. I got the CD from a magazine and it isnt a LiveCD so the magazine says "fedora core installer isn't a LiveCD, so it will merrily destroy your primary partition when you install on your machine", now I'm guessing the primary... (1 Reply)
Discussion started by: ArkNia
1 Replies
6. Linux
Hi all,
I'm experiencing a problem with Fedora Core 4, by which I don't know how to export a directory exclusively in NFSv3.
I have two raid arrays "/dev/md0" and "/dev/md1" both to be visible to SGI machines via NFSv3...
My situation is that Fedora runs NFSv4 and that causes problems with the... (0 Replies)
Discussion started by: spaceace13666
0 Replies
7. UNIX for Dummies Questions & Answers
Hello I'm trying to install fedora core 5 and I'm currently at this screen here:
http://fedora.redhat.com/docs/fedora-install-guide-en/fc5/figs/installingpackages.png
However, the bottom bar is completely gray and there's nothing telling me the "status" of the install. I also told it to format... (2 Replies)
Discussion started by: obeseogre
2 Replies
8. UNIX for Dummies Questions & Answers
how do i change the mailrelay settings smtp for fedora core 4 to a new IP ? (1 Reply)
Discussion started by: dannyd
1 Replies
9. Linux
Hi ,
I am facing a strange with BIND in Fedora Core 6. Here is the config for more info.
#cat /etc/named.caching-nameserver.conf
options {
listen-on port 53 { any; };
directory "/var/named";
// dump-file "/var/named/data/cache_dump.db";
... (3 Replies)
Discussion started by: narasimhulu
3 Replies
10. SuSE
Hi. Not sure if this should go in the beginners section, so forgivness please if it's not correctly placed.
I just installed Linux Fedora Core 6 on my home computer (and am very very new to this) so I can learn more about it. However, I am looking for the FC6 equivalent to the System Device... (2 Replies)
Discussion started by: Carl1976
2 Replies
LEARN ABOUT DEBIAN
textdump
TEXTDUMP(4) BSD Kernel Interfaces Manual TEXTDUMP(4)
NAME
textdump -- textdump kernel dumping facility
SYNOPSIS
options KDB
options DDB
DESCRIPTION
The textdump facility allows the capture of kernel debugging information to disk in a human-readable rather than the machine-readable form
normally used with kernel memory dumps and minidumps. This representation, while less complete in that it does not capture full kernel
state, can provide debugging information in a more compact, portable, and persistent form than a traditional dump. By combining textdump
with other ddb(4) facilities, such as scripting and output capture, detailed bug information can be captured in a fully automated manner.
FORMAT
textdump data is stored in a dump partition in the same style as a regular memory dump, and will be automatically extracted by savecore(8) if
present on boot.
textdump files are stored in the tar(5) format, and consist of one or more text files, each storing a particular type of debugging output.
The following parts may be present:
ddb.txt Captured ddb(4) output, if the capture facility has been used. May be disabled by clearing the debug.ddb.textdump.do_ddb
sysctl.
config.txt Kernel configuration, if has been compiled into the kernel. May be disabled by clearing the debug.ddb.textdump.do_config
sysctl.
msgbuf.txt Kernel message buffer, including recent console output if the capture facility has been used. May be disabled by clearing the
debug.ddb.textdump.do_msgbuf sysctl.
panic.txt Kernel panic string, if the kernel panicked before the dump was generated. May be disabled by clearing the
debug.ddb.textdump.do_panic sysctl.
version.txt Kernel version string. My be disabled by clearing the debug.ddb.textdump.do_version sysctl.
Kernel textdumps may be extracted using tar(1).
CONFIGURATION
The textdump facility is enabled as part of the kernel debugger using options KDB and options DDB. By default, kernel dumps generated on
panic or via explicit requests for a dump will be regular memory dumps; however, by using the textdump set command in ddb(4), or by setting
the debug.ddb.textdump.pending sysctl to 1 using sysctl(8), it is possible to request that the next dump be a textdump.
If at the ddb(4) command line, the commands textdump set, textdump status, and textdump unset may be used to set, query, and clear the
textdump pending flag.
As with regular kernel dumps, a dump partition must be automatically or manually configured using dumpon(8).
EXAMPLES
In the following example, the script kdb.enter.panic will run when the kernel debugger is entered as a result of a panic, enable output cap-
ture, dump several useful pieces of debugging information, and then invoke panic in order to force a kernel dump to be written out followed
by a reboot:
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllock; call doadump; reset
In the following example, the script kdb.enter.witness will run when the kernel debugger is entered as a result of a witness violation,
printing lock-related information for the user:
script kdb.enter.witness=show locks
These scripts may also be configured using the ddb(8) utility.
SEE ALSO
tar(1), ddb(4), tar(5), ddb(8), dumpon(8), savecore(8), sysctl(8)
HISTORY
The textdump facility first appeared in FreeBSD 7.1.
AUTHORS
The textdump facility was created by Robert N. M. Watson.
BSD
December 24, 2008 BSD