Hi All,
Running 8.3-STABLE 5/21/2012 on HP DL360. While testing crash dump
functionality, the dump aborts with the following message:
Aborting dump due to I/O error.
status == 0xb, scsi status == 0x0
** DUMP FAILED (ERROR 5) **
Automatic reboot in 5 seconds - press a key on the console
2011-09-08 22:11, Andrea Venturoli skrev:
Hello.
Anyone can give any hint on this?
Guessing!
You have run out of swapspace, based on these 2 lines
panic: ffs_write: dir write
current process = 0 (swapper)
Or you have a hardware error. Does the current process
change between panics or is it
On 09/09/11 14:26, Bernt Hansson wrote:
You have run out of swapspace, based on these 2 lines
panic: ffs_write: dir write
current process = 0 (swapper)
Hmmm...
Cacti woldn't think so: the graph about swap space is plain flat (round
0%, by the way); of course it could have risen so fast that
Hello.
Anyone can give any hint on this?
I really have no clue.
bye Thanks
av.
# uname -a
FreeBSD x..it 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #1: Wed Dec 15
11:53:13 CET 2010 r...@x..it:/usr/obj/usr/src/sys/x i386
# kgdb kernel.debug
I have several jails running on my freebesd machine and lately it started to
crash when it gets a bit loaded. I followed the freebsd kernel debugging
manual, and got some output, but I have no idea what to do with it. The only
thing I think I understand of it that the bit that matters are just the
Hello.
Any one can make anything out of this crash dump?
It's an SMP amd64 6.2 box with a RAID-5 SCSI controller and a couple GiB
of RAM. We are also using GELI.
bye Thanks
av.
--
# kgdb kernel.debug /var/crash
thought of obtaining the crash dump. i went
through the developers guide.
and i added the following lines on the /etc/rc.conf
---
dumpdev=/dev/ad0s1b
dumpdir=/var/crash
savecore_flags=
--
the /etc/fstab file is
Device Mountpoint FStype Options DumpPass#
/dev/ad0s1b
On Mon, Oct 31, 2005 at 02:58:50AM -0800, kamal kc wrote:
but rebooting does not show any crash dump file
on /var/crash.
What is displayed when savecore is run at boot time? Alternatively,
what happens when you run savecore yourself? You may not have enough
space on /var to save the dump
Hi,
I compiled my FreeBSD 5.3-STABLE kernel with
options KDB, DDB
makeoptions DEBUG=-g
and wrote a kernel module that does nothing but call
panic() upon its loading, to try experimenting on
crash kernel debugger and crash dump.
Upon kldload the module, KDB was invoked and I was
dropped
I'd like to get a crash dump and so
I added the following lines to /etc/rc.conf
dumpdev=/dev/ad0s1b
dumpdir=/usr/crash
-bash-2.05b# ls -ld /usr/crash/
drwx-- 2 root wheel 512 Feb 16 11:17 /usr/crash/
but I'm not getting any dump! /usr/crash is always empty.
..and the machine crashes quite
I was up for 2wks and today saw this:
Fatal trap 12 - page fault while in kernel mode
CPUID 0 APIC ID 0
Fault write address = 0x418ad66c
Fault code = supervisor write, page not present
Inst Pointer = 0x8:0xc05109d9
Stack Pointer = 0x10:0xe5ea8978
Frame Pointer = 0x10:0xe5ea8994
Code Segment base
that I finally have it ?
During the next boot, savecore should save a crash dump in /var/crash
(assuming one was successfully saved in swap when the crash happened).
Look at the Developers Handbook for details about obtaining a stack
trace of the kernel at the moment of the crash:
http
[...]
What do I do with this information now that I finally have it ?
During the next boot, savecore should save a crash dump in /var/crash
(assuming one was successfully saved in swap when the crash happened).
Look at the Developers Handbook for details about obtaining a stack
trace of the kernel
address = 0x418ad66c
Fault code = supervisor write, page not present
[...]
What do I do with this information now that I finally have it ?
During the next boot, savecore should save a crash dump in /var/crash
(assuming one was successfully saved in swap when the crash happened).
Look
address = 0x418ad66c
Fault code = supervisor write, page not present
What do I do with this information now that I finally have it ?
During the next boot, savecore should save a crash dump in
/var/crash (assuming one was successfully saved in swap when the
crash happened).
Look
On Thu, Jan 06, 2005 at 08:56:45AM -0600, J.D. Bronson wrote:
I was up for 2wks and today saw this:
Fatal trap 12 - page fault while in kernel mode
CPUID 0 APIC ID 0
Fault write address = 0x418ad66c
Fault code = supervisor write, page not present
Inst Pointer = 0x8:0xc05109d9
Stack
Hello,
I have a FreeBSD 5.3-BETA5 server that panics more or less every week.
I have compiled the kernel with makeoptions DEBUG=-g and got a
vmcore of the last crash. Next stop will be installing FreeBSD
5.3-RELEASE within the next days.
Here is the kgdb output:
# cd
concluded it
was the OS and setup to catch a crash dump. The dump is submitted below and
perhaps someone knows how to tranlate it for a recommended fix. If this
should be on another list, please let me know.
Thanks for any help!
CRASH DUMP:
(kgdb) symbol-file kernel.debug
Reading symbols from
I am trying to debug a boot time kernel panic. This is completely new
territory for me and I need some help. I'm taking this one step at a
time, the first step is to get a crash dump.
This is a repeateable panic which occurs when I boot from my windows
partition to my FreeBSD partition. Once
19 matches
Mail list logo
