Re: 7.0 Crashing
On Sun, Jul 27, 2008 at 06:54:59PM -0400, Michael Toth wrote:
Kostik Belousov wrote:
On Sun, Jul 27, 2008 at 04:25:15PM -0400, Michael toth wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4838 (egrep)
trap number = 12
panic: page fault
cpuid = 4
Uptime: 1h2m48s
Physical memory: 2035 MB
Dumping 87 MB: 72 56 40 24 8
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
#0 doadump () at pcpu.h:195
195 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc0782597 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
#9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1,
eva=671813488) at /usr/src/sys/i386/i386/trap.c:789
#10 0xc0a8be57 in trap (frame=0xe7d6bd38) at
/usr/src/sys/i386/i386/trap.c:357
#11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#12 0x2806e607 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up
#1 0xc0782597 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418
418 doadump();
(kgdb) up
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
572 boot(bootopt);
(kgdb) up
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
899 panic(%s, trap_msg[type]);
(kgdb) up
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
812 trap_fatal(frame, eva);
(kgdb) up
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
490 (void) trap_pfault(frame, FALSE, eva);
(kgdb) up
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
139 calltrap
Current language: auto; currently asm
(kgdb) up
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
339 owner = (struct thread *)(v
~MTX_FLAGMASK);
Current language: auto; currently c
(kgdb) up
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
293 VM_OBJECT_LOCK(fs.first_object);
(kgdb) p fs
$1 = {m = 0x0, object = 0x12, pindex = 13878757899709627520, first_m =
0xc5f0a8b8, first_object = 0xc600d174, first_pindex = 0, map =
0xc56b5570, entry = 0xc59fc7f8, lookup_still_valid = 2, vp = 0xc55c5220}
(kgdb) p fs.first_object
$2 = 0xc600d174
(kgdb)
Please, show the output of
p/x *(fs.first_object)
BTW, you have said that you got a lot of the panics. Are backtraces
the same for all of them ?
Here is the p/x *(fs.first_object) ..
and it appears that vmcore.6 is different (vmcore.6 is new from a few
hours ago)
So does this point to a hardware issue?
Thanks
# kgdb kernel.debug /var/crash/vmcore.5
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd...
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer =
Re: 7.0 Crashing
Kostik Belousov wrote:
On Sun, Jul 27, 2008 at 06:54:59PM -0400, Michael Toth wrote:
Kostik Belousov wrote:
On Sun, Jul 27, 2008 at 04:25:15PM -0400, Michael toth wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4838 (egrep)
trap number = 12
panic: page fault
cpuid = 4
Uptime: 1h2m48s
Physical memory: 2035 MB
Dumping 87 MB: 72 56 40 24 8
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
#0 doadump () at pcpu.h:195
195 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc0782597 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
#9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1,
eva=671813488) at /usr/src/sys/i386/i386/trap.c:789
#10 0xc0a8be57 in trap (frame=0xe7d6bd38) at
/usr/src/sys/i386/i386/trap.c:357
#11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#12 0x2806e607 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up
#1 0xc0782597 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418
418 doadump();
(kgdb) up
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
572 boot(bootopt);
(kgdb) up
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
899 panic(%s, trap_msg[type]);
(kgdb) up
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
812 trap_fatal(frame, eva);
(kgdb) up
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
490 (void) trap_pfault(frame, FALSE, eva);
(kgdb) up
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
139 calltrap
Current language: auto; currently asm
(kgdb) up
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
339 owner = (struct thread *)(v
~MTX_FLAGMASK);
Current language: auto; currently c
(kgdb) up
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
293 VM_OBJECT_LOCK(fs.first_object);
(kgdb) p fs
$1 = {m = 0x0, object = 0x12, pindex = 13878757899709627520, first_m =
0xc5f0a8b8, first_object = 0xc600d174, first_pindex = 0, map =
0xc56b5570, entry = 0xc59fc7f8, lookup_still_valid = 2, vp = 0xc55c5220}
(kgdb) p fs.first_object
$2 = 0xc600d174
(kgdb)
Please, show the output of
p/x *(fs.first_object)
BTW, you have said that you got a lot of the panics. Are backtraces
the same for all of them ?
Here is the p/x *(fs.first_object) ..
and it appears that vmcore.6 is different (vmcore.6 is new from a few
hours ago)
So does this point to a hardware issue?
Thanks
# kgdb kernel.debug /var/crash/vmcore.5
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd...
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
Re: 7.0 Crashing
On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote: I had someone run a Dell Diags CD on the machine and it passed all tests. Before that it core'd again; here is the backtrace from that one. Is there any other want (maybe in freebsd) to test the hardware better? and/or should I submit a bug report for this? Sure, you can submit bug report. From my POV, there is actually no data to resolve it. You may use memtest86 (Google for it) for memory/chipset/cpu cache test. pgpls5rcoMmpS.pgp Description: PGP signature
Re: 7.0 Crashing
Kostik Belousov wrote: On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote: I had someone run a Dell Diags CD on the machine and it passed all tests. Before that it core'd again; here is the backtrace from that one. Is there any other want (maybe in freebsd) to test the hardware better? and/or should I submit a bug report for this? Sure, you can submit bug report. From my POV, there is actually no data to resolve it. i.e. you should have no expectation that anyone else will be able to resolve it either. Note that diagnostics can tell you when a machine has failed, but can never tell you when a machine is working perfectly. Kris You may use memtest86 (Google for it) for memory/chipset/cpu cache test. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 Crashing
On Mon, Jul 28, 2008 at 09:52:45PM +0200, Kris Kennaway wrote: Kostik Belousov wrote: On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote: I had someone run a Dell Diags CD on the machine and it passed all tests. Before that it core'd again; here is the backtrace from that one. Is there any other want (maybe in freebsd) to test the hardware better? and/or should I submit a bug report for this? Sure, you can submit bug report. From my POV, there is actually no data to resolve it. i.e. you should have no expectation that anyone else will be able to resolve it either. Why ?! Note that diagnostics can tell you when a machine has failed, but can never tell you when a machine is working perfectly. Kris You may use memtest86 (Google for it) for memory/chipset/cpu cache test. pgpyKeF59EZ9P.pgp Description: PGP signature
Re: 7.0 Crashing
Kostik Belousov wrote: On Mon, Jul 28, 2008 at 09:52:45PM +0200, Kris Kennaway wrote: Kostik Belousov wrote: On Mon, Jul 28, 2008 at 01:16:39PM -0400, Michael toth wrote: I had someone run a Dell Diags CD on the machine and it passed all tests. Before that it core'd again; here is the backtrace from that one. Is there any other want (maybe in freebsd) to test the hardware better? and/or should I submit a bug report for this? Sure, you can submit bug report. From my POV, there is actually no data to resolve it. i.e. you should have no expectation that anyone else will be able to resolve it either. Why ?! This was directed to Michael, sorry. Kris Note that diagnostics can tell you when a machine has failed, but can never tell you when a machine is working perfectly. Kris You may use memtest86 (Google for it) for memory/chipset/cpu cache test. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 Crashing
Michael Toth wrote: Hi, I am running 7.0 stable on a Dell Power Edge 2950 and it is core dumping on me. Below is the dmesg and some core info I am hoping that someone can help me find out why it keeps core dumping on me. Thanks # cd /usr/obj/usr/src/sys/GENERIC/ # kgdb kernel.debug /var/crash/vmcore.5 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0775284 stack pointer = 0x28:0xe7d6bad0 frame pointer = 0x28:0xe7d6bae8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4838 (egrep) trap number = 12 panic: page fault cpuid = 4 Uptime: 1h2m48s Physical memory: 2035 MB Dumping 87 MB: 72 56 40 24 8 Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb)q # cat /var/run/dmesg.boot Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #0: Sun Jul 27 08:58:11 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf48 Stepping = 8 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x649dSSE3,RSVD2,MON,DS_CPL,EST,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 Logical CPUs per core: 2 real memory = 2147221504 (2047 MB) avail memory = 2091675648 (1994 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 ioapic3: Changing APIC ID to 11 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard ioapic3 Version 2.0 irqs 96-119 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: DELL PE BKC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 amr0: LSILogic MegaRAID 1.53 mem 0xf81f-0xf81f,0xfe9c-0xfe9f irq 46 at device 14.0 on pci2 amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: LSILogic PERC 4e/Di Firmware 521S, BIOS H430, 256MB RAM pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 5.0 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection 6.9.5 port 0xecc0-0xecff mem 0xfe6e-0xfe6f irq 64 at device 7.0 on pci6 em0: [FILTER] em0: Ethernet address: 00:14:22:21:da:67 pcib7: ACPI PCI-PCI bridge at device 0.2 on pci5 pci7: ACPI PCI bus on pcib7 em1: Intel(R) PRO/1000 Network Connection 6.9.5 port 0xdcc0-0xdcff mem 0xfe4e-0xfe4f irq 65 at device 8.0 on pci7 em1: [FILTER] em1: Ethernet address: 00:14:22:21:da:68 pcib8: ACPI PCI-PCI bridge at device 6.0 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 0.0 on pci8 pci9: ACPI PCI bus on pcib9 amr1: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 106 at device 4.0 on pci9 amr1: [ITHREAD] amr1: delete logical drives supported by controller amr1: LSILogic PERC 4/DC Firmware 351S,
Re: 7.0 Crashing
Kris Kennaway wrote: Michael Toth wrote: Hi, I am running 7.0 stable on a Dell Power Edge 2950 and it is core dumping on me. Below is the dmesg and some core info I am hoping that someone can help me find out why it keeps core dumping on me. Thanks # cd /usr/obj/usr/src/sys/GENERIC/ # kgdb kernel.debug /var/crash/vmcore.5 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0775284 stack pointer = 0x28:0xe7d6bad0 frame pointer = 0x28:0xe7d6bae8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4838 (egrep) trap number = 12 panic: page fault cpuid = 4 Uptime: 1h2m48s Physical memory: 2035 MB Dumping 87 MB: 72 56 40 24 8 Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb)q # cat /var/run/dmesg.boot Copyright (c) 1992-2008 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 7.0-STABLE #0: Sun Jul 27 08:58:11 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2793.20-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf48 Stepping = 8 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x649dSSE3,RSVD2,MON,DS_CPL,EST,CNXT-ID,CX16,xTPR AMD Features=0x2010NX,LM AMD Features2=0x1LAHF Cores per package: 2 Logical CPUs per core: 2 real memory = 2147221504 (2047 MB) avail memory = 2091675648 (1994 MB) ACPI APIC Table: DELL PE BKC FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic1: Changing APIC ID to 9 ioapic2: Changing APIC ID to 10 ioapic3: Changing APIC ID to 11 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 32-55 on motherboard ioapic2 Version 2.0 irqs 64-87 on motherboard ioapic3 Version 2.0 irqs 96-119 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: DELL PE BKC on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x808-0x80b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 amr0: LSILogic MegaRAID 1.53 mem 0xf81f-0xf81f,0xfe9c-0xfe9f irq 46 at device 14.0 on pci2 amr0: [ITHREAD] amr0: delete logical drives supported by controller amr0: LSILogic PERC 4e/Di Firmware 521S, BIOS H430, 256MB RAM pcib3: ACPI PCI-PCI bridge at device 0.2 on pci1 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 4.0 on pci0 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 5.0 on pci0 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge at device 0.0 on pci5 pci6: ACPI PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection 6.9.5 port 0xecc0-0xecff mem 0xfe6e-0xfe6f irq 64 at device 7.0 on pci6 em0: [FILTER] em0: Ethernet address: 00:14:22:21:da:67 pcib7: ACPI PCI-PCI bridge at device 0.2 on pci5 pci7: ACPI PCI bus on pcib7 em1: Intel(R) PRO/1000 Network Connection 6.9.5 port 0xdcc0-0xdcff mem 0xfe4e-0xfe4f irq 65 at device 8.0 on pci7 em1: [FILTER] em1: Ethernet address: 00:14:22:21:da:68 pcib8: ACPI PCI-PCI bridge at device 6.0 on pci0 pci8: ACPI PCI bus on pcib8 pcib9: ACPI PCI-PCI bridge at device 0.0 on pci8 pci9: ACPI PCI bus on pcib9 amr1: LSILogic MegaRAID 1.53 mem 0xf80f-0xf80f irq 106 at device 4.0 on pci9 amr1: [ITHREAD] amr1: delete logical drives supported by controller amr1:
Re: 7.0 Crashing
Michael Toth wrote: Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0782859 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 #8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536, fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293 #9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1, eva=671813488) at /usr/src/sys/i386/i386/trap.c:789 #10 0xc0a8be57 in trap (frame=0xe7d6bd38) at /usr/src/sys/i386/i386/trap.c:357 #11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0x2806e607 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) q Not much there, check for RAM/hardware problems. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0 Crashing
On Sun, Jul 27, 2008 at 08:41:03PM +0200, Kris Kennaway wrote: Michael Toth wrote: Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0782859 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 #8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536, fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293 #9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1, eva=671813488) at /usr/src/sys/i386/i386/trap.c:789 #10 0xc0a8be57 in trap (frame=0xe7d6bd38) at /usr/src/sys/i386/i386/trap.c:357 #11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0x2806e607 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) q Not much there, check for RAM/hardware problems. Yes, it does not look sensible. Just to be sure, show the source lines around vm/vm_fault.c:293, and, from the frame 8, print the content of the fs and fs.first_object. The fault address 0x188 would suggest that some NULL pointer dereference is being performed, but assuming faulted line is VM_OBJECT_LOCK(fs.first_object); no appropriate structure member with offset 0x188 could be imagined. pgpwMrykZoTOa.pgp Description: PGP signature
Re: 7.0 Crashing
On Sun, Jul 27, 2008 at 04:25:15PM -0400, Michael toth wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4838 (egrep)
trap number = 12
panic: page fault
cpuid = 4
Uptime: 1h2m48s
Physical memory: 2035 MB
Dumping 87 MB: 72 56 40 24 8
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
#0 doadump () at pcpu.h:195
195 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
#9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1,
eva=671813488) at /usr/src/sys/i386/i386/trap.c:789
#10 0xc0a8be57 in trap (frame=0xe7d6bd38) at
/usr/src/sys/i386/i386/trap.c:357
#11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#12 0x2806e607 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up
#1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
418 doadump();
(kgdb) up
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
572 boot(bootopt);
(kgdb) up
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
899 panic(%s, trap_msg[type]);
(kgdb) up
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
812 trap_fatal(frame, eva);
(kgdb) up
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
490 (void) trap_pfault(frame, FALSE, eva);
(kgdb) up
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
139 calltrap
Current language: auto; currently asm
(kgdb) up
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
339 owner = (struct thread *)(v
~MTX_FLAGMASK);
Current language: auto; currently c
(kgdb) up
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
293 VM_OBJECT_LOCK(fs.first_object);
(kgdb) p fs
$1 = {m = 0x0, object = 0x12, pindex = 13878757899709627520, first_m =
0xc5f0a8b8, first_object = 0xc600d174, first_pindex = 0, map =
0xc56b5570, entry = 0xc59fc7f8, lookup_still_valid = 2, vp = 0xc55c5220}
(kgdb) p fs.first_object
$2 = 0xc600d174
(kgdb)
Please, show the output of
p/x *(fs.first_object)
BTW, you have said that you got a lot of the panics. Are backtraces
the same for all of them ?
pgpLuzydpzEKW.pgp
Description: PGP signature
Re: 7.0 Crashing
Kostik Belousov wrote: On Sun, Jul 27, 2008 at 08:41:03PM +0200, Kris Kennaway wrote: Michael Toth wrote: Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0782859 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 #8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536, fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293 #9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1, eva=671813488) at /usr/src/sys/i386/i386/trap.c:789 #10 0xc0a8be57 in trap (frame=0xe7d6bd38) at /usr/src/sys/i386/i386/trap.c:357 #11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0x2806e607 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) q Not much there, check for RAM/hardware problems. Yes, it does not look sensible. Just to be sure, show the source lines around vm/vm_fault.c:293, and, from the frame 8, print the content of the fs and fs.first_object. The fault address 0x188 would suggest that some NULL pointer dereference is being performed, but assuming faulted line is VM_OBJECT_LOCK(fs.first_object); no appropriate structure member with offset 0x188 could be imagined. Here is the kgdb with (what I hope) is the information you wanted to see. (I do not know how to use kgdb very well) Thanks # kgdb kernel.debug /var/crash/vmcore.5 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-marcel-freebsd... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 4; apic id = 04 fault virtual address = 0x188 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0775284 stack pointer = 0x28:0xe7d6bad0 frame pointer = 0x28:0xe7d6bae8 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 4838 (egrep) trap number = 12 panic: page fault cpuid = 4 Uptime: 1h2m48s Physical memory: 2035 MB Dumping 87 MB: 72 56 40 24 8 Reading symbols from /boot/kernel/acpi.ko...Reading symbols from /boot/kernel/acpi.ko.symbols...done. done. Loaded symbols for /boot/kernel/acpi.ko #0 doadump () at pcpu.h:195 195 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) backtrace #0 doadump () at pcpu.h:195 #1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 #2 0xc0782859 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 #3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at /usr/src/sys/i386/i386/trap.c:899 #4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at /usr/src/sys/i386/i386/trap.c:812 #5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at /usr/src/sys/i386/i386/trap.c:490 #6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0, file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339 #8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536, fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293 #9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1, eva=671813488) at /usr/src/sys/i386/i386/trap.c:789 #10 0xc0a8be57 in trap (frame=0xe7d6bd38) at /usr/src/sys/i386/i386/trap.c:357 #11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #12 0x2806e607 in ?? () Previous frame inner to this frame (corrupt stack?) (kgdb) up #1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418 418 doadump(); (kgdb) up #2 0xc0782859 in panic (fmt=Variable fmt is not available. ) at /usr/src/sys/kern/kern_shutdown.c:572 572 boot(bootopt); (kgdb) up #3 0xc0a8b39c in trap_fatal
Re: 7.0 Crashing
Kostik Belousov wrote:
On Sun, Jul 27, 2008 at 04:25:15PM -0400, Michael toth wrote:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 4838 (egrep)
trap number = 12
panic: page fault
cpuid = 4
Uptime: 1h2m48s
Physical memory: 2035 MB
Dumping 87 MB: 72 56 40 24 8
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
#0 doadump () at pcpu.h:195
195 __asm __volatile(movl %%fs:0,%0 : =r (td));
(kgdb) backtrace
#0 doadump () at pcpu.h:195
#1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
#9 0xc0a8b50b in trap_pfault (frame=0xe7d6bd38, usermode=1,
eva=671813488) at /usr/src/sys/i386/i386/trap.c:789
#10 0xc0a8be57 in trap (frame=0xe7d6bd38) at
/usr/src/sys/i386/i386/trap.c:357
#11 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#12 0x2806e607 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(kgdb) up
#1 0xc0782597 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
418 doadump();
(kgdb) up
#2 0xc0782859 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
572 boot(bootopt);
(kgdb) up
#3 0xc0a8b39c in trap_fatal (frame=0xe7d6ba90, eva=392) at
/usr/src/sys/i386/i386/trap.c:899
899 panic(%s, trap_msg[type]);
(kgdb) up
#4 0xc0a8b620 in trap_pfault (frame=0xe7d6ba90, usermode=0, eva=392) at
/usr/src/sys/i386/i386/trap.c:812
812 trap_fatal(frame, eva);
(kgdb) up
#5 0xc0a8bfcc in trap (frame=0xe7d6ba90) at
/usr/src/sys/i386/i386/trap.c:490
490 (void) trap_pfault(frame, FALSE, eva);
(kgdb) up
#6 0xc0a71bdb in calltrap () at /usr/src/sys/i386/i386/exception.s:139
139 calltrap
Current language: auto; currently asm
(kgdb) up
#7 0xc0775284 in _mtx_lock_sleep (m=0xc600d174, tid=3318745216, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:339
339 owner = (struct thread *)(v
~MTX_FLAGMASK);
Current language: auto; currently c
(kgdb) up
#8 0xc09a93d7 in vm_fault (map=0xc56b5570, vaddr=671809536,
fault_type=2 '\002', fault_flags=8) at /usr/src/sys/vm/vm_fault.c:293
293 VM_OBJECT_LOCK(fs.first_object);
(kgdb) p fs
$1 = {m = 0x0, object = 0x12, pindex = 13878757899709627520, first_m =
0xc5f0a8b8, first_object = 0xc600d174, first_pindex = 0, map =
0xc56b5570, entry = 0xc59fc7f8, lookup_still_valid = 2, vp = 0xc55c5220}
(kgdb) p fs.first_object
$2 = 0xc600d174
(kgdb)
Please, show the output of
p/x *(fs.first_object)
BTW, you have said that you got a lot of the panics. Are backtraces
the same for all of them ?
Here is the p/x *(fs.first_object) ..
and it appears that vmcore.6 is different (vmcore.6 is new from a few
hours ago)
So does this point to a hardware issue?
Thanks
# kgdb kernel.debug /var/crash/vmcore.5
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain
conditions.
Type show copying to see the conditions.
There is absolutely no warranty for GDB. Type show warranty for details.
This GDB was configured as i386-marcel-freebsd...
Unread portion of the kernel message buffer:
Fatal trap 12: page fault while in kernel mode
cpuid = 4; apic id = 04
fault virtual address = 0x188
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0775284
stack pointer = 0x28:0xe7d6bad0
frame pointer = 0x28:0xe7d6bae8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
