Date: Thu, 4 Sep 2003 11:45:09 -0400 From: "Michael W. Oliver" <michael@gargantuan.com> To: freebsd-stable@freebsd.org Subject: Re: Heads up: panics should be fixed! Message-ID: <200309041145.12839.michael@gargantuan.com>
next in thread | raw e-mail | index | archive | help
+--- On Wednesday, September 03, 2003 03:09 ---
| Mike Tancsa proclaimed:
| >| in
| >| /etc/rc.conf
| >| add
| >| dumpdev="/dev/ad0s1b" # Device name to crashdump to (or NO).
| >| dumpdir="/var/crash" # Directory where crash dumps are to be stored
| >
| >Ok, I am guessing the 'dumpdev' line is the boot-time equivalent of
| > running the dumpon(8) command to set the sysctl kern.dumpdev.
|
| Correct. The above also assumes thats where you have your swap. If its
| not, than adjust accordingly.
|
Well, it has been a little over 24 hours, and I got a panic, but no dump!
Here is the log from the panic as well as the message stating that a dump
couldn't be performed:
//--start--//
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0xbed557c5
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc027c38d
stack pointer = 0x10:0xdea01ecc
frame pointer = 0x10:0xdea01ef4
code segment = base 0x0, limit 0xfffff, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags = interrupt enabled, resume, IOPL = 0
current process = 5 (syncer)
interrupt mask = none
trap number = 12
panic: page fault
syncing disks... 8
done
Uptime: 1d0h9m53s
dumping to dev #ar/0x20001, offset 1279168
dump failed, reason: device doesn't support a dump routine
Automatic reboot in 15 seconds - press a key on the console to abort
Rebooting...
//--end--//
I have a HighPoint IDE RAID controller in this box with a RAID 1
configuration (ar0) using two Seagate 120GB disks (ad4 and ad6). I put
this in /etc/rc.conf before I rebooted last night:
//--start--//
$ head /etc/rc.conf
dumpdev="/dev/ar0s1b" #swap device configured in /etc/fstab
dumpdir="/usr/var/crash" #using a dir under /usr as /var isn't big enough
//--end--//
Here is the output from 'disklabel -r ar0' showing that my swap device is
indeed /dev/ar0s1b:
//--start--//
$ disklabel -r ar0
# /dev/ar0c:
type: ESDI
disk: ar0s1
label:
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 14592
sectors/unit: 234436482
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize bps/cpg]
a: 262144 0 4.2BSD 2048 16384 94 # (Cyl. 0 - 16*)
b: 2589856 262144 swap # (Cyl. 16*- 177*)
c: 234436482 0 unused 0 0 # (Cyl. 0 - 14592*)
e: 524288 2852000 4.2BSD 2048 16384 94 # (Cyl. 177*- 210*)
f: 524288 3376288 4.2BSD 2048 16384 94 # (Cyl. 210*- 242*)
g: 230535906 3900576 4.2BSD 2048 16384 89 # (Cyl. 242*- 14592*)
//--end--//
So, what am I missing here in order to get a dump so that I can help debug
this problem? Is the ar0 device not able to be a dump device? Do I need to
install a dedicated IDE drive on the MB's IDE controller just so that I can
get a dump?
This is exacerbated by the fact that I will have to wait another 24 hours to
try again.
--
Mike
perl -e 'print unpack("u","88V]N=&%C=\"!I;F9O(&EN(&AE861E<G,*");'
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200309041145.12839.michael>